Mmm, you'll probably have to wait for it to fail and check what states are still there. I'd expect it to just re-connect if the states timed out and start to fail.
Sounds like they are getting redirected locally if they see a cert error. Check what cert they are being offered. The details there may indicate what is intercepting the traffic.
@SteveITS Since the Netgate 2100 is at the Methodist local church and I support the firewall, this was a real user issue. They access the site monthly to do retirement account contributions for the church employees. Fortunately the login mechanism (once you can see it) requires two-factor authentication. Glad for that.
Thanks. I had the same issue, kept failing boot verification
43000 files in the config backup directory.
After getting rid of those, it upgraded faster than I have ever encountered in the past., I had gotten used to upgrades taking 10+ minutes.
Yup more and better logging is coming. However it also looks like there is an issue with the negotiated MRU/MTU value so a fix for that is in the works.
All sorted. SUE.....
Turns out ethernet doesn't work that well over a 300m long cable.....
Interesting though, the RJ45 Cable Tester did work so that was a bit confusing. Anyhow, good to know for the future and all sorted now.
@jwright Which device do you have/are running pfSense? If it’s a netgate device, connect to the console with a serialport terminal like “putty”.
If it’s a homebuilt pfSense CE, connect a monitor and keyboard. Then you will know if it boots as expected or something catastrophic has happened.
@guardian said in Anyone using pfSense with telMAX ISP (Canada)?:
I don't trust my ability to secure it.
Not much different than IPv4. You start out with everything blocked and only allow what you want. In fact, you can configure many rules to apply to both IPv4 & IPv6.
Here's an example:
[image: 1755915116010-9101928c-dd2d-4e58-abe2-d4a68923083d-image.png]
The first rule blocks pings and the second allows other ICMP.
Yeah, just to prove it out I ran a simple test. Since I don't have anything I can easily use that advertises mDNS I just turned on Publishing in Avahi itself on 4 firewalls:
steve@steve-NUC9i9QNX:~$ mdns-scan
+ 4860 [00:08:a2:xx.xx.xx]._workstation._tcp.local
+ 4860._ssh._tcp.local
+ 4860._sftp-ssh._tcp.local
+ fw1 [00:08:a2:xx.xx.xx]._workstation._tcp.local
+ fw1._ssh._tcp.local
+ fw1._sftp-ssh._tcp.local
+ pfsense [00:01:21:xx.xx.xx]._workstation._tcp.local
+ pfsense._sftp-ssh._tcp.local
+ pfsense._ssh._tcp.local
+ 1100-3 [f0:ad:4e:xx.xx.xx]._workstation._tcp.local
+ 1100-3._sftp-ssh._tcp.local
+ 1100-3._ssh._tcp.local
In that result 4860 is in the same subnet as the client I'm testing from. fw1 is the router on that subnet. pfsense and 1100-3 are other firewalls in different subnets connected to fw1.
You can see the scan tool is able to see all of them no problem.
@stephenw10
Ended up doing a reinstall. Netgate installer is pretty sweet. First time using it and absolutely no issues at all. Impressive.
Also restoring from ACB was a bit nerve racking as I couldn’t find my key but it all worked out in the end. Seamless to get back online to be honest
I really don’t know why people have hang up’s over the installer..it just works
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.