Upgrade 2.5.2 to 2.6.0, upgrade success, Limiters not passing
-
This post is deleted! -
I also had no internet after 2.6.0 upgrade frojm 2.5.2 .
My wan(out) on the traffic graph showed no outgoing traffic.
I fixed this by going to Interfaces/WAN, go to the bottom of the page and uncheck
Block bogon networks
The internet was restored.
I hope this helps. -
@derez said in upgrade 2.5.2 to 2.6.0, upgrade success, no internet conection:
uncheck
Block bogon networksThat should just remove the rule on WAN to block inbound traffic from bogons. Likely reloading the new rules triggered something else. (the rule allowing LAN out wasn't active or something??) Had you tried rebooting first?
-
I have a test VM for pfSense just to play around, no real internet access. The "WAN" is the home LAN for the VM.
I did an upgrade from latest 2.5.x to 2.6 without any issues.
The "WAN" connection was right available after the upgrade.The real upgrade will be done during weekend, but its a Netgate Appliance, so the upgrade is from 21.05.2 to 22.01.
The VM was a test run for that.
Regards
-
@steveits You seem to be correct, prior to unchecking Block bogon networks, I rebooted twice.
However, I just enabled Block bogon networks and still have internet. -
@derez said in upgrade 2.5.2 to 2.6.0, upgrade success, no internet conection:
prior to unchecking Block bogon networks, I rebooted twice
Strange. Rebooting would reload everything of course. I wonder if restoring the config from backup would have "fixed" it also. Or if you had happened to have made a backup while it wasn't working, compare the backups.
-
Thanks Guys...
2.6.0 working fine now....
I disable "Block private networks and loopback addresses" and "Block bogon networks"
disable Limiter and limiter Fw rule .,..thanks
-
@neothesdony its the limiters behaving weird. Captive portal may also be blocking udp stuff like whatsapp calling. And aliases can also fail to work in the firewall rules. I'm also sticking to 2.5.2 for now.
-
There are no known bugs for any of those things but I agree the Limiters are the most likely thing there.
Steve
-
This post is deleted! -
@blikie yes agree..
it happened to me too -
@stephenw10 i have done some testing..
A fresh install pfsense 2.6 everything works with limiters on floating rules.
But when u have more than 1 LAN interface active, limiters block internet access.
Captive portal may or may not play a role in that as well. -
Same here in my environment. Updated from 2.5.2 to 22.1
I have two networks with limiters on rules for these interfaces.all traffic which should pass these rules are not working until I remove the In / Out pipe limiters.
-
How exactly do you have the Limiters configured?
-
I have the same error after upgrade to 2.6.0
All interfaces is UP and green, but no Internet connection at all!
This may be fixed at System/Routing/Gateways -> Save -> Apply, but for only next reboot.
This is looks a really bug. -
I'm using queues (which seems to work) to shape my traffic from internal traffic. Limitiers are used for guest access.
I have two zones for guests and a limiters for in and out bandwith per zone.Limiters using settings for bandwidth limit, tail drop and fifo.
these limiters are used on packet filter rules allowing internet access.
regards
-
@pooperman If you have multiple gateways make sure the default is set as WAN there.
If it's set as automatic and you have internal gateways that can become the default route which is obviously invalid.
Most people should not have internal gateways there. You would only have that if you have an internal router with other subnets behind it.Steve
-
@tohil Can we see that limiter config from the config file?
-
@stephenw10
I have one WAN gateway from my provider, but its not default, its uses for only vpn connection. And second gateway is a VPN one, which is marked as default.
It works on 2.5.2, its works on 2.6.0, but only after reapply gateway settings by hand. But for reboot it has no internet at all. -
@pooperman Hmm, interesting. What is the default route after a reboot before you reapply the gateway? Does the VPN come up correctly?
Steve
