Jump to content

Driver for Realtek's RTL810x Fast Ethernet Series


179 posts in this topic

Recommended Posts

Looks ok! The only thing which makes me wonder is that ASPM is enabled which may cause power management issues on some machines but as DHCP is working, it's obvious that there is inbound and outbound traffic on the interface.

 

Mieze

I'm unable to disable ASPM in my BIOS.

May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: RTL8101E: (Chipset 0) at 0x<ptr>, 70:5a: f:19:94:5c

 

Chipset 0 is correct and  "at 0x<ptr>" is normal?

 

If it's correct, where is the error? I tried every kext related to RTL8101E and only your kext seems to work, but no luck...

 

If I use nullcpupowermanagement.kext, maybe it works?

I'm unable to disable ASPM in my BIOS.

May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: RTL8101E: (Chipset 0) at 0x<ptr>, 70:5a: f:19:94:5c

 

Chipset 0 is correct and  "at 0x<ptr>" is normal?

 

If it's correct, where is the error? I tried every kext related to RTL8101E and only your kext seems to work, but no luck...

There is no indication of a driver issue. In case of an ASPM related failure, the link would constantly go up and down (every few seconds) without ever acquiring an IP address.

 

Mieze

  • 2 weeks later...
  • 2 weeks later...

Ok, thanks for trying to help me.... good night....

mate, I'm facing the exact same issue. My chipset is RTL8136. This was the only driver that worked. I am also getting IP and everything, but no internet. Were you able to find any solution?

  • 2 months later...
  • 1 month later...

mate, I'm facing the exact same issue. My chipset is RTL8136. This was the only driver that worked. I am also getting IP and everything, but no internet. Were you able to find any solution?

Did you manage to fix the issue somehow? Same issue over here... 0x<ptr>, IP but no WAN connectivity

  • 2 weeks later...

Hi,

I am facing exactly the same problem. The driver looks to work perfectly, DHCP gives the right IP and the rest of parameters but no connectivity to internet.

My hardware: HP Pavilion 17-g072, i7-5500U @2.4GHz, Intel HD 5500, 12 GB RAM, WiFi on USB Archer_T2U. Working systems:

Win10, Linux Ubuntu, El Capitan and macOS Sierra.

Of course, The Realtek card works perfectly with Win10 and Ubuntu.

 

Is it something with HP laptops, as I can see people with these machines mostly report this issue.

 

Regards to all,

Henryk

  • 3 months later...

I've been having a hard time getting this card to work. I installed the lnx2mac driver v 0.90 and nothing is showing under ethernet.

Unfortunately I can't help you as this is a PCI card but the driver only supports PCIe devices. Sorry!

 

Mieze

No problem man, I won't be needing this pci NIC card anymore since I found a newer kext to support my lan ports on my xw8600 workstation optimized for El Capitan. My issue was when I wake up from sleep, I'd lose Internet access.

  • 3 weeks later...

mate, I'm facing the exact same issue. My chipset is RTL8136. This was the only driver that worked. I am also getting IP and everything, but no internet. Were you able to find any solution?

 

I just wanted to let you know that I'm working on an update of the driver which supports newer hardware and is optimized for Sierra and El Capitan.

 

Mieze  :cat:

 

Hello, I'm also using this with 8136 chipset and have exactly the same issue, everything recognised totally fine and all working except internet! Not a huge deal for me as I seldom use ethernet and mainly wanted it working in order to use the App Store, but I look forward to a new version of this anyway and will test as soon as it's available.

 

Thanks for all the hard work Mieze, much appreciated :)

  • 3 weeks later...

As already announced weeks ago, here is the first development version 2.0.0d3 of the driver. Among several changes I added:

  • Support for Apple's private driver interface in order to resolve stability issues under heavy load and with virtualization software.
  • Support for polled receive mode.
  • Also supports RTL8107E which can be found on a number of new boards/notebooks.

Please take into account that this is new driver which is still under development and might have bugs, cause kernel panics, etc so that you should be prepared to recover from these situations.

 

Special thanks to user p569 for testing the driver on his RTL8107!  :thumbsup_anim:

 

Good luck testing!  :cat:

 

Mieze

 

RealtekRTL8100-V2.0.0d3.zip

Thank you, Mieze, for your kind words

and making RTL8107 to work on my laptop

I pay my highest respect for your work on the driver

Great work!

p569

:construction::startreck:

Will the new driver work with RTL8101/2/3 Family Ethernet NIC

Vendor Realtek PCIe GBE Family Controller.

This is a laptop

(Cheked by HWiNFO64)

 

On Windows 8.1 x64 I have Driver installed for RealTek PCIe FE Family Controller and it works fine.

 

I want to install El Capitan 10.11.6 on this laptop and want to confirm if the new update resolves the previous issues

Thank you very, very much Mieze. The new version of the driver works fantastically.

Fabulous work.

Many thanks, again.

Henryk

 

 

My hardware: HP Pavilion 17-g072, i7-5500U @2.4GHz, Intel HD 5500, 12 GB RAM, WiFi on USB Archer_T2U.

  • 2 weeks later...
  • 2 weeks later...
  • 3 weeks later...

Mize

 

When waking up or disconnecting and reconnecting the cable, the dhcp does not work , getting ip 169.254.x.x

 

After this, unloading and loading the kext, everything back normal operation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff81170de000, 40:ca:65:01:70:40
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet
 

 

Mize

 

When waking up or disconnecting and reconnecting the cable, the dhcp does not work , getting ip 169.254.x.x

 

After this, unloading and loading the kext, everything back normal operation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff81170de000, 40:ca:65:01:70:40
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
 kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet
 

 

Please post a kernel log extract showing a cycle where you unplugged and replugged the cable.

Hello mieze, Thanks for your reply

I removed the timestamp from the logs, to make it more readable

 

come on

 

Loading the kext without the cable connected
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff812e4c7000, 00:6a:9f:01:70:40
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
kernel[0]: en0: attached with 6 suspended link-layer multicast membership(s)
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
kernel[0]: en0: successfully restored 6 suspended link-layer multicast membership(s) (err=0)
Setting the tcpdump (sudo tcpdump -i en0 port 67 or port 68 -e -n or arp) and connecting the cable
 
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet

log fom tcpdump

ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
00:6a:9f:01:70:40, ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.104.68: BOOTP/DHCP, Reply, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
00:6a:9f:01:70:40, ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.104.68: BOOTP/DHCP, Reply, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.1.104 tell 192.168.1.1, length 46
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.1.104 tell 192.168.1.1, length 46
00:6a:9f:01:70:40, ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.104.68: BOOTP/DHCP, Reply, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
00:6a:9f:01:70:40, ethertype ARP (0x0806), length 60: Reply 192.168.1.1 is-at 3c:1e:04:61:73:dc, length 46
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
00:6a:9f:01:70:40, ethertype ARP (0x0806), length 60: Reply 192.168.1.1 is-at 3c:1e:04:61:73:dc, length 46
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.1.104, length 28
Ok, ip received and working
 
 
Disconnecting the cable  
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link down on en0

Reconnecting the cable

kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet

log from tcpdump

3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 169.254.195.12, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 169.254.195.12, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Probe 169.254.195.12, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 169.254.195.12, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 169.254.195.12, length 28
ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Announcement 169.254.195.12, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:6a:9f:01:70:40, length 300
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
3c:1e:04:61:73:dc, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.1 tell 192.168.1.104, length 28
The interface can not talk to the dhcp server
 
 

kextunload  kext

kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link down on en0

kextload kext

kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe ASPM support disabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RxPoll support enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 segmentation offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Version 2.0.0 using interrupt mitigate value 0x0. Please don't support tonymacx86.com!
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: RTL8106E: (Chipset 15) at 0x0xffffff812e4c9000, 00:6a:9f:01:70:40
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: MSI interrupt index: 1
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Already in power state 1.
kernel[0]: en0: attached with 4 suspended link-layer multicast membership(s)
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: No medium selected. Falling back to autonegotiation.
kernel[0]: en0: successfully restored 4 suspended link-layer multicast membership(s) (err=0)
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: EEE Advertise: 0x2, Link Partner Ability: 0x2
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: pollIntervalTime: 1000us
kernel[0]: (kernel) Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, energy-efficient-ethernet

Okay, everything normal again.
 
 
As I did the same procedure in linux and work normally, I discarded performing a better inspection of dhcp traffic with tcpdump.
Haaaa, I performed the tests with and without ipv6
 
Any idea ?
 
 
Tanks

@jalves: I've checked the driver's code again and found no evidence for a driver bug. I don't have hardware to test myself but as sleep/wake and link change detection are basic functions of a driver which have been thoroughly tested, it's hard to imagine a scenario in which a driver bug causing this behavior wouldn't have been found much earlier. That's why I'm not willing to believe in a driver bug until some user with the same chip confirms this issue.

 

Please check your BIOS settings and make sure that network boot, the UEFI network stack as well as any LAN related power management functions are disabled (in particular if there is any function to put the NIC into a low power state when the cable is disconnected). 

 

Mieze

@Mieze

 

 

I reviewed my settings and also did not find anything strange

 

Just for record

 

I test it on a Ubuntu 14.04LTS , 4.4.0-31 kernel, driver r8169 2.3LK-NAPI .  ( Realtek 8106E - 10EC, 8136 )

 

Tank you for your attention

×
×
  • Create New...