WAN down after updating dyndns WAN_PPPOE (After upgrade to 2.3.3) Pls help
-
Hi guys,
since I upgraded to 2.3.3 I get very strange behaviour. 2-3 Times a day my WAN interfaces gets shut down by an event "updating dyndns WAN_PPPOE"…..
I dont even use dyndns. The only way to get my WAN back up is to reboot my pfsense. This is really bad.
You can see the log files in here: http://imgur.com/a/g9TNz
Order is from bottom to top... I really cant figure out what causes this.
Need help on this badly :)
Thanks!
-
Update: I even set a dyndns service now but the error persists…
-
Hi guys,
since I upgraded to 2.3.3 I get very strange behaviour. 2-3 Times a day my WAN interfaces gets shut down by an event "updating dyndns WAN_PPPOE"…..
I dont even use dyndns. The only way to get my WAN back up is to reboot my pfsense. This is really bad.
You can see the log files in here: http://imgur.com/a/g9TNz
Order is from bottom to top... I really cant figure out what causes this.
Need help on this badly :)
Thanks!
Your log screenshot does not show anything extraordinary.
Do you have multiple WANs?
If you have only one WAN which is PPPoE then I think you are wrong in conclusion, the PPPoE is going down not by dyndns service event but PPPoE down event causes DynDNS to update. The root cause is something different, ex you modem or whatever else. Crystal ball is out of service now. -
@w0w:
Hi guys,
since I upgraded to 2.3.3 I get very strange behaviour. 2-3 Times a day my WAN interfaces gets shut down by an event "updating dyndns WAN_PPPOE"…..
I dont even use dyndns. The only way to get my WAN back up is to reboot my pfsense. This is really bad.
You can see the log files in here: http://imgur.com/a/g9TNz
Order is from bottom to top... I really cant figure out what causes this.
Need help on this badly :)
Thanks!
Your log screenshot does not show anything extraordinary.
Do you have multiple WANs?
If you have only one WAN which is PPPoE then I think you are wrong in conclusion, the PPPoE is going down not by dyndns service event but PPPoE down event causes DynDNS to update. The root cause is something different, ex you modem or whatever else. Crystal ball is out of service now.Thanks for that! So you assume that the error is not within pfSense but either the Modem or the connection itself?
-
IDK if this can give a clue but I'll leave it here:
The last events were on last Thursday (13. April) where the connection went down several times in the afternoon. Only thing that helped was pulling the LAN cable between modem and pfsense and replugging it.
Screenshot: http://imgur.com/a/XcmId
Then, 14. - 17. April was Public Holiday so nobody in the office, not a single connection loss in this time. Now, back on working day, first disconnect happened around 9 AM…
