I installed ipfire on a fresh apu2 Hardware using 2.25 Update 150, then later Updated to 151.
Dhcpcd on the apu2 is used to get a Dynamic ip from my internet router. This Works fine until After some hours, when ipfire tries to Renew the lease…
I tried Wired end Wireless Connections between ipfire end the Internet Router, to excluded many Potential HW problems in any level.
Lease Renewal is normally 10days, so Why so frequent Problems?
Here is the log:
IPFire diagnostics
Section: red
Date: November 29, 2020
The lines with “red0: carrier lost” indicate that the internet signal coming to IPFire stopped. In all three cases about 9 secs later the signal was back and was acquired again.
To me that would suggest a problem either with your modem/router unit or with the line coming into the modem/router.
Can you login to your modem/router and does it have logs that you can also check.
It looks like you have tested various connection methods between IPFire and the modem/router already. Did this include trying with red connected to a different network port on your apu2. Of course you would have to change this via the setup programme. Depending on how critical your system availability is you may or may not want to try that.
Yes, i tried with re-Configuration in the Console to use different cat5 Ports&cables and also with the apu2 builtin Wireless Moduleas red0.
When i connect my enddevices directly to the internet router, i did not observe any disconnets towards them or one the internet side.
This the Log from the router, stating to be online since 21.11.:
verbunden seit 21.11.2020, 20:22 Uhr, Geschwindigkeit des Internetzugangs (verfügbare Bitrate): ↓ 61,7 Mbit/s ↑ 12,3 Mbit
However, 2274 Hits from the router were blocked from ipfire:
I checked my IPFire dhcpcd logs for red0 and there are no carrier lost messages anywhere.
The lease time coming from my cable modem/router is 86400 secs, so 24 hours. That is what is shown in my IPFire logs. The dhcp server in the modem/router will then check if the IP address is still being used at 50% of this and if yes then the lease time will be extended. So if the line stays working then no release of the IP address or interface will occur. In my logs, the only renew of the IP address is from when I have carried out a reboot, when IPFire releases the IP address and shuts down red0.
Pulling the cable out of my IPFire red network socket and putting it back in was the only way I could get a carrier lost message in my logs and googling for carrier lost indicated physical hardware problems. Pulling out the cable going into my cable modem/router did not cause any carrier lost message.
As you have already checked cables and used other network ports then I don’t know where else to look for the cause of your issue.
Carrier lost is generated by a nic that has lose his link. After this it start autonegotiation again and get it back instantly. In the most cases this is a hardware failure. (bad cable, bad nic, unstable power supply or a bad ethernet port on the other side)
Also some modems switch of the carrier if they have lost the upstream synchronisation.
Hmmmm…i’m really clueless Now…
i found quite a lot of related posts in the forums, that turned out to be HW Problems in the end…thats why i kept trying to use different hw ports on the apu as well as on the router, Changing the cable and finally also using a wireless Connection
I have been fiddling with this issue for a month now before Posting here
Thanks for all replies anyways! I will Keep trying
There is one Bug related to this:
Everytime red0 goes down, the Device beeps
Disabling on the web-ui Hand no Effect,
I had to rename the /etc/Init.d beep instance
i just wanted to come back to this topic after a while of testing…
first, i continued to use the wifi<->wifi setup between router and ipfire, without success.
Now since 4 days, i updated to the latest -153 revision and went back to the console to change back to a cable connection between the two.
I’m really sure, this is all i did, but since that moment i have a stable connection!!
