Paul Collins <paul@xxxxxxxxxxxxxxxxxxx> writes: > reinette chatre <reinette.chatre@xxxxxxxxx> writes: >>> When I say "packets > 250 bytes" I mean 250-byte packets as claimed by >>> "ping -s 222 mygateway": >>> >>> PING cornelius.lan (10.2.4.1) 222(250) bytes of data. >>> >>> The above will work, but "ping -s 223 cornelius" yields no replies. >> >> Are you saying this works before suspend, but not after resume? What do >> you usually do to get this working again? > > Yes, normally it works great; I can ping with packet sizes up to the > MTU. However, after suspend/resume and reassociation, "ping -s 223" or > greater does not work. I get replies with "-s 222" or less, > i.e. packets of 250 bytes or less. > > To get it working again I do "ifdown wlan0" followed by "ifup wlan0", > which does the equivalent of "ip set link wlan0 down/up" and applying > the network configuration. > > I will give the patch a shot when I get home. I thought at first that the patch had moved the problem from reliably reproducible to intermittently reproducible, but it looks like it was simply intermittently reproducible the whole time. So, no change with the patch applied. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
