Cannot obtain IP, no network connection...

clay_statue

By clay_statue
in General Support

Recommended Posts

clay_statue Noob

clay_statue

Posted
Posted

I was in the middle of setting up my first Windows VM when unraid suddenly decided it doesn't want to play ball with my router and rejects DHCP.  I now get the default 169.xxx.xxx.xxx IP that occurs when it fails to obtain a working IP.  It was working fine the last few days and then decided to stop... go figure.

 

I can boot into my bare-metal Manjaro and use the eth0 without any issues, so I know it's not a hardware problem.  I've tried assigning a static ip in /boot/config/network.cfg (as well as turning on/off "bond" and "bridge" in every combination imaginable) but so far nothing is working.

 

 

fractaltower-diagnostics-20201106-0820.zip

Link to comment
Ford Prefect Experienced

Ford Prefect

Posted
Posted (edited)

...the system-log in the diagnostics zip indicates, that your system first received IP 192.168.0.100 and then, same time later got reset (like plug pulled & reseated) for several times where it got offered an IP in a different network range, from 192.168.1.250.

Then, again changed after some time and the rig was back on 192.168.0.100

 

...does this ring a bell of some sort?

What LANs are your DHCP servers sitting in and did you swap cables or trieg to passthrough the NIC while in use?

Also, the reported link speed is 100MBit/sec only....what quality cables are you using?

Edited by Ford Prefect
Link to comment
clay_statue Noob

clay_statue

Posted
  • Author
Posted (edited)

I am yet to have a wired connection to the internet for my tower.  As an interim solution I am using a wifi extender to provide an ethernet port for the tower.  I have 192.168.0.100 reserved on the router (static DHCP?) for unraid so it will always gets assigned the same IP whenever it boots.  I don't know why unraid is refusing it, I'll try removing the reserved IP and just let it assign whatever it wants to see if that helps...

 

This could be some something to do with my janky network setup, although it has been working fine for a few days (albeit slow).  I think I need to go buy a 100ft ethernet cable and plug unraid directly to the router temporarily and see if it calms down the DHCP shenanigans.  

 

ps... This seems to be the crux of the issue 

Nov  8 06:57:27 FractalTower dhcpcd[1919]: br0: soliciting a DHCP lease
Nov  8 06:57:27 FractalTower dhcpcd[1919]: br0: offered 192.168.0.180 from 192.168.0.1
Nov  8 06:57:32 FractalTower dhcpcd[1919]: br0: probing for an IPv4LL address
Nov  8 06:57:37 FractalTower dhcpcd[1919]: br0: using IPv4LL address 169.254.111.46

So the router and unraid are actually talking to each other, but for some reason br0 refuses the IP that it's offered and just assigns IPv4LL instead.  Why is br0 refusing the DHCP server?

Edited by clay_statue
Link to comment
clay_statue Noob

clay_statue

Posted
  • Author
Posted (edited)

Yea, okay it's not the janky network setup.  Even with a direct patch cable to the router it won't take an IP.


I don't know if what is happening is because dhcpcd is screwing up.  I checked /etc/dhcpcd.conf and swapped clientid for duid to see if that would help but it didn't.

 

I know there is an issue with linux and the realtek chipset of my mobo's onboard LAN port.  I solved it in Manjaro by blacklisting the driver r8169 in /etc/modprobe.d and installing an older driver r8125.  However I saw that unraid uses the r8125 driver and it was working so I am skeptical that this is the issue, but you never know...

 

Edit:

 

I created an unraid trial USB using the newest unraid 6.9 Beta and that worked.  The beta version has no trouble taking it's IP from the router and connecting to the internet like it should.  The challenge now is to figure out how to update unraid on my existing flash drive without a working network interface.  Or rebuild my system from scratch using the new trial USB and adding existing array to the new system without clearing them for the new arry....

Edited by clay_statue
Link to comment
itimpi Grand Master

itimpi

Posted
Posted

To update a USB drive manually it is only a case of copying all the bz* type files from e target release (which you seem to have a copy of on your trial USB drive) overwriting the ones already present.    Before doing so take a backup of the current files so you can easily revert to the current release should that be required for any reason.

Link to comment
Ford Prefect Experienced

Ford Prefect

Posted
Posted (edited)
13 hours ago, clay_statue said:

I am yet to have a wired connection to the internet for my tower.  As an interim solution I am using a wifi extender to provide an ethernet port for the tower.  I have 192.168.0.100 reserved on the router (static DHCP?) for unraid so it will always gets assigned the same IP whenever it boots.  I don't know why unraid is refusing it, I'll try removing the reserved IP and just let it assign whatever it wants to see if that helps...

 

This could be some something to do with my janky network setup, although it has been working fine for a few days (albeit slow).  I think I need to go buy a 100ft ethernet cable and plug unraid directly to the router temporarily and see if it calms down the DHCP shenanigans.  

 

ps... This seems to be the crux of the issue 


Nov  8 06:57:27 FractalTower dhcpcd[1919]: br0: soliciting a DHCP lease
Nov  8 06:57:27 FractalTower dhcpcd[1919]: br0: offered 192.168.0.180 from 192.168.0.1
Nov  8 06:57:32 FractalTower dhcpcd[1919]: br0: probing for an IPv4LL address
Nov  8 06:57:37 FractalTower dhcpcd[1919]: br0: using IPv4LL address 169.254.111.46

So the router and unraid are actually talking to each other, but for some reason br0 refuses the IP that it's offered and just assigns IPv4LL instead.  Why is br0 refusing the DHCP server?

 

That problem is not to be seen in the diagnostics you posted above.

The rig got offered and accepted DHCP IPs from two different networks in a row...see below at 06:58:27 (192.168.0.100) - 07:06:52 (192.168.1.128) - 07:09:00(192.168.0.250)

Your Router or an intermediate (maybe your WLAN-Client-Adapter) offered these two leases from different networks and the NIC (driver & kernel) accepted it just fine.

Wether the beta or a newly / empty network config did help here, I cannot say...I have no experience with RT-Nics ... just see driver isues all over the place here in the forums for RT based NICs...yours seems to be a 2.5G model with downward compatibility, based on what ethertool reports. 

Nov  6 06:58:21 FractalTower kernel: r8125: eth0: link up
Nov  6 06:58:22 FractalTower dhcpcd[1935]: br0: carrier acquired
Nov  6 06:58:22 FractalTower kernel: bond0: link status definitely up for interface eth0, 100 Mbps full duplex
Nov  6 06:58:22 FractalTower kernel: bond0: making interface eth0 the new active one
Nov  6 06:58:22 FractalTower kernel: device eth0 entered promiscuous mode
Nov  6 06:58:22 FractalTower kernel: bond0: first active interface up!
Nov  6 06:58:22 FractalTower kernel: br0: port 1(bond0) entered blocking state
Nov  6 06:58:22 FractalTower kernel: br0: port 1(bond0) entered forwarding state
Nov  6 06:58:22 FractalTower dhcpcd[1935]: br0: soliciting a DHCP lease
Nov  6 06:58:22 FractalTower dhcpcd[1935]: br0: offered 192.168.0.100 from 192.168.0.1
Nov  6 06:58:22 FractalTower dhcpcd[1935]: br0: probing address 192.168.0.100/24
Nov  6 06:58:27 FractalTower dhcpcd[1935]: br0: leased 192.168.0.100 for infinity
Nov  6 06:58:27 FractalTower dhcpcd[1935]: br0: adding route to 192.168.0.0/24
Nov  6 06:58:27 FractalTower dhcpcd[1935]: br0: adding default route via 192.168.0.1
Nov  6 06:58:27 FractalTower dhcpcd[1935]: forked to background, child pid 1991
Nov  6 06:58:27 FractalTower rc.inet1: ip link set br0 up
---[...]---
Nov  6 07:06:52 FractalTower kernel: r8125: eth0: link down
Nov  6 07:06:52 FractalTower kernel: bond0: link status definitely down for interface eth0, disabling it
Nov  6 07:06:52 FractalTower kernel: device eth0 left promiscuous mode
Nov  6 07:06:52 FractalTower kernel: bond0: now running without any active interface!
Nov  6 07:06:52 FractalTower kernel: br0: port 1(bond0) entered disabled state
Nov  6 07:06:53 FractalTower dhcpcd[1991]: br0: carrier lost
Nov  6 07:06:53 FractalTower avahi-daemon[5077]: Withdrawing address record for 192.168.0.100 on br0.
Nov  6 07:06:53 FractalTower dhcpcd[1991]: br0: deleting route to 192.168.0.0/24
Nov  6 07:06:53 FractalTower dhcpcd[1991]: br0: deleting default route via 192.168.0.1
Nov  6 07:06:53 FractalTower avahi-daemon[5077]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.0.100.
Nov  6 07:06:53 FractalTower avahi-daemon[5077]: Interface br0.IPv4 no longer relevant for mDNS.
Nov  6 07:06:54 FractalTower ntpd[2052]: Deleting interface #1 br0, 192.168.0.100#123, interface stats: received=58, sent=59, dropped=0, active_time=507 secs
Nov  6 07:06:54 FractalTower ntpd[2052]: 216.239.35.12 local addr 192.168.0.100 -> <null>
Nov  6 07:06:54 FractalTower ntpd[2052]: 216.239.35.8 local addr 192.168.0.100 -> <null>
Nov  6 07:06:54 FractalTower ntpd[2052]: 216.239.35.4 local addr 192.168.0.100 -> <null>
Nov  6 07:06:54 FractalTower ntpd[2052]: 216.239.35.0 local addr 192.168.0.100 -> <null>
Nov  6 07:07:03 FractalTower kernel: r8125: eth0: link up
Nov  6 07:07:03 FractalTower dhcpcd[1991]: br0: carrier acquired
Nov  6 07:07:03 FractalTower kernel: bond0: link status definitely up for interface eth0, 100 Mbps full duplex
Nov  6 07:07:03 FractalTower kernel: bond0: making interface eth0 the new active one
Nov  6 07:07:03 FractalTower kernel: device eth0 entered promiscuous mode
Nov  6 07:07:03 FractalTower kernel: bond0: first active interface up!
Nov  6 07:07:03 FractalTower kernel: br0: port 1(bond0) entered blocking state
Nov  6 07:07:03 FractalTower kernel: br0: port 1(bond0) entered forwarding state
Nov  6 07:07:03 FractalTower dhcpcd[1991]: br0: rebinding lease of 192.168.0.100
Nov  6 07:07:03 FractalTower dhcpcd[1991]: br0: NAK: from 192.168.1.250
Nov  6 07:07:03 FractalTower dhcpcd[1991]: br0: soliciting a DHCP lease
Nov  6 07:07:03 FractalTower dhcpcd[1991]: br0: offered 192.168.1.128 from 192.168.1.250
Nov  6 07:07:03 FractalTower dhcpcd[1991]: br0: probing address 192.168.1.128/24
Nov  6 07:07:08 FractalTower dhcpcd[1991]: br0: leased 192.168.1.128 for 60 seconds
Nov  6 07:07:08 FractalTower avahi-daemon[5077]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.128.
Nov  6 07:07:08 FractalTower avahi-daemon[5077]: New relevant interface br0.IPv4 for mDNS.
Nov  6 07:07:08 FractalTower dhcpcd[1991]: br0: adding route to 192.168.1.0/24
Nov  6 07:07:08 FractalTower dhcpcd[1991]: br0: adding default route via 192.168.1.250
Nov  6 07:07:08 FractalTower avahi-daemon[5077]: Registering new address record for 192.168.1.128 on br0.IPv4.
Nov  6 07:07:09 FractalTower ntpd[2052]: Listen normally on 3 br0 192.168.1.128:123
Nov  6 07:07:09 FractalTower ntpd[2052]: new interface(s) found: waking up resolver
Nov  6 07:07:38 FractalTower dhcpcd[1991]: br0: dhcp_sendudp: Network is unreachable
Nov  6 07:07:54 FractalTower kernel: r8125: eth0: link down
Nov  6 07:07:54 FractalTower kernel: bond0: link status definitely down for interface eth0, disabling it
Nov  6 07:07:54 FractalTower kernel: device eth0 left promiscuous mode
Nov  6 07:07:54 FractalTower kernel: bond0: now running without any active interface!
Nov  6 07:07:54 FractalTower kernel: br0: port 1(bond0) entered disabled state
Nov  6 07:07:55 FractalTower dhcpcd[1991]: br0: carrier lost
Nov  6 07:07:55 FractalTower avahi-daemon[5077]: Withdrawing address record for 192.168.1.128 on br0.
Nov  6 07:07:55 FractalTower avahi-daemon[5077]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.128.
Nov  6 07:07:55 FractalTower dhcpcd[1991]: br0: deleting route to 192.168.1.0/24
Nov  6 07:07:55 FractalTower avahi-daemon[5077]: Interface br0.IPv4 no longer relevant for mDNS.
Nov  6 07:07:55 FractalTower dhcpcd[1991]: br0: deleting default route via 192.168.1.250
Nov  6 07:07:57 FractalTower ntpd[2052]: Deleting interface #3 br0, 192.168.1.128#123, interface stats: received=0, sent=4, dropped=0, active_time=48 secs
Nov  6 07:07:57 FractalTower ntpd[2052]: 216.239.35.0 local addr 192.168.1.128 -> <null>
Nov  6 07:07:57 FractalTower ntpd[2052]: 216.239.35.4 local addr 192.168.1.128 -> <null>
Nov  6 07:07:57 FractalTower ntpd[2052]: 216.239.35.8 local addr 192.168.1.128 -> <null>
Nov  6 07:07:57 FractalTower ntpd[2052]: 216.239.35.12 local addr 192.168.1.128 -> <null>
Nov  6 07:08:05 FractalTower kernel: r8125: eth0: link up
Nov  6 07:08:05 FractalTower dhcpcd[1991]: br0: carrier acquired
Nov  6 07:08:05 FractalTower kernel: bond0: link status definitely up for interface eth0, 100 Mbps full duplex
Nov  6 07:08:05 FractalTower kernel: bond0: making interface eth0 the new active one
Nov  6 07:08:05 FractalTower kernel: device eth0 entered promiscuous mode
Nov  6 07:08:05 FractalTower kernel: bond0: first active interface up!
Nov  6 07:08:05 FractalTower kernel: br0: port 1(bond0) entered blocking state
Nov  6 07:08:05 FractalTower kernel: br0: port 1(bond0) entered forwarding state
Nov  6 07:08:06 FractalTower dhcpcd[1991]: br0: rebinding lease of 192.168.1.128
Nov  6 07:08:06 FractalTower dhcpcd[1991]: br0: probing address 192.168.1.128/24
Nov  6 07:08:11 FractalTower dhcpcd[1991]: br0: leased 192.168.1.128 for 60 seconds
Nov  6 07:08:11 FractalTower dhcpcd[1991]: br0: adding route to 192.168.1.0/24
Nov  6 07:08:11 FractalTower dhcpcd[1991]: br0: adding default route via 192.168.1.250
Nov  6 07:08:11 FractalTower avahi-daemon[5077]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.128.
Nov  6 07:08:11 FractalTower avahi-daemon[5077]: New relevant interface br0.IPv4 for mDNS.
Nov  6 07:08:11 FractalTower avahi-daemon[5077]: Registering new address record for 192.168.1.128 on br0.IPv4.
Nov  6 07:08:12 FractalTower ntpd[2052]: Listen normally on 4 br0 192.168.1.128:123
Nov  6 07:08:12 FractalTower ntpd[2052]: new interface(s) found: waking up resolver
Nov  6 07:08:41 FractalTower dhcpcd[1991]: br0: dhcp_sendudp: Network is unreachable
Nov  6 07:08:43 FractalTower kernel: r8125: eth0: link down
Nov  6 07:08:43 FractalTower kernel: bond0: link status definitely down for interface eth0, disabling it
Nov  6 07:08:43 FractalTower kernel: device eth0 left promiscuous mode
Nov  6 07:08:43 FractalTower kernel: bond0: now running without any active interface!
Nov  6 07:08:43 FractalTower kernel: br0: port 1(bond0) entered disabled state
Nov  6 07:08:44 FractalTower dhcpcd[1991]: br0: carrier lost
Nov  6 07:08:44 FractalTower avahi-daemon[5077]: Withdrawing address record for 192.168.1.128 on br0.
Nov  6 07:08:44 FractalTower dhcpcd[1991]: br0: deleting route to 192.168.1.0/24
Nov  6 07:08:44 FractalTower avahi-daemon[5077]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.128.
Nov  6 07:08:44 FractalTower dhcpcd[1991]: br0: deleting default route via 192.168.1.250
Nov  6 07:08:44 FractalTower avahi-daemon[5077]: Interface br0.IPv4 no longer relevant for mDNS.
Nov  6 07:08:46 FractalTower ntpd[2052]: Deleting interface #4 br0, 192.168.1.128#123, interface stats: received=0, sent=4, dropped=0, active_time=34 secs
Nov  6 07:08:46 FractalTower ntpd[2052]: 216.239.35.0 local addr 192.168.1.128 -> <null>
Nov  6 07:08:46 FractalTower ntpd[2052]: 216.239.35.4 local addr 192.168.1.128 -> <null>
Nov  6 07:08:46 FractalTower ntpd[2052]: 216.239.35.8 local addr 192.168.1.128 -> <null>
Nov  6 07:08:46 FractalTower ntpd[2052]: 216.239.35.12 local addr 192.168.1.128 -> <null>
Nov  6 07:08:55 FractalTower kernel: r8125: eth0: link up
Nov  6 07:08:55 FractalTower dhcpcd[1991]: br0: carrier acquired
Nov  6 07:08:55 FractalTower kernel: bond0: link status definitely up for interface eth0, 100 Mbps full duplex
Nov  6 07:08:55 FractalTower kernel: bond0: making interface eth0 the new active one
Nov  6 07:08:55 FractalTower kernel: device eth0 entered promiscuous mode
Nov  6 07:08:55 FractalTower kernel: bond0: first active interface up!
Nov  6 07:08:55 FractalTower kernel: br0: port 1(bond0) entered blocking state
Nov  6 07:08:55 FractalTower kernel: br0: port 1(bond0) entered forwarding state
Nov  6 07:08:55 FractalTower dhcpcd[1991]: br0: rebinding lease of 192.168.1.128
Nov  6 07:08:55 FractalTower dhcpcd[1991]: br0: NAK: wrong network from 192.168.0.1
Nov  6 07:08:55 FractalTower dhcpcd[1991]: br0: message: wrong network
Nov  6 07:08:55 FractalTower dhcpcd[1991]: br0: soliciting a DHCP lease
Nov  6 07:08:55 FractalTower dhcpcd[1991]: br0: offered 192.168.0.100 from 192.168.0.1
Nov  6 07:08:55 FractalTower dhcpcd[1991]: br0: probing address 192.168.0.100/24
Nov  6 07:09:00 FractalTower dhcpcd[1991]: br0: leased 192.168.0.100 for infinity
Nov  6 07:09:00 FractalTower avahi-daemon[5077]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.100.
Nov  6 07:09:00 FractalTower avahi-daemon[5077]: New relevant interface br0.IPv4 for mDNS.
Nov  6 07:09:00 FractalTower dhcpcd[1991]: br0: adding route to 192.168.0.0/24
Nov  6 07:09:00 FractalTower dhcpcd[1991]: br0: adding default route via 192.168.0.1
Nov  6 07:09:00 FractalTower avahi-daemon[5077]: Registering new address record for 192.168.0.100 on br0.IPv4.
Nov  6 07:09:01 FractalTower ntpd[2052]: Listen normally on 5 br0 192.168.0.100:123
Nov  6 07:09:01 FractalTower ntpd[2052]: new interface(s) found: waking up resolver
Nov  6 07:09:20 FractalTower webGUI: Successful login user root from 192.168.0.101

 

Edited by Ford Prefect
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing