Have a strange problem. Using a Intel N 2230 and connecting 802.11n to a router, I lose access to the network at various times. I'm still shown as connected but I can't reach any part of the internal network or external internet etc. Performed a packet capture of the moment it drops, traffic doesn't seem to strange to me (albeit I'm new to this) apart from a series of packets with SACK_PERM=1. (??) Anyone able to take a look at the attached and see what's happening? I'm starting to think its a driver issue.... Packet Capture http://sdrv.ms/16uKhsb thanks Richard asked 24 Aug '13, 14:05  rcarter15 |
One Answer:
Fram 26 contains the last inbound packet coming in from your router. After that, only outbound packets were traced, among those even ARP request which should trigger an immediate reply from your default gateway. Assuming that your Win7 is the only one suffering and the other users on the WLAN are still happily communicating at this time, you're probably with your guess. dumpcap doesn't trace the lower WLAN protocols though to find out who is failing. answered 25 Aug '13, 10:24  mrEEde |
Thanks mrEEde, I've been playing with this all day.
I have a second Dell laptop which runs a different wireless card, so far this does not seem to display the same problem.
I have also now installed linux on the machine with the issue.
I'd start to think its hardware related, except 802.11g works fine and stable. Its only when I switch to the 802.11n that the problems appear (even with forcing 20mhz channel)
I've dropped a mail to dell but that might take some time ;-)
thanks for checking I hadn't missed anything in the packet capture.
Richard
It'll do that if you're capturing in monitor mode, which you can do on OS X, Linux (although you might have to use airmon-ng, rather than the Wireshark checkbox or TShark/dumpcap/tcpdump
-Iflag, to turn monitor mode on), and *BSD, but which you can't do on Windows. Turning on monitor mode on a Wi-Fi adapter might disassociate it from the network, so you might need a separate machine from the machine having the problems - and that machine will obviously need 802.11n support on its Wi-Fi adapter. For protocols above the 802.11 layer, and possibly 802.11 management frames, you may have to worry about decrypting protected network (WEP or WPA/WPA2) traffic.I can fire up linux on my work laptop, which is also 802.11n and working fine.
I'll run a capture from there and see what happens.
I'll repost it once I get a failure. ;-)
thanks
Richard