And magically, both Epson R3000 and WP4530 show as online now, even though I haven't used them. Strange behaviour.

@noplan thank you

@roy360 This grabs the both the ipv4 and ipv6 networks. whois -h whois.radb.net -- '-i origin AS32934' | awk '/^route6*:/ {print $2;}' Not sure what's going on with your rule. I'll mess with this this weekend. Would be nice to have something that periodically updates. Edited 2-27 to add: The web service I want to use (https://api.bgpview.io/asn/asn to look up/prefixes) is 'Service Temporarily Unavailable' so that approach will have to wait for another time. Not a good sign for reliability... I did write a quick script to drop the ipv4 and ipv6 prefixes for all three facebook ASNs using, whois -h whois.radb.net -- '-i origin ASxxxxx' | awk '/^route6*:/ {print $2;}', into /usr/local/www and then created two URL table aliases from those files (I did one for v4 and another for v6). Ran the script from a cron job and that looks to work OK. I'll revisit this sometime in the future.

@bmeeks That's what I figured! Thanks again!

@krbvroc1 if ipv6 broke please see this https://redmine.pfsense.org/issues/11365

@daddygo The picture is so clear for me now. I much appreciate your advice and time. CF PRO plan is right at a reasonable cost. I will prefer it. Thanks

@jimp said in Recover via WebGUI feature: No, that is not viable. It was more like a dream :) (On the 'ceph' project we've been taking about "downgrade" feature for a long time and still talking...) But it's a nice dream !

Thanks @maverickws . The purpose of this revamp: they wanted to use only single pair of pfSense so that it can handle the traffics for the whole subnet 172.16.0.0/21. For eg 172.16.1.0/24 for client A, 172.16.2.0/24 for client B, 172.16.3.0/24 for client C and so on. Initially there are 2 WAN as in 2 ISP, 1 for each pair of the old pfSense unit. So now will be reduce to only 1 WAN (1 ISP). I will need to create few VIP at the new pfsense as a gateway for each subnet, for eg 172.16.1.1/24 for client A, 172.16.2.1/24 for client B, and assign VLAN to each of the subnet and configure some rules so that they wont be able to communicate with each other.

@johnpoz OK thank you very much

@thiago-0 There are some issues with OpenVPN on the new version. Check the OpenVPN forum.

@xplozia said in Pfsense FW behind to Mikrotik WiFi router: What I have to do in Mikrotik in order to redirect all traffic to the Pfsense? Hi, This seems more like a MikroTik forum issue. Proposal: Why not the pfSense is your main router + firewall

There is a potential for some things to be different, and moreso as time goes on, but for the time being most of the PHP code is the same on both. It's worth trying, and if there is a need for a patch specific to Plus 21.02 we can generate one of those as well.

That's what happened with the one I received from the other user as well, I couldn't base64 decode it even on other systems. You don't need those certs on the firewall unless you need to use them for export in some way, though. If the users have them already, they can keep using them. If they need to get a new copy you could use that opportunity to give them a new one. As long as you know the cert serials you can revoke them without the certs being present in the GUI, too.

I found today that PHP is already with the correct time, even before we update to PFSense 2.5. With that, the conclusion I had is that certain packages of the FreeBSD system receive updates before the PFSense system itself, even because if I did not do this I would not receive updates from the repository to notify that there is a new update from it. Problem solved. FreeBSD version 11.3-Stable.