I found solution for this issue, at least for my case: one has to set correct MAC-address before bringing up the interface.
On my board RTL8102E works without EEPROM, so MAC value is unpredictable. In many cases this random value has multicast bit set to 1. This fact breaks driver and (or) TCP stack operation: * r8169 reports that link is down * r8101 reports that link is OK, but Linux TCP stack ignores packets with multicast destination MAC Overall behavior of r8169 seems to be better than r8101's: second one sometimes stops to transceive packets (once per several hours of continuous TCP traffic, average load ~30Mbps down). In same conditions r8169 works without issues (or at least I think so? (c)). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1132156 Title: Realktek r8169 driver unrelaible with r8101/02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1132156/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
