Hello Everyone,

First post, so I might miss some stuff.

 

I had a perfectly fine running server for 2 years, and then a few months back I updated to 7.0.0 and could not reach the server anymore.

Currently debugging it and noticed that it is fine, but the network is just broken for some reason. I have a Realtek 8125 card (I know that they can be very annoying)

I got it to work for like 30min and did some docker image updates, but after a restart, it just broke again.

So far I deleted the network.cfg I dont have a network-rules.cfg My current network.cfg (I've already changed it like 30 times in the process of debugging) is:
IFNAME[0]="eth0"

PROTOCOL[0]="ipv4"

USE_DHCP[0]="no"

IPADDR[0]="192.168.178.48"

NETMASK[0]="255.255.255.0"

GATEWAY[0]="192.168.178.1"

DNS_SERVER1="8.8.8.8"

DNS_SERVER2="8.8.4.4"

 

It seems to me that it is just not able to connect to my router but my router (FritzBox) says that the server is online with the ip:192.168.178.48 which makes no sense to me.

Ping dosnt work it just errors with "Destiantion Host Unreachable"

I checked eth0 exist and does have the ip

 

I also tryed with DHCP but it just gets an invalid ip and is still not able to reach the router.

 

Just spend my weekend with this and am kind of out of idears would really appreachiate some help!

Best Regards,

Tim

homeserver-diagnostics-20250412-1304.zip

syslog

Edited April 12, 20251 yr by TimMueller

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

is this good?

Rename /boot/config/network.cfg to .bak and reboot, note that the LAN settings will go back to default DHCP, then post new diags.

There we go

homeserver-diagnostics-20250412-1317.zip network.cfg

NIC is getting an APIPA (internal) address, router is not assigning a valid address:

 

Apr 12 13:15:21 [1656]: br0: soliciting a DHCP lease
Apr 12 13:15:26 [1656]: br0: probing for an IPv4LL address
Apr 12 13:15:32 [1656]: br0: using IPv4LL address 169.254.237.119
Apr 12 13:15:32 [1656]: br0: adding route to 169.XXX.XXX.0/16

 

This usually means a router issue, or it's not properly connected to it.

 

 

Yes, that's my guess as well.

The thing is, I don't know what to do. The router settings worked before, basically just assigning a static IP to the server.
Already restarted it twice

 

Dont know how to check the connection else than just seeing that doesn't work.😅

 

Do you have an idea on what I could do here?

Assuming the NIC cable is connected correctly to the router, you can try rebooting the router first, if the same, do a factory reset to it, if still the same, try a different NIC.

 

 

Okay, tried the router restart again and for some reason it worked this time hope it stays this way
Thanks for the help!