Upgrade 2.5.2 to 2.6.0, upgrade success, Limiters not passing

neothesdony · Feb 26, 2022, 2:09 PM

Just Upgrade from 2.5.2 to 2.6.0, the upgrade run smoothly with no error.
But after reboot there is no internet connection. seems like pfsense blocking internet from LAN.
check syslog: no traffic were blocked.
ping to 1.1.1.1 from diagnostic>>ping. OK
my WAN connection PPPoE.(connection established and got IP from server)
hw: qotom J1900 4 intel LAN

Reinstall 2.5.2 and restore conf..
internet connection restored now..
I think i will wait to upgrade to 2.6.0.

any one have the same issue?

A Former User · Feb 15, 2022, 4:18 AM

@neothesdony said in upgrade 2.5.2 to 2.6.0, upgrade success, no internet conection:

any one have the same issue?

NO, ALL WORKING 100%

TorqueWrench · Feb 15, 2022, 4:58 AM

@neothesdony

I did not. I even tried rebooting after the initial upgrade reboot in case that was what you meant, but still no problem. Any other messages in the log? Maybe try a traceroute from the LAN to confirm that the connection is dying on the pfSense router?

How is your LAN setup? Do you have another gateway/router connected on the pfSense LAN interface? Could a watchdog have tripped setting that gateway to down? If there is another gateway/router connected to the pfSense interface, did you try restarting that?

FWIW, you might also want to consider crossposting your issue to the r/pfsense subreddit; a lot of pfSense users visit there that might not visit these forums as regularly (myself included).

Sorry this happened to you.

-TorqueWrench

neothesdony · Feb 15, 2022, 2:43 PM

Thanks for your help guys..
reinstall router with clean install pfsense 2.6.0
restore configuration... reboot
got notif from telegram boot up complete
fw rule allow all LAN NET
connection OK for few minutes
ping from pfsense shell to 1.1.1.1: RTO
tracing route from LAN to 1111 . traffic can not pass pfsense
still no success , no internet connection from LAN.
syslog no block.
snort: no block
pfsense blocker: WAN inbound only and disabled
I give up and back to 2.5.2. and everything running OK..
I think i will wait for 2.6.1
Thanks guys

plfinch · Feb 15, 2022, 4:25 PM

This post is deleted!

Derez · Feb 15, 2022, 9:06 PM

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.

SteveITS · Feb 15, 2022, 9:14 PM

@derez said in upgrade 2.5.2 to 2.6.0, upgrade success, no internet conection:

uncheck
Block bogon networks

That 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?

FSC830 · Feb 15, 2022, 9:17 PM

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

Derez · Feb 15, 2022, 9:41 PM

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

SteveITS · Feb 15, 2022, 11:02 PM

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

neothesdony · Feb 16, 2022, 1:26 AM

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

blikie · Feb 16, 2022, 1:26 AM

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

stephenw10 · Feb 16, 2022, 1:49 AM

There are no known bugs for any of those things but I agree the Limiters are the most likely thing there.

Steve

neothesdony · Feb 16, 2022, 2:47 AM

This post is deleted!

neothesdony · Feb 16, 2022, 6:33 AM

@blikie yes agree..
it happened to me too

blikie · Feb 16, 2022, 2:08 PM

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

tohil · Feb 16, 2022, 2:35 PM

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.

stephenw10 · Feb 16, 2022, 4:26 PM

How exactly do you have the Limiters configured?

pooperman · Feb 16, 2022, 6:00 PM

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.

tohil · Feb 16, 2022, 6:03 PM

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