Re: wi problem with message > 7400 bytes
On Thu, 30 Oct 2003, Lars Eggert wrote: > Daniel Eischen wrote: > >> > >>Could you post a tcpdump for each case? I wonder if this is related to a > >>fragmentation issue I've seen in the past. > > > > 22:46:43.513038 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52198:[EMAIL > > PROTECTED]) > > 22:46:48.522475 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52199:[EMAIL > > PROTECTED]) > > 22:46:53.532018 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52200:[EMAIL > > PROTECTED]) > > 22:46:58.541178 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52201:[EMAIL > > PROTECTED]) > > 22:47:03.553048 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52202:[EMAIL > > PROTECTED]) > > 22:47:08.568862 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52203:[EMAIL > > PROTECTED]) > > 22:47:13.583328 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52204:[EMAIL > > PROTECTED]) > > 22:47:18.578512 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52205:[EMAIL > > PROTECTED]) > > 22:47:23.609098 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52206:[EMAIL > > PROTECTED]) > > 22:47:28.597680 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52207:[EMAIL > > PROTECTED]) > > 22:47:33.607059 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52208:[EMAIL > > PROTECTED]) > > It's not what I've seen in the past - but also pretty strange! Only the > first fragment seems to be received. Wonder what happened to the other > fragments... I guess the problem was with the access point. Once I swapped it with a Linksys WAP-11, it worked. For future reference, the bad access point was a Dell TrueMobile-branded Intel 1170 Wireless Base Station (Model WLGW2011). -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi problem with message > 7400 bytes
On Thu, 30 Oct 2003, Lars Eggert wrote: > Daniel Eischen wrote: > >> > >>Could you post a tcpdump for each case? I wonder if this is related to a > >>fragmentation issue I've seen in the past. > > > > 22:46:43.513038 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52198:[EMAIL > > PROTECTED]) > > 22:46:48.522475 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52199:[EMAIL > > PROTECTED]) > > 22:46:53.532018 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52200:[EMAIL > > PROTECTED]) > > 22:46:58.541178 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52201:[EMAIL > > PROTECTED]) > > 22:47:03.553048 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52202:[EMAIL > > PROTECTED]) > > 22:47:08.568862 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52203:[EMAIL > > PROTECTED]) > > 22:47:13.583328 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52204:[EMAIL > > PROTECTED]) > > 22:47:18.578512 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52205:[EMAIL > > PROTECTED]) > > 22:47:23.609098 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52206:[EMAIL > > PROTECTED]) > > 22:47:28.597680 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52207:[EMAIL > > PROTECTED]) > > 22:47:33.607059 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52208:[EMAIL > > PROTECTED]) > > It's not what I've seen in the past - but also pretty strange! Only the > first fragment seems to be received. Wonder what happened to the other > fragments... > > If you tcpdump on gpz, does the output look the same? Also, you may want I'll try that tomorrow. gpz is a Sun Solaris 9 box at work, but before you say "try another BSD box", I already did. I tried 2 other FreeBSD boxes in place of gpz and I had the same results. > to run the tcpdump without a filter (if you don't do this already) to > see if the other fragments show up as corrputed frames or something. > > (As an aside, fragmentation on a lossy link compounds throughput issues, > but of course you know that already.) Everything is behind Cisco 10/100 switches and doing 10/100 full duplex except for the laptop (vespa) which is through a Dell TrueMobile wireless access point. The access point is connected to a switch and is about 10 feet away from the laptop. I tried this test at home with a different setup: orion - laptop with D-Link DWL-650H PC-Card (wi) sirius - FreeBSD current box with em interface Linksys WRT-54g router/access point with builtin 10/100 switch There is no other traffic on this network; orion and sirius are standalone. sirius is wired to a 10/100 port in the router/access point and is at 100 full-duplex. Repeating the same test lets me send messages up to 25152 bytes in length, much better than 7400. This seems to be about the same limit I hit in VxWorks (which supposedly has the BSD 4.4 IP stack). I'll see if I can get my hands on a different access point at work to see if that makes a difference. Here's the tcpdump from the above setup with message size 25153: 05:27:59.632708 sirius.49245 > orion-home.12345: udp 25153 (frag 19970:[EMAIL PROTECTED]) 05:27:59.815829 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:00.023248 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:00.216317 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:00.404066 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:00.583116 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:00.777315 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:00.950056 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:01.129616 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:01.327645 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:01.560564 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:01.769612 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:01.945923 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:02.128897 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:02.309202 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:02.514941 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:02.731612 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:02.907988 sirius > orion-home: udp (frag 19970:[EMAIL PROTECTED]) 05:28:07.982121 sirius.49245 > orion-home.12345: udp 25153 (frag 20226:[EMAIL PROTECTED]) 05:28:08.150171 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED]) 05:28:08.357960 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED]) 05:28:08.551270 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED]) 05:28:08.754906 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED]) 05:28:08.953891 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED]) 05:28:09.145286 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED]) 05:28:09.365111 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED]) 05:28:09.577964 sirius > orion-home: udp (frag 20226:[EMAIL PROTECTED
Re: wi problem with message > 7400 bytes
Daniel Eischen wrote: Could you post a tcpdump for each case? I wonder if this is related to a fragmentation issue I've seen in the past. 22:46:43.513038 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52198:[EMAIL PROTECTED]) 22:46:48.522475 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52199:[EMAIL PROTECTED]) 22:46:53.532018 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52200:[EMAIL PROTECTED]) 22:46:58.541178 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52201:[EMAIL PROTECTED]) 22:47:03.553048 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52202:[EMAIL PROTECTED]) 22:47:08.568862 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52203:[EMAIL PROTECTED]) 22:47:13.583328 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52204:[EMAIL PROTECTED]) 22:47:18.578512 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52205:[EMAIL PROTECTED]) 22:47:23.609098 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52206:[EMAIL PROTECTED]) 22:47:28.597680 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52207:[EMAIL PROTECTED]) 22:47:33.607059 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52208:[EMAIL PROTECTED]) It's not what I've seen in the past - but also pretty strange! Only the first fragment seems to be received. Wonder what happened to the other fragments... If you tcpdump on gpz, does the output look the same? Also, you may want to run the tcpdump without a filter (if you don't do this already) to see if the other fragments show up as corrputed frames or something. (As an aside, fragmentation on a lossy link compounds throughput issues, but of course you know that already.) Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: wi problem with message > 7400 bytes
On Thu, 30 Oct 2003, Lars Eggert wrote: > Daniel Eischen wrote: > > > Greetings, > > > > I'm having a problem receiving UDP messages over a wi interface: > > > > wi1: at port 0x180-0x1bf irq 11 function 0 > > config 1 on pccard0 > > wi1: 802.11 address: 00:02:2d:4a:d8:7d > > wi1: using Lucent Technologies, WaveLAN/IEEE > > wi1: Lucent Firmware: Station (6.10.1) > > wi1: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > > > (wi0 is also a 'Dell TrueMobile 1150 Series PC Card' in > > a mini-PCI card, but hangs the system when you try and > > configure it -- so it obviously isn't configured in this > > set up.) > > > > I have a small program that does a trivial UDP test: > > > > http://people.freebsd.org/~deischen/udptest.c > > > > My results show that: > > > > o Receiving large (> 7400 bytes) messages does not work. > > > > o Sending large messages works. > > > > o Sending & receiving large messages over a wired > > interface (dc, fxp, etc) works. > > > > Am I suppose to be able to receive UDP messages larger > > than 7400 bytes over the air? > > Could you post a tcpdump for each case? I wonder if this is related to a > fragmentation issue I've seen in the past. 22:46:43.513038 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52198:[EMAIL PROTECTED]) 22:46:48.522475 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52199:[EMAIL PROTECTED]) 22:46:53.532018 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52200:[EMAIL PROTECTED]) 22:46:58.541178 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52201:[EMAIL PROTECTED]) 22:47:03.553048 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52202:[EMAIL PROTECTED]) 22:47:08.568862 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52203:[EMAIL PROTECTED]) 22:47:13.583328 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52204:[EMAIL PROTECTED]) 22:47:18.578512 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52205:[EMAIL PROTECTED]) 22:47:23.609098 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52206:[EMAIL PROTECTED]) 22:47:28.597680 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52207:[EMAIL PROTECTED]) 22:47:33.607059 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52208:[EMAIL PROTECTED]) In this case, I ran: gpz $ udptest -D -c -a 192.168.3.31 -m 7393 vespa $ udptest -D vespa (192.168.3.31) is the affected notebook with wi interface. I ran udptest as the server, so all it is doing is trying to receive a message. The tcpdump was done on vespa. The kernel is current from Monday or Tuesdays sources, and I had the same problem with a kernel from August. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi problem with message > 7400 bytes
Daniel Eischen wrote: Greetings, I'm having a problem receiving UDP messages over a wi interface: wi1: at port 0x180-0x1bf irq 11 function 0 config 1 on pccard0 wi1: 802.11 address: 00:02:2d:4a:d8:7d wi1: using Lucent Technologies, WaveLAN/IEEE wi1: Lucent Firmware: Station (6.10.1) wi1: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps (wi0 is also a 'Dell TrueMobile 1150 Series PC Card' in a mini-PCI card, but hangs the system when you try and configure it -- so it obviously isn't configured in this set up.) I have a small program that does a trivial UDP test: http://people.freebsd.org/~deischen/udptest.c My results show that: o Receiving large (> 7400 bytes) messages does not work. o Sending large messages works. o Sending & receiving large messages over a wired interface (dc, fxp, etc) works. Am I suppose to be able to receive UDP messages larger than 7400 bytes over the air? Could you post a tcpdump for each case? I wonder if this is related to a fragmentation issue I've seen in the past. Thanks, Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
wi problem with message > 7400 bytes
Greetings, I'm having a problem receiving UDP messages over a wi interface: wi1: at port 0x180-0x1bf irq 11 function 0 config 1 on pccard0 wi1: 802.11 address: 00:02:2d:4a:d8:7d wi1: using Lucent Technologies, WaveLAN/IEEE wi1: Lucent Firmware: Station (6.10.1) wi1: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps (wi0 is also a 'Dell TrueMobile 1150 Series PC Card' in a mini-PCI card, but hangs the system when you try and configure it -- so it obviously isn't configured in this set up.) I have a small program that does a trivial UDP test: http://people.freebsd.org/~deischen/udptest.c My results show that: o Receiving large (> 7400 bytes) messages does not work. o Sending large messages works. o Sending & receiving large messages over a wired interface (dc, fxp, etc) works. Am I suppose to be able to receive UDP messages larger than 7400 bytes over the air? To run the above test: # On one machine, run it as a server (it just echoes # the messages back to the client). # $ udptest -D # On the wireless machine, run it as a client (it # sends a message to the server and waits for the # echoed response). # $ udptest -D -c -a -m If I set message size to 7392 (plus an 8 byte header in my message = 7400), everything works. Anything higher and I never receive the response. Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
