Look here for the information about 32-bit i386 and nanoBSD not happening for 2.4: https://forum.pfsense.org/index.php?topic=121255.0

That's a bit tricky ;) A default install on any sort of hardware with "common" network device names ("igb0", "vr0" etc) should pick 2 interfaces to be WAN (DHCP client) and LAN (192.168.1.1 with DHCP server enabled). So you can physically plug in to each network port until you find the one that is being LAN. That will let you get to the webGUI and either assign interfaces using the webGUI or enable SSH and login to a text session an use the console menu.

Yeah just click the little button next to their lease to create the static/reservation for their mac to always get that IP.  go to the bottom of the dhcp server and add it..

I don't suggest a version. Don't know your setup, needs, … nothing from you.

A note for future readers of this thread: replace the old em1 with ibg0 when doing a search/replace in your favorite text editor, always be careful to look and think about where it finds "em1". Quite often it happens that a string like "em1" happens to appear in some randomly-generated long key (e.g. in the OpenVPN section or…), so you do not want to mindlessly/accidentally replace those.

misconfigured… I found the culprit: when I said that I had deleted the bridge, it turned out I had not! pfsense was running with a Bridge between LAN/DMZ with DHCP on both. Not what I intended or wanted. I had deleted the 'Interface Group' instead of the Bridge! I'm not even sure what it is or how to use that. Now that the Bridge is really gone, all appears normal.

NanoBSD? What are your firewall DNS settings?

@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/