Wan reconnect problem
-
@ed-tech i dont know about yours, but since i have only one wan, and that is pppoe, the only thing in common about our situations is that only disabling and enabling the interface solves for a while the problem
-
@stephenw10
Im on phone right now, but here it is what i can copy:Nov 28 07:55:21 ppp 11865 [wan_link0] PPPoE: Connecting to '' Nov 28 07:55:21 ppp 11865 [wan_link0] Link: reconnection attempt 9 Nov 28 07:55:19 ppp 11865 [wan_link0] Link: reconnection attempt 9 in 2 seconds Nov 28 07:55:19 ppp 11865 [wan_link0] LCP: Down event Nov 28 07:55:19 ppp 11865 [wan_link0] Link: DOWN event Nov 28 07:55:19 ppp 11865 [wan_link0] PPPoE connection timeout after 9 secondsThats all, it repeats. I dont think pppoe is the culprit
-
You have 6 NICs there. 4 of them are Realtek which is bad. But worse is that two of them are rl(4) devices which are terrible NICs. I can't see exactly which NICs you're using there for each interface but I do see you have dhclients running on bot rl0 and rl1 so if those are your WANs it's almost certainly a NIC problem.
For reference: https://github.com/pfsense/FreeBSD-src/blob/devel-main/sys/dev/rl/if_rl.c#L46
Steve
-
@Cobrax2 said in Wan reconnect problem:
Thats all, it repeats. I dont think pppoe is the culprit
Well it is in that it's not connecting and just timing out. Check that the ppp process ID (11865) remains the same in the logs. We have seen some instances where two ppp processes were started and conflicted.
Try to check what happens in the logs when it initially goes down. Is there something other than the ppp event, maybe the parent NIC loses link ?
Check what's shown when you resave and it connects. Does it just connect up immediately at the first attempt for example?
-
@stephenw10 said in Wan reconnect problem:
@Cobrax2 said in Wan reconnect problem:
Thats all, it repeats. I dont think pppoe is the culprit
Well it is in that it's not connecting and just timing out. Check that the ppp process ID (11865) remains the same in the logs. We have seen some instances where two ppp processes were started and conflicted.
Try to check what happens in the logs when it initially goes down. Is there something other than the ppp event, maybe the parent NIC loses link ?
Check what's shown when you resave and it connects. Does it just connect up immediately at the first attempt for example?
Yes, it connects fine right away. Will try to save the logs next time it occurs. I suspect it has something t9 do with my privider, as the setup worked fine until recently, and i didnt do any changes. My problem is, why doesnt the nic reset? What does the disabling and enabling in gui do?
-
It stops and starts the ppp daemon (mpd5). If it has become confused somehow and is trying the wrong thing that might do it. Or if it's somehow blocked restarting it creates new connections that may not be for example. Neither of which should ever happen but....
-
@stephenw10 said in Wan reconnect problem:
It stops and starts the ppp daemon (mpd5). If it has become confused somehow and is trying the wrong thing that might do it. Or if it's somehow blocked restarting it creates new connections that may not be for example. Neither of which should ever happen but....
It does nothing to the em0?
I am talking about the one in interfaces/wan.
How can i trigger it via shell command? I would like to try a cron job
Thanks -
If you just resave and apply the WAN does it reconnect? That can be triggered at the CLI.
When the WAN is set to pppoe0 then resaving or re-enabling it does not do anything for the parent NIC, em0.
-
@stephenw10 said in Wan reconnect problem:
If you just resave and apply the WAN does it reconnect? That can be triggered at the CLI.
When the WAN is set to pppoe0 then resaving or re-enabling it does not do anything for the parent NIC, em0.
I didnt try just save and apply. I did uncheck, save apply and then check save apply. Can that be done by shell? If not how can i try just the save and apply?
-
You can run:
/etc/rc.interfaces_wan_configure -
@stephenw10 thanks, will try
