@stevehaley: I keep seeing references to posts that claim that it is possible to configure pfsense to establish the gre tunnel with the hitron in modem mode in order to login for the stAtic ip on virgin. Has anyone managed this? I cant even get pfsense to get a dynamic address when the existing smarthub 2 is in modem mode and have to spoof the mac address. The Hitron and Smarthub are two completely different devices, aren't they?

Glad its not just me. I even resorted to "pkg-static upgrade -f" just to make sure nothing had become corrupted, it took about 4 hours to download and reinstall 10MiB. It definitely seems to be something very wrong in the package manager itself.  Its not working at all from the UI but that is probably timeouts due to how very slow its running. Downloading something via curl on the command line does my line speed.  Downloading from the mirror site directly works fine.  All other functionality of pfSense is absolutely fine.

hhajj: You mention that after few minutes, connection to web configurator is lost. Did you get the 502 bad gateway error? If so you are not alone  :-[ Have a look here https://redmine.pfsense.org/issues/6406 Looks like the bug is one year old and that progess is 0%.

I followed this guide: https://www.netgate.com/docs/sg-1000/faq.html#how-do-i-restore-the-firewall-os-firmware And flashed the image to USB using this command: https://www.netgate.com/docs/reference/create-flash-media.html#linux-freebsd-mac-os-x Then when I had the OTG cable plugged in, with the USB connected, it gave a re-flash option from the console on first boot. Hope that helps.

Not yet.

I logged on to my pfSense today and was pretty horrified to see a 502 error page. I didn't want to reboot until I understood the cause. I did have the OpenVPN Widget and IPSec VPN Widget running on the homepage of pfSense. I also changed my firewall logs to show 20 results, show FAIL & REJECT, and refresh every 1 second. Perhaps this was a bit too aggressive. My OpenVPN clients couldn't connect via OpenVPN but IPSec VPN was able to still connect. As advised earlier, restarting PHP-FPM using the numerical menu options in the pfSense console allowed the OpenVPN tunnels to connect again, and removed the 502 error. Hope this helps.

What does npcap loopback adapters have to do with anything? Why do you have npcap even installed?  Are you running wireshark?  That has zero to do with your machine clearly got an 192.168.1.101 address from a dhcp server.. IPv4 Address. . . . . . . . . . . : 192.168.1.104(Preferred)   Subnet Mask . . . . . . . . . . . : 255.255.255.0   Lease Obtained. . . . . . . . . . : Sunday, May 14, 2017 5:10:03 PM   Lease Expires . . . . . . . . . . : Sunday, May 14, 2017 7:10:03 PM   Default Gateway . . . . . . . . . : 192.168.1.1   DHCP Server . . . . . . . . . . . : 192.168.1.1

@Chti: Last night I decided to upgrade my SG-4860 from 2.3.3.1 to 2.3.4. So I hooked up the console, and the device boots up for a few seconds but then remains indefinitely at a "Boot: F1" line. Honestly, I'd just call them Monday.  There have been a few similar posts in the official hardware forum and they've really been extremely helpful to people who have had problems with updates of both BIOS and pfSense itself.  You might want to check a few of those posts too, maybe there is something there. Rick

I don't have a Dell server , but had the same errors on an AMD LX800 Geode. I ended up using the CD instal w. an USB attached DVD drive. Remember to set the set kern.cam.boot_delay="10000" My post https://forum.pfsense.org/index.php?topic=127036.msg701568#msg701568 /Bingo

It seems there is a problem with pfsense kernel upgrade on nanobsd … for some reason it remains locked and cannot be upgraded using GUI or pfSense-upgrade ... The solution is to do regular upgrade and than go to shell and execute: pkg unlock pfSense-kernel-pfSense pkg upgrade pfSense-kernel-pfSense pkg lock pfSense-kernel-pfSense reboot

I did. I used an usb to install Pfsense and the error is from that installation using pfSense-CE-memstick-2.3.4-RELEASE-amd64.img. @johnpoz: At a loss to what your trying to do?  The memstick images are meant to be written to a usb stick.. And then booted from that stick.. https://doc.pfsense.org/index.php/Writing_Disk_Images

Remember that the ASA is "SIP Aware" , and it's default enabled under services. Not that it should do something to a conn limit. Also you have port 5061 in your ASA rules , and refer to 5060 in the pfsense examples. Someone here mentioned using siproxd , on pfsense http://siproxd.sourceforge.net/ SIP and NAT requires some thoughts , or a sip aware proxy to "modify" "the inside ip addr" , to the "outside addr" , in the "payload" All of that stuff is being done by default , in the ASA. /Bingo

@klave7: With the help of the PFSense team I was able to get it working again by reflashing the software onto the device.  In case anyone else has this problem. Hi Where did you download the firmware image file from? I have the exact same issue and can't find the image file anywhere… SG-4860 as well and boots up to F6 PXE Boot: F1 … and then nothing

If you can get to a loader prompt (and type in it), try this: set hint.bwn.0.disabled=1 boot If that works, after install, add hint.bwn.0.disabled=1 to /boot/loader.conf.local

There are many views on upgrading…. I will share with you my general approach (Synology, Android, etc...) I currently still don't own a pfSense box  ??? :D Assuming it's only for home use, you don't have big secrets to protect, pfSense is not your full time hobby, you are not an active pfsense user in the community, you don't have a job in network routing domain and you don't want to spend too much time updating a router box. Below is my order (1st being the highest priority) ASAP if there is a major exploits or vulnerabilities that is trending online (e.g. Read on Apache struts) pfSense released a patch version that fixes a bug affecting you directly (feature) or indirectly (performance, high cpu or memory leaks) When pfSense release a minor version you really require (feature, performance) When your version is no longer supported, might be time to upgrade (if time permits) Major version changes, hardware supports it, it's time to upgrade to keep up  (if time permits)

Unfortunately, there are no log messages remaining that would explain what happened. System / General is swamped with snort messages. DNS Resolver is swamped with messages from umbound repeatedly restarting.