@stephenw10 OK, that sounded like French, but I'll go back and read it a few more times and see if it begins to make sense when I compare it to my GUI options. ;)
Thanks so much for your help!

Yes, that is true. Netgate hardware includes pfSense Plus for the lifetime of the device. No additional subscription required.

What exactly are you seeing?

@GeorgePatches said in What happened to the CE downloads?:

@mcury Yes, that part seemed to work much like the standard installer.

Thanks GeorgePatches 👍

@usafit why would you think that should go on your firewall.. Endpoint is in the name even, pfsense or any router/firewall is not an "endpoint"

The firewall aspect of pfsense, just allows you to control what is routed.. Can endpoint A on network X talk to endpoint B on network Y..

An endpoint is something that starts a conversation, the other end point is what that something is talking to.. Pfsense is the router between when those 2 things are on different network..

Sure when you access the gui of say pfsense, then pfsense is the endpoint in that conversation.. But vast majority of traffic flows thru pfsense, pfsense is not the "endpoint".. Installing such software doesn't make a lot of sense for something like pfsense.. You would put that on your VM host, or the vm themselves or you laptop or your PC, or your phone, etc. Some iot device..

Is it no longer possible to download the CE images without registration?

Just want to update you folks. After a few hours of scouring the Internet. I have found that iOS 17.4 is broken for certain devices which seems to affect only certain iOS devices.

I have been messing around here what I’ve found so far. Using EDGE instead of 4G no problems, no SSL errors or time outs but of course very slow, using 4G is where the problem arises on the device itself.

Tethering using 4G to either a Desktop/Laptop or Android phone no problems at all. Connecting to WI-FI internally or externally no problems at all.

Remove SIM from the iPhone installed it into an Android and did all the same tests no errors at all. APIs and Browsers work perfectly fine.

This is very interesting however iOS 17.5 has been released so I will update and do all the tests. But it seems a lot of APIs and websites are broken with Apples Native Webkit.

Regards

Mmm, I can't really comment on that. I didn't write it as I don't have access to an AT&T connection. Try it and see, contributions to the docs are always welcome.

@stephenw10 Ok, thank's

If you see it again I would check the state table. The dpinger state may have been created on the wrong interface before the VTI came up and still be there.

@johnpoz
Thank you John. I'll have to do some research and figure out how to implement this.

There is nothing public. Generally we include as a recommended patch anything that can be fixed by a run-time patch, is confirmed as fixed definitively and has significant impact.

@matthewgcampbell

As Stephen indicated, more details needed.

If you have an external ONT, it's possible to rather easily pull certs from a 210 (possibly others).

https://github.com/mozzarellathicc/attcerts

The 210 can be found for cheap on ebay. Going this route eliminates a useless piece of a equipment remaining connected, not to mention gaining a port.

With the newer pf (CE 2.7x) and plus (23.09?) - which ever versions they introduced openssl3, there are additional steps needed to make eapol authentication work using wpa_supplicant. You can refer to this lovely reddit post which details the requirements quite nicely. - https://www.reddit.com/r/PFSENSE/comments/18jz0uc/installing_att_bypass_on_a_clean_install_of/ .

If you have a 320 with no external ONT, there's still ways of bypassing but more involved. You will need to obtain an sfp ont module and have a switch w/port to accept such modules.

What speeds are you seeing across the tunnel? What's the latency across the tunnel? High latency across a layer 2 connection can cause significant issues.

Hmm, I wonder how that happened. Curious. Glad you were able to track that down.

@stephenw10
No wireguard in my case. Now I use PPPoE only for IPv4 and HE GIF for the IPv6 testing and fallback. No problem with 13.x.x.x based sites currently, but I did not tested all of them.
I honestly don't understand what the relation to IPv6 is at all if packet capture shows that the connection is going through the IPv4 stack. I would be sure that it's some configuration error either from the provider's side or somewhere else on my end, but in fact, everything works directly, without pfSense.

To get a working internet connection we must create a VLAN7, assignee it and add a PPPoE connection. I wouldn't say this is impossible, but if one character is wrong and the installer try three times to connect my ISP blocks me for some hours...

@lightingman117 It feels like asking for trouble if you install unsupported packages inside pfsense... I am running pfsense as a VM under Proxmox which has worked fine for a few years now. With such a setup you can run any number of additional "packages" as separate VM's on the same machine, all booting up and working in unison.
Such a setup should work perfectly fine on a Protectly machine...

I then have AdGuard Home running as a VM and simply set all DHCP clients in pfsense so that their DNS is the AdGuard IP. AdGuard is not a DNS resolver, just a blocker/filtering service so it needs to point to a DNS service. You don't need to use pfsense resolver (unbound) but you can if you like, simply by setting the IP as the upstream DNS in AdGuard.

Then if you find it useful you can use pfBlockerNG to do additional filtering, like GeoBlocking.

Probably not those from the begining of March unfortunately. For some period attachments were being uploaded to an invalid storage location and when that was corrected those were effectively lost. But all other attachments (since the move to NodeBB) were restored.

@stephenw10 It was an antivirus page I left up that Squid stopped your right. Thanks I never reset the firewall when that was open.

The "Squid stopped a virus page"