Comment 25 for bug 1269883

Revision history for this message
Stéphane Gourichon (stephane-gourichon-lpad) wrote :

Summary: behavior is different in Wily, sometimes not working, sometimes working but fails on heavy traffic.

Done some test check booting a Asus n551 on Ubuntu 15.10 live (wily werewolf).

## First test : one-way link only?

First (sanity check / scientific control), tested integrated Ethernet port which works flawlessly.

With tested device (same Ethernet cable, cat 5e) at first try behavior seems to have improved compared with previous Ubuntu releases:
* ethernet auto-negociation is fast (like on previous kernels when it worked in USB2)
* mii-tool is fast (typical 0.05s) (like on previous kernels when it worked in USB2)
* few lines in dmesg (like on previous kernels when it worked in USB2)
* but DHCP does not complete

"tcpdump -n -i devicename" on both sides showed that packets sent by tested device are received on remote side but packets sent from remote side are not received by device (even ARP packets).

Tried reversing cable just in case, behavior is the same. Just plugging the same cable to integrated Ethernet of same machine instead of tested device, everything works.

Tested with another cable, same result.

## Subsequent tests: works then fails on heavy traffic

* Plugged the device in another USB port. Everything seemed to worked.
* Then tested again in the initial port. Worked again. Then after a moment (testing with dd anc nc), same problem (device received no packet).
* Unplugging then plugging the device -> no longer creates ethernet device enx(encodedmacaddress)
* Unplugging then plugging the device -> works again but load test using dd and nc quickly comes to the same problem.

Conclusion: behavior is different in Wiley, sometimes not working, sometimes working. Problem seems different from previous ones.

I attached part of dmesg. Promiscuous mode is when I used tcpdump.