jon
31 March 2024 21:50
2
Hello Jorge - Welcome to the IPFire Community!
There are others with a similar issues that have posted in the community. I have not experienced the same issue so I do not know the solution. Maybe give the connsheduler Reconnect command a try.
Also, you may want to post items from the log. That should help others assist you with a fix.
Here is one post I found that may help:
IPFire Core 144. Red interface is setup with dynamic IP. When a reconnection happens, it won’t automatically assign a new IPv4 address. ifconfig shows no address.
Reconnection examples: power-cycle the modem attached to red0, or do ifconfig red0 down; ifconfig red0 up.
IP can be manually assigned with dhcpcd red0 .
This is a problem whenever my modem resets on its own. My whole setup loses internet connectivity until I manually intervene.
Is this expected behavior? What would be the best way…
EDIT : Here is another:
Hi,
I have a weird bug. After reboot I have no internet but if I physically unplug and then plug back in the network cable will work.
Also if I do:
/etc/rc.d/init.d/networking/red stop
/etc/rc.d/init.d/networking/red start
will also drop the internet connection but it claims it got the right IP.
Bringing up the red0 interface…
Starting dhcpcd on the red0 interface… [ OK ]
DHCP Assigned Settings for red0:
IP Address: 173.180.2…
with this solution:
LOL, did some reading and it turns out I was misunderstanding how dhcpcd works.
According to docs dhcpcd - ArchWiki
The dhcpcd does the request then wait so the timeout is how long it will wait for a response and not a delay before requesting. Technically it can wait indefinitely ( with 0 )
The problem is that in current implementation the boot on the router will stop for the wait, there is way around that described in docs but not implemented in ipfire.
This kind of makes my retry patch use…
1 Like