Skip to contentSkip to conversation

2.4.9 UDP broke?

DISCUSSION Jeremiah Johnson 6 participants 12 messages Aug 31, 2001 – Sep 7, 2001

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello linux-kernel,

I am having very strange problems with 2.4.9 and UDP. Basically, anything using UDP wont work. Anything using TCP/ICMP works fine. I am not even enabling any kind of firewall code in the kernel so that shouldn't be the issue, and I have looked at pretty much everything I can think of to resolve this issue. Can anybody either point me in the right direction or if needed request specific info to fix the problem?

- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO48sm5HTj7BlqKb5AQGOpQgApna8Qr9qqHsQFRb2hCYYvgOere09U1Sf iWDVFXJSpR452/sZnURsaoR8FNiVfTK4OkeCtp12ufr5AKfF+1PX3uflHj9vmesT Hz5MVE4N7kN7NeJ3pfFsMLDpcVV52w+2R9vqsX4Dk3t4DubwPO2vXv3ND2rNjXCX CCFOcZK2kFxgitpICQpT5/KnvBoRMj84HGH2Co3i0IYRBOTQ/U506Hy6gbjhgTER 9BbqtTuSkEwo90Ryp3WLIGGyjPn0qgRoaBxYlAm+2wVR3thGTQGQy0tU373sJxUC woh2ELHAK312vGCXbncXQ57pkU168QcEH5uzLL00/1QWILwtPa4MSA== =roGe
-----END PGP SIGNATURE-----

#1 lore raw

--- Jeremiah Johnson <[email protected]> wrote: >
-----BEGIN PGP SIGNED MESSAGE-----

Quoted 8 lines

Hash: MD5

Hello linux-kernel,

I am having very strange problems with 2.4.9 and
UDP. Basically,
anything using UDP wont work. Anything using
TCP/ICMP works fine.

May be it is not the kernel, I dont know but in my box it works as normal

(I can use speakfreely ; it uses UDP and otehr program too)

Quoted 9 lines

in the kernel so
that shouldn't be the issue, and I have looked at
pretty much
everything I can think of to resolve this issue.
Can anybody either
point me in the right direction or if needed
request specific info
to fix the problem?

Quoted 9 lines

- --
Best regards,
Jeremiah
mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO48sm5HTj7BlqKb5AQGOpQgApna8Qr9qqHsQFRb2hCYYvgOere09U1Sf

Quoted 1 line

iWDVFXJSpR452/sZnURsaoR8FNiVfTK4OkeCtp12ufr5AKfF+1PX3uflHj9vmesT

Quoted 1 line

Hz5MVE4N7kN7NeJ3pfFsMLDpcVV52w+2R9vqsX4Dk3t4DubwPO2vXv3ND2rNjXCX

Quoted 1 line

CCFOcZK2kFxgitpICQpT5/KnvBoRMj84HGH2Co3i0IYRBOTQ/U506Hy6gbjhgTER

Quoted 1 line

9BbqtTuSkEwo90Ryp3WLIGGyjPn0qgRoaBxYlAm+2wVR3thGTQGQy0tU373sJxUC

Quoted 1 line

woh2ELHAK312vGCXbncXQ57pkU168QcEH5uzLL00/1QWILwtPa4MSA==

Quoted 10 lines

=roGe
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

=====
S.KIEU

http://travel.yahoo.com.au - Yahoo! Travel
- Got Itchy feet? Get inspired!

#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello Steve,

Thursday, August 30, 2001, 10:50:08 PM, you wrote:

SK> --- Jeremiah Johnson <[email protected]> wrote: > SK> -----BEGIN PGP SIGNED MESSAGE-----

Quoted 8 lines
Quoted 8 lines

Hash: MD5

Hello linux-kernel,

I am having very strange problems with 2.4.9 and
UDP. Basically,
anything using UDP wont work. Anything using
TCP/ICMP works fine.

SK> May be it is not the kernel, I dont know but in my box SK> it works as normal

SK> (I can use speakfreely ; it uses UDP and otehr program SK> too)

Well considering the only thing I changed in my configuration is the kernel, I think its a problem there. Went from 2.4.3-ac? to 2.4.9. System is RedHat 7.1.. Maybe it has something to do with RedHats inclusion of a broken compiler, I'll have to check on that when I get into the office.

I do have 2.4.9 working fine on other systems too. Strange.
- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO4+xapHTj7BlqKb5AQE/sQf+MNVYf4Dv4KRS2V3jiexwdlwpAUyNGUDp VUli3po/IuoBsiz0zubCK0tFSVMB/2o24kYzAFIBKajrQP7uVVSUqbQzWpwWazpg Vu3wAnHx3oPBpWmF3fxrMGjC/1g4FKUAnmBKne8VQOPaEVy+iUxZy5VQhXYXoBs0 O98+7VzgxjPI7txEmmqcJdLJHy7hQSuKvN9+FYvDmueeWeZV909NuH9P3Estp00c HtuKAb57wkea8CcoZlknr+Iuei7geRAti4iGrGMYEVFNTYQxVVSC/FGM+T4UP1ia R08TX47WHR2sucVatXv8oT/ixyepo82D0xIHbBltYLB8yqC/JxkDYA== =5GKB
-----END PGP SIGNATURE-----

#10 lore raw
In reply to Steve Kieu
Quoted 4 lines · Jeremiah Johnson

Well considering the only thing I changed in my configuration is the kernel, I think its a problem there. Went from 2.4.3-ac? to 2.4.9. System is RedHat 7.1.. Maybe it has something to do with RedHats inclusion of a broken compiler

Please don't trot out that tired old FUD again - it just makes you look really silly...

I'm running 2.4.9 and 2.4.10-pre on a number of Red Hat 7.1 boxes and nfs works fine, even rwhod across a vpn is working fine.

cu

jjs

#11 lore raw
In reply to Jeremiah Johnson
Quoted 2 lines · Jeremiah Johnson

I am having very strange problems with 2.4.9 and UDP. Basically, anything using UDP wont work. Anything using TCP/ICMP works fine.

NTP (which relies on UDP traffic to port #123) works fine here with 2.4.9. Check your packet filter setup, please.

#3 lore raw
In reply to Jeremiah Johnson
Quoted 21 lines · Jeremiah Johnson

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello Steve,

Thursday, August 30, 2001, 10:50:08 PM, you wrote:

SK> --- Jeremiah Johnson <[email protected]> wrote: > SK> -----BEGIN PGP SIGNED MESSAGE-----

Quoted 8 lines
Quoted 8 lines

Hash: MD5

Hello linux-kernel,

I am having very strange problems with 2.4.9 and
UDP. Basically,
anything using UDP wont work. Anything using
TCP/ICMP works fine.

SK> May be it is not the kernel, I dont know but in my box SK> it works as normal

Quoted 8 lines

SK> (I can use speakfreely ; it uses UDP and otehr program SK> too)

Well considering the only thing I changed in my configuration is the kernel, I think its a problem there. Went from 2.4.3-ac? to 2.4.9. System is RedHat 7.1.. Maybe it has something to do with RedHats inclusion of a broken compiler, I'll have to check on that when I get into the office.

I had a very similar experience. In my case it turned out that for some reason no UDP packets above 5524 would come through (try pinging with larger than default packet sizes). The solution was to restrict NFS to 5000 (actually 4096) size packets. I have not been able to figure out the cause of this yet. (and yes, tcpdump was able to see them fine).

Vladimir Dergachev

Quoted 24 lines

I do have 2.4.9 working fine on other systems too. Strange.
- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO4+xapHTj7BlqKb5AQE/sQf+MNVYf4Dv4KRS2V3jiexwdlwpAUyNGUDp VUli3po/IuoBsiz0zubCK0tFSVMB/2o24kYzAFIBKajrQP7uVVSUqbQzWpwWazpg Vu3wAnHx3oPBpWmF3fxrMGjC/1g4FKUAnmBKne8VQOPaEVy+iUxZy5VQhXYXoBs0 O98+7VzgxjPI7txEmmqcJdLJHy7hQSuKvN9+FYvDmueeWeZV909NuH9P3Estp00c HtuKAb57wkea8CcoZlknr+Iuei7geRAti4iGrGMYEVFNTYQxVVSC/FGM+T4UP1ia R08TX47WHR2sucVatXv8oT/ixyepo82D0xIHbBltYLB8yqC/JxkDYA== =5GKB
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#4 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

I found the answer to the problem today. It has to do with a bug in one of these options:

CONFIG_TULIP_MWI
CONFIG_TULIP_MMIO

Since the system is a older dual p100 I didn't really want to sit through the 2 hours of compilation to "test" which one it is. I'm willing to bet its CONFIG_TULIP_MWI though since its still marked as experimental. With both of these options disabled 2.4.9 works fine on that system though as it does on my other boxes. Whoever maintains the code for those two config options might want to do some testing. I can provide more information about the system if needed.

Sunday, September 02, 2001, 7:25:44 PM, you wrote:

vmc> I had a very similar experience. In my case it turned out that for some vmc> reason no UDP packets above 5524 would come through (try pinging with vmc> larger than default packet sizes). The solution was to restrict NFS to vmc> 5000 (actually 4096) size packets. I have not been able to figure out the vmc> cause of this yet. (and yes, tcpdump was able to see them fine).

vmc> Vladimir Dergachev

- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO5WLyZHTj7BlqKb5AQFiIQf8DG8rppS8oNKQvmQts2rFQzx0MVizZZv/ p12tm+bcToP8jg6OKL0hzkeL59k3RgJpbjSleHl6VHgGzZ4VfZuvtE7gwA0e/Ch8 MQck+diQkDY14qM+qxdIhwjuSyt+qDTlOPge/MZKNvtGckYkQ9qKVHiWbKWuxlYS U4N8knpXHUZ9fM+hPPqi/0yNfwx6g7QbtLycYJzP0GIDSzP4y/P30HMkSJ9EUzP1 MQCho4dj2K2WvMyrNVAO70Nj90j1ioU7vJE2LMooKrZmWBpBSMX6MMKr//lJP73H RTQLNZmRGbBtblq4QiXai6OpEYkaaE84iutfs9JbssOJ+S2cxNDM1g== =XNHF
-----END PGP SIGNATURE-----

#5 lore raw
Quoted 10 lines · Jeremiah Johnson

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

I found the answer to the problem today. It has to do with a bug in one of these options:

CONFIG_TULIP_MWI
CONFIG_TULIP_MMIO

Hmm, interesting. I'll check the latest version of tulip (as well as the one on Donald Becker's website). Did you try them out already ?

Vladimir Dergachev

Quoted 36 lines

Since the system is a older dual p100 I didn't really want to sit through the 2 hours of compilation to "test" which one it is. I'm willing to bet its CONFIG_TULIP_MWI though since its still marked as experimental. With both of these options disabled 2.4.9 works fine on that system though as it does on my other boxes. Whoever maintains the code for those two config options might want to do some testing. I can provide more information about the system if needed.

Sunday, September 02, 2001, 7:25:44 PM, you wrote:

vmc> I had a very similar experience. In my case it turned out that for some vmc> reason no UDP packets above 5524 would come through (try pinging with vmc> larger than default packet sizes). The solution was to restrict NFS to vmc> 5000 (actually 4096) size packets. I have not been able to figure out the vmc> cause of this yet. (and yes, tcpdump was able to see them fine).

vmc> Vladimir Dergachev

- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO5WLyZHTj7BlqKb5AQFiIQf8DG8rppS8oNKQvmQts2rFQzx0MVizZZv/ p12tm+bcToP8jg6OKL0hzkeL59k3RgJpbjSleHl6VHgGzZ4VfZuvtE7gwA0e/Ch8 MQck+diQkDY14qM+qxdIhwjuSyt+qDTlOPge/MZKNvtGckYkQ9qKVHiWbKWuxlYS U4N8knpXHUZ9fM+hPPqi/0yNfwx6g7QbtLycYJzP0GIDSzP4y/P30HMkSJ9EUzP1 MQCho4dj2K2WvMyrNVAO70Nj90j1ioU7vJE2LMooKrZmWBpBSMX6MMKr//lJP73H RTQLNZmRGbBtblq4QiXai6OpEYkaaE84iutfs9JbssOJ+S2cxNDM1g== =XNHF
-----END PGP SIGNATURE-----

#6 lore raw

Ironically, the latest "stable" version of the tulip driver on:
http://sourceforge.net/projects/tulip is older than whats in 2.4.9. I'm willing to bet the latest "devel" is older too (they're dated June 15(devel), and February 19(stable).

-miah

Quoted 19 lines · On Tue, 4 Sep 2001 [email protected] wrote:
Quoted 10 lines · Jeremiah Johnson

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

I found the answer to the problem today. It has to do with a bug in one of these options:

CONFIG_TULIP_MWI
CONFIG_TULIP_MMIO

Hmm, interesting. I'll check the latest version of tulip (as well as the one on Donald Becker's website). Did you try them out already ?

Vladimir Dergachev

#7 lore raw
In reply to Jeremiah Johnson
Quoted 11 lines · Jeremiah Johnson

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

I found the answer to the problem today. It has to do with a bug in one of these options:

CONFIG_TULIP_MWI
CONFIG_TULIP_MMIO

You are absolutely correct - once I enabled both of these it works great. My guess is that whoever tested the patches was concentrated on the case when options were enabled.

Vladimir Dergachev

Quoted 35 lines

Since the system is a older dual p100 I didn't really want to sit through the 2 hours of compilation to "test" which one it is. I'm willing to bet its CONFIG_TULIP_MWI though since its still marked as experimental. With both of these options disabled 2.4.9 works fine on that system though as it does on my other boxes. Whoever maintains the code for those two config options might want to do some testing. I can provide more information about the system if needed.

Sunday, September 02, 2001, 7:25:44 PM, you wrote:

vmc> I had a very similar experience. In my case it turned out that for some vmc> reason no UDP packets above 5524 would not come through (try pinging with vmc> larger than default packet sizes). The solution was to restrict NFS to vmc> 5000 (actually 4096) size packets. I have not been able to figure out the vmc> cause of this yet. (and yes, tcpdump was able to see them fine).

vmc> Vladimir Dergachev

- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO5WLyZHTj7BlqKb5AQFiIQf8DG8rppS8oNKQvmQts2rFQzx0MVizZZv/ p12tm+bcToP8jg6OKL0hzkeL59k3RgJpbjSleHl6VHgGzZ4VfZuvtE7gwA0e/Ch8 MQck+diQkDY14qM+qxdIhwjuSyt+qDTlOPge/MZKNvtGckYkQ9qKVHiWbKWuxlYS U4N8knpXHUZ9fM+hPPqi/0yNfwx6g7QbtLycYJzP0GIDSzP4y/P30HMkSJ9EUzP1 MQCho4dj2K2WvMyrNVAO70Nj90j1ioU7vJE2LMooKrZmWBpBSMX6MMKr//lJP73H RTQLNZmRGbBtblq4QiXai6OpEYkaaE84iutfs9JbssOJ+S2cxNDM1g== =XNHF
-----END PGP SIGNATURE-----

#8 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

If I enable both of these options though, UDP totally breaks for me. So its definitely something in there. Maybe I'll get some time and test to see which option is actually doing the breaking.

Wednesday, September 05, 2001, 1:28:39 PM, you wrote:

Quoted 11 lines · Jeremiah Johnson
Quoted 11 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

I found the answer to the problem today. It has to do with a bug in one of these options:

CONFIG_TULIP_MWI
CONFIG_TULIP_MMIO

vmc> You are absolutely correct - once I enabled both of these it works vmc> great. My guess is that whoever tested the patches was concentrated on the vmc> case when options were enabled.

vmc> Vladimir Dergachev

- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO5kFFJHTj7BlqKb5AQG+9ggAnKz03bYjsYYSsrINzUTKEFCtWs2bRP0t sGsIZ55rpi4FH9QFbJGIzxih6C5Mf3p1IJU2fUEP5ci4ddEDJbWbAia/4yz6S2qd hAe3pjep/Oy1XBky8PKxIpLkOJMAgFgqeM9aguwFVCuhXxZBvK6NNPaozqZ/nYHl 9EM8/kuwfNONaJxYnduqkCRPKdCUPxPZcuwd56Wt3JvJ6meUW249pGEBJhFM63Qe +esn3TweBeYj5M80mYcU0CunDRr3D0ABMrdtApCUv0FMIP7ke0LTCQBeZZrUtajW +k/gDEySN3tRIuCUltYZ5SYMxtxFZ6eYgerwyhr3s8iKfD+7Tk1BFg== =/5Uc
-----END PGP SIGNATURE-----

#9 lore raw
Quoted 8 lines · Jeremiah Johnson

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

If I enable both of these options though, UDP totally breaks for me. So its definitely something in there. Maybe I'll get some time and test to see which option is actually doing the breaking.

After some testing: 2.4.6 and 2.4.8 require both of these options be disabled. 2.4.9 wants them enabled.

Furthemore: after I turned on these option on the only 2.4.9 kernel I currently have I was able to ping all machines on the network (and they were able to ping each other). However, before (when options were turned off) none of the machines on the network could ping each other with packets of size 6000, though I could see them with tcpdump.

<whine>
tulip worked so great earlier, why mess with it ?
</whine>

Vladimir Dergachev

Quoted 45 lines

Wednesday, September 05, 2001, 1:28:39 PM, you wrote:

Quoted 11 lines · Jeremiah Johnson
Quoted 11 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello volodya,

I found the answer to the problem today. It has to do with a bug in one of these options:

CONFIG_TULIP_MWI
CONFIG_TULIP_MMIO

vmc> You are absolutely correct - once I enabled both of these it works vmc> great. My guess is that whoever tested the patches was concentrated on the vmc> case when options were enabled.

vmc> Vladimir Dergachev

- --
Best regards,
Jeremiah mailto:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQEVAwUAO5kFFJHTj7BlqKb5AQG+9ggAnKz03bYjsYYSsrINzUTKEFCtWs2bRP0t sGsIZ55rpi4FH9QFbJGIzxih6C5Mf3p1IJU2fUEP5ci4ddEDJbWbAia/4yz6S2qd hAe3pjep/Oy1XBky8PKxIpLkOJMAgFgqeM9aguwFVCuhXxZBvK6NNPaozqZ/nYHl 9EM8/kuwfNONaJxYnduqkCRPKdCUPxPZcuwd56Wt3JvJ6meUW249pGEBJhFM63Qe

(quoted diff) +2 -0
+esn3TweBeYj5M80mYcU0CunDRr3D0ABMrdtApCUv0FMIP7ke0LTCQBeZZrUtajW
+k/gDEySN3tRIuCUltYZ5SYMxtxFZ6eYgerwyhr3s8iKfD+7Tk1BFg==

=/5Uc
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/