wi problem with message > 7400 bytes

[Daniel Eischen]

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:1480 at 0+)
> > 22:46:48.522475 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52199:1480 at 0+)
> > 22:46:53.532018 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52200:1480 at 0+)
> > 22:46:58.541178 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52201:1480 at 0+)
> > 22:47:03.553048 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52202:1480 at 0+)
> > 22:47:08.568862 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52203:1480 at 0+)
> > 22:47:13.583328 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52204:1480 at 0+)
> > 22:47:18.578512 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52205:1480 at 0+)
> > 22:47:23.609098 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52206:1480 at 0+)
> > 22:47:28.597680 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52207:1480 at 0+)
> > 22:47:33.607059 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52208:1480 at 0+)
> 
> 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