https://forum.pfsense.org/index.php?topic=122999.0 Did you enable https in your captive portal - if so then your browser would throw you an error like below.. You would think users understand this problem already ;)  Per the thread many OSes understand captive portals and when you connect via wireless they would direct you to the portal page via http url they try and go to in the background, etc. edit: ah jimp beat me too it ;) [image: httpscaptiveportal.png] [image: httpscaptiveportal.png_thumb]

For all those unifi controller users.. Same thing for adding the SAN to cert your using for unifi controller.. sudo su - cd <unifi_base># on Windows, "%USERPROFILE%/Ubiquiti Unifi" cd /usr/lib/unifi create new certificate (with csr) java -jar lib/ace.jar new_cert <hostname><company><city><state><country># your CSR can be found at /var/lib/unifi - unifi_certificate.csr.der - unifi_certificate.csr.pem have this CSR signed by a CA, you'll get a few certificates back… copy the signed certificate(s) to <unifi_base># import the signed certificate and other intermediate certificates java -jar lib/ace.jar import_cert <signed_cert>[<other_intermediate_root_certs>…] Just add SANs you want on your cert.. Before you sign the csr on pfsense. [image: unifi-trusted-cert.png] [image: unifi-trusted-cert.png_thumb]</other_intermediate_root_certs></signed_cert></unifi_base></country></state></city></company></hostname></unifi_base>

Good luck! Generally they try to design their antennas to do multiband capability..  One could put a jack in place and run to an external directional antenna that is "in band" but that won't stop the other bands from making their presence known..  Just be more inefficient as the device tries to transmit back to them.. Maybe another device is the answer such as a Cradlepoint or Sierra Wireless..

https://doc.pfsense.org/index.php/How_can_I_forward_ports_with_pfSense https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

pfSense by default trusts the LAN and not the WAN. The deny by default logic only applies for untrusted interfaces. LAN side, UPNP, DHCP, DNS, management, SSH, etc are all allowed.

https://doc.pfsense.org/index.php/Why_was_FreeBSD_chosen_instead_of_another_OS

pfSense uses wol ( https://www.freshports.org/net/wol/ ) to send wol packets. It doesn't have a daemon to listen for them.

Edit your gateway settings: System/Routing/Gateways

I could probably filter out a list of known offenders to see what is new with a simple script.  Thanks.

You should not upgrade to 2.4. I tried and completely disappointed Sorry, have to disagree completely. My experience migrating 20+ installations at various revisions from 2.2.5 up to 2.3.5 has been very positive. The only (minor) headache I ran into was a system that wouldn't auto-update from 2.3.0. It seemed to be locked down to a development stream and wouldn't let me change it. Simplest fix was to take a backup of the config.xml, reinstall from scratch and restore the backup. Full repair was perhaps 20min. Other than that it's been quite painless for me. Whatever you do, make sure you have a backup of your current setup. Just my $.02

@johnpoz: 1.1.1.1 is typical ip used in cisco for the captive portal.. So states from such an IP would point to that as your problem.. Its really bad practice to leave it using that IP if you ask me.. That is reserved IP range and shouldn't really be used in such a setup.  1.1.1.1 was handed off to apnic long time ago.. They could hand that out whenever even though currently they listed it as testing network.. Its better to change that to a rfc1918 address that you do not use in your network or even a rfc3330 special use IPv4.. But if your seeing odd traffic from 1.1.1.1 it would point cisco or maybe other wireless controller doing something funky.. Thanks so much !

It was actually in a chapter in the book had I bothered to look a little further. Thank you so much for your assistance. Have to laugh at myself sometimes.

I think we need some actual numbers of how many states you have, how many new ones are being created, and what your throughput is.

You reinstall the old version and restore the configuration backup you took before you upgraded.

i was not happy the RC candidate crashed my sg 2220… but now that i have learned the process to console and reinstall the OS i am happy.  i did learn several tricks on the way to improve my network from all the research i did!