@cmb: Um, founder of project here, thousands of source commits to my name. I replied to you just above. You don't need to install anything else, just don't try to modify the GUI's nginx instance. Setup your own nginx.conf, add a shell script /usr/local/etc/rc.d/my-nginx.sh containing something like: #!/bin/sh /usr/local/sbin/nginx -c /path/to/your/nginx.conf and you're done. Hello, I'm using nginx to serve up WPAD files, and I've added a wireless card to my pfsense box, so instead of WAN and LAN interfaces, I have WAN and WIFI1 and WIFI2 interfaces. Since each WIFI interface has its own gateway address, I think I need one nginx server for each WIFI interface, since I need to serve up two different sets of WPAD files. When I use the command above, the new nginx server seems to "bind" to the LAN interface (which I haven't yet disabled).  Is there a way for me to tell these new instances of nginx to be available on my WIFI1 and WIFI2 interfaces? -TM

@ johnpoz Thank you for the steps to download/install the patch. It worked perfectly! I didn't know of that URL to fetch the FreeBSD packages although I came across similar ones. Bharath

@rcollen: It might not be the same problem but i have also had the problem with updating and when you change the default gateway under "System/Routing/Gateways" , set the WAN as the default (dual WAN i am not sure of) and the LAN you select to not be used as default. This has seemed to help me to upgrade and download the packages . You should have NO gateway configured on LAN in the first place (let alone marked as default, huh…)

I found what causes it. It was one of my foxclock browser plugin. Now it was displaying properly as it should.  Thanks!

@NetResearchNewb: I just couldn't find any solution and I very much need one as soon as possible. https://portal.pfsense.org/

The uma_zalloc_arg you're getting is because the computer is having memory reference errors. Run memtest86 on it, and I bet you'll see errors with your RAM.

Just for completeness I should update this thread to say I was in error about the IP forwarding, I've checked the scenario out again, that actually continues OK. The fault seems purely to be that the config restore script unloads the system nameserver (the Bind package), then barfs when it cannot resolve names.

Good deal. Thanks.

Check the documentation - particularly on the sip proxy package. https://doc.pfsense.org/index.php/VoIP_Configuration

So just to update you all. I took apart my atom box and found a PCI slot. Stuck an intel based gig card in there and it worked perfectly with my wifi. So confirmed it was the Realtek NIC's causing the issue. Thanks all for taking the time to try and help. Will likely upgrade to a faster box at some point in the future with intel nics but for now PCI card is doing fine. :)

After hours…. I found solution: https://forum.pfsense.org/index.php?topic=51618.msg276125#msg276125

anyone?

Firstly, have a backup of your config, then: If the base FreeBSD and pfSense script PHP… files are fine, but you just made some config change that messed something up, restore the known-good config from backup. If files in the base FreeBSD or pfSense scripts... are gone wrong (deleted, corrupted, disk hardware problem...), then do a full install, then restore your config. (If the base system has been corrupted in some way, there is not much to be gained messing about trying to get back the files you know are deleted/corrupted... You will never be quite sure if everything is right. Much easier to just reinstall and restore the config.