weird internet access issue
-
@stephenw10 so I haven't lost internet access yet, fingers crossed. not sure why because I haven't made any changes.
I did notice however in the gateway system logs:
Oct 12 20:02:01 dpinger 49963 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 1.1.1.1 bind_addr xxx.xxx.xxx.xxx identifier "WAN_DHCP "
This would typically come before the WAN_DHCP 1.1.1.1: sendto error: 65 - but it didn't this time.
So I'm still waiting for it to happen.
-
That log entry is dpinger starting on the WAN and recording the values it;s using. So that usually means the WAN was reconnected or a setting was changed causing dpinger to restart.
-
@stephenw10 so does that imply this time the wan reconnected successfully unlike before?
i know i didn't make any changes or reconnect anything manually
-
You'd have to check the system log for that time. But it's not an error. That's the expected output what dpinger starts.
Steve
-
@stephenw10 looks like i did some cleanup during that time. I removed wireguard tunnels and peers because I wasn't using them.
-
Ah, OK. Yes that could well trigger dpinger to restart. Not an issue then.
-
@stephenw10 it's been 6 days without issue after cleaning up the openvpn and wireguard tunnels and clients I wasn't using..
-
@stephenw10 yea it's been over a week without issue so far.
would it make sense after cleanup the issue would be fixed? not sure why having those in there would cause the issues i faced.
-
I would guess that you had some VPN connection defined that was becoming the default gateway if the WAN ever saw packet loss or latency. Removing that prevented it.
But you should make sure that the default gateway in System > Routing is set as the WAN and not automatic.Steve
-
@stephenw10 I will make sure it's set to that, thank you so much for helping me through this!
I guess we can close the issue. I think I'm good now. Appreciate it.
-
P pp-ng referenced this topic on
