weird internet access issue

pp-ng

@stephenw10 Yes same sendto error: 65

When you say re-save WAN, do you mean go into interfaces > wan and click save?

I did not do that if that's what you mean. I can try that next time

stephenw10

Yes, try that. That does many of the same things that reconnecting the link does but not all. That may give us some insight. Try to grab the system logs just after you have done that if it works.

Steve

pp-ng

@stephenw10 The gateway system logs?

stephenw10

Yes, the main system log. It will show the WAN settings being reapplied.

pp-ng

@stephenw10 i'm expecting to have the issue tomorrow, besides trying to re-save the WAN - is there anything else I should try for debugging or narrowing down the issue?

stephenw10

You can try to manually ping the gateway monitoring IP and see what error it shows.

pp-ng

@stephenw10 from diag > cmd prompt ?

rcoleman-netgate

@pp-ng Diag -> Ping

stephenw10

Or directly at the command line.

I usually prefer to SSH in and use the command line because then I can go back and review what was done.

A Former User

@pp-ng said in weird internet access issue:

Hi, I noticed that my internet access goes down once every 1 - 2 days.
Under gateways, it shows offline - packetloss for my WAN

Do your ISP cutting of your Internet access every xyz hours like here in Germany all 24 hours? Some thing is running full?

When I restart my modem which my ISP provides, everything starts working again.

Is this a pure mode or a small router with a modem?

It happened again and this time I directly plugged my modem into a laptop using the same ethernet cable that I use to plug into my pfsense router. My laptop had internet access and seemed to work fine.

Also for 2 days or longer or only for a moment?

pp-ng

@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.

stephenw10

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.

pp-ng

@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

stephenw10

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

pp-ng

@stephenw10 looks like i did some cleanup during that time. I removed wireguard tunnels and peers because I wasn't using them.

stephenw10

Ah, OK. Yes that could well trigger dpinger to restart. Not an issue then.

pp-ng

@stephenw10 it's been 6 days without issue after cleaning up the openvpn and wireguard tunnels and clients I wasn't using..

pp-ng

@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.

stephenw10

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

pp-ng

@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.