weird internet access issue

stephenw10

Yes, check to see if the default route has gone missing from the table.

Go to System > Routing > Gateways. Make sure WAN_DHCP is set as the default gateway and hit save. Check the route table again, that should have brought back the default route if it was removed.
Just setting the default gateway there if it's still at the default auto might prevent this happening.

Otherwise go to Interfaces > WAN and hit save there. See if that restores connectivity.

Steve

pp-ng

@stephenw10 Yea it is currently set to auto, I will change it to WAN_DHCP and see if the issue happens again. Otherwise I'll note down what the Diag > Routes show when the issue happens again.

I'm not entirely concerned about restoring connectivity as I am prevent this from happening. It's getting quite old having to go through this every~39-48hrs :)

Greatly appreciate this assistance with this, hopefully we'll figure out the root issue.

stephenw10

Indeed, preventing it happen is the goal here but working out exactly what restores it helps us pin down the actual problem so it can be prevented.

pp-ng

@stephenw10 Happened again

The Default > Routes page looks the exact same after it happened vs when it's working.

I tried saving and applying on the system > routing page, didn't restore access

I tried saving and applying on edit gateway page for the wan_dchp - it didn't restore access

I tried restarting the dchp servicce, didn't restore access

I switched the outbound nat from manual to hybrid, didn't restore anything

I eventually had to go back to unplug and plug back in the ethernet cable to the pfsense because I have to start working :)

stephenw10

Hmm, OK.

The logs showed the same sendto error: 65 ?

That really looks like a missing default route...

Did you try re-saving the WAN?

Steve

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.