Just upgraded from 22.01 to 22.05 on my Netgate 2100 MAX, cant reach internet now?
-
Ryan
Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
Requesting firmware for your Netgate device? https://go.netgate.com
Switching: Mikrotik, Netgear, Extreme
Wireless: Aruba, Ubiquiti -
It shows status as up, it has a gateway IP, no errors , no collisions, in/out packets 1/2(264 B/168B)
Suggestions?
Thanks for the prompt reply.
-
@robmontreal said in Just upgraded from 22.01 to 22.05 on my Netgate 2100 MAX, cant reach internet now?:
upgraded to 22.05 on my Netgate 2100 MAX, rebooted and now no internet
You rebooted or it rebooted itself? Upgrades will reboot automatically but it can take 10+ minutes sometimes, just wait it out.
tried pfsense ping
You can't ping the pfSense or the pfSense can't ping out to the Internet?
LAN should not have a gateway, only WAN.
192.168.1.69
2001:56a:f1e1:c500:92ec:77ff:fe20:724The IPv4 is a private IP, do you have another router in front of your pfSense? Can you ping that router?
Can you ping using IPv6? In Windows:
ping -6 ipv6.google.com
or
ping -6 2607:f8b0:4009:81b::200e -
@steveits Thanks for the reply.... I had to reconnect old router so they can do some work, old router works as expected.
I will reply in a bit when everyone goes to lunch i will switch over to Netgate again and troubleshoot
After the upgrade it rebooted itself. I lost connectivity drove to the office(45 mins) and it was up, but could not get to the internet.
I'll reply again in a bit
Thanks.. -
@rcoleman-netgate OK we are on the same page.
Thanks for the reference.
I removed the Package and Re-Installed the PFBlocker.
Now the CPU Usage is moving from 15% to 26% this is somewhat more normal from my observations. -
Ok i plugged modem back into netgate, i have a gateway under wan, but i cannot ping it, using ping under diags menu
Under status>gateways it says Pending everywhere?? Is this normal?
Thanks
-
This post is deleted! -
@robmontreal The pending status is probably because it can't ping the gateway either (?). In System/Routing you can edit the gateway and check "Disable Gateway Monitoring" but that's a bit of a hack. Does the ISP router normally respond to pings?
Is your WAN DHCP?
-
@steveits Hey Steve, i do not think my isp router normally responds to ping, i would have to reconnect the old router to check as everything works with old router.
My WAN is DHCP.
The pending was because i had the wan disconnected, my bad... it shows good now....
Can i provide more screen shots for you?Thanks..
-
@robmontreal OK so that's a public IP at least. If you can't ping the .1 gateway then either that gateway doesn't respond to pings, or there's some weird routing going on, or there's a firewall rule blocking your ping, etc. That shot shows the gateway online though so it seems like the monitoring did ping it...
Is anything set in System/Routing/Static Routes?
-
@steveits Ok, so I can ping the gateway just to confirm.
Nothing in static routes, its empty.
This is getting weird.
-
@robmontreal said in Just upgraded from 22.01 to 22.05 on my Netgate 2100 MAX, cant reach internet now?:
I can ping the gateway
tracert 8.8.4.4
and see how far you get. If you can get to the gateway it ought to be working.
It's not a DNS issue is it?
-
@steveits if i cant ping anything, i figure dns is not an issue
here is a tracert from my windows box
-
@steveits Is it easy to revert back to 22.01 version?
This issue is getting annoying... :)
-
@robmontreal You can reinstall:
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html192.168.0.1 is the LAN of your pfSense? It sounds like it doesn't want to route out. Does Diagnostics/Routes show a default route? Yet, the gateway is pingable...which might make sense if there is no default route.
Does System/Routing have a default gateway set? (black globe icon)
-
This post is deleted! -
This post is deleted! -
@robmontreal said in Just upgraded from 22.01 to 22.05 on my Netgate 2100 MAX, cant reach internet now?:
rather than leave as automatic in gateway i selected WAN_DHCP
I vaguely recall having to do that several years ago somewhere due to a bug, but it's not normal. The docs talk about it selecting the wrong gateway...
-
Just to complete this post, as I deleted some screenshots with IP in them.
This problem is SOLVED
"I ended up setting the WAN gateway to WAN_DHCP as it was set to none."
And then everything started working as it should.
Thanks to all that helped me out.
Have a great day!
