CE 2.7.2 to CE 2.7.2 routing issue
-
Rules on the interface where the remote system is showing down:
Above is for bldg1 -- blow is the corresponding interface in bldg 2
-
Are they using the internal LAN IP addresses as the monitoring IP on each side? You seem to have static routes for those in the table which would otherwise be unexpected.
Do pings also fail simply to the remote side of the link?
Are you NATing that traffic? Do your Outbound NAT rules include the link interface?
-
the monitor ip is the LAN network internal gateway of the opposite pfsense.
Local Ip -> remote IP -> remote LAN gateway.
30.1 30.2 20.1Previously, (2.6x) this didn't work unless static routes were manually defined.
It worked between 2.7.2 and 2.6, but this issue arose when I went to 2.7.2 on both ends.The traffic across that .30 network is primarily between the buildings with no restrictions that I can see.
Any protocol, any to any on both ends.Pings fail only one way. Some traffic is getting through both ways.
It's like the firewall rule on one end isn't really operating correctly.
-
And that was it -- I opened and resaved both rules -- no changes mind you -- and boom -- it works as expected.
Sooo... lesson learned:
Don't restore backups.
Don't save them encrypted so you can read and manually transcribe the settings because restores are ...Well, it did restore the settings -- they just didn't take effect. :/
-
Hmm, odd. I assume no alerts were shown about failures to load the ruleset?
-
@stephenw10
No alerts in Bldg 2.
Bldg 1 ... I have pfblocker installed and it spams alerts so hard I'm thinking about just removing it :/Are there any alternatives?
I can go back to a pi-hole elsewhere on the network if there isn't. -
Hmm, odd. Sometimes if the running ruleset doesn't match the configured rules it's because it's unloadable. But when that happens you see an alert in the GUI. That should be different to anything pfBlocker is alerting you to.
Otherwise it appears it simply hadn't loaded. I assume the firewall rebooted when you restored the config? -
I did not see any related alerts - and the restore in bldg 2 caused a reboot and it was rebooted manually before and after the cutover.
-
Is it spamming alerts on the IP rules or the DNS rules? You could just disable the rules causing issues. I was never happy with the rulesets we could come across so we do IP via pfBlocker and DNS filtering via a third party service. It also would have helped to do some packet capturing to see if packets are even making it to the other side. That would verify if it were a routing or firewall issue.
-
@Stewart
pfBlockerNG MaxMind - MaxMind now requires a License Key! Review the IP tab: MaxMind settings for more information. @ 2024-02-29 16:15:40Once an hour.
I have turned off everything I can find about IP. -
@MakOwner said in CE 2.7.2 to CE 2.7.2 routing issue:
@Stewart
pfBlockerNG MaxMind - MaxMind now requires a License Key! Review the IP tab: MaxMind settings for more information. @ 2024-02-29 16:15:40Once an hour.
I have turned off everything I can find about IP.I think it now also requires an Account ID in addition to the License Key be provided to download updates. I think this new requirement took effect in January of this year.
I had to make a recent change in the Suricata IDS/IPS package because of the MaxMind authentication API change.
