Gave up and rebuilt it in the end. Then restored my config from backup. Whole process took 30 mins after my CF card reader arrived.

@jejethx: We have Pfsense 2.0.3 with HAVP + Squid + SquidGuard. I'd start with upgrading your PFS version.

I'm not quite sure what you're trying to do.  The current squid package is 3.5.19.  You want to "upgrade" to 3.5.3?

That is good to hear.  Now I just need to reinstall pfSense and I'll give that a go. Thank you all for your comments and suggestions!!

For anyone coming by this post later, it seems the MBUFS 'issue' is related to certain hardware setups.  I was initially surprised as the VM PF Servers I have don't have this high usage with the default settings. Anyway, I found the following pfsense documentation which explains this and what related settings to check: http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards Cheers,

Still failing.  The web configurator still says that 2.3.2p1 is available but the system will not update. In the option 13 console the last lines say: All respositories are up-to-date pkg:  Repository pfSense-core cannot be opened.  'pkg update' required pkg:  Repository pfSense cannot be opened.  'pkg update' required Checking for upgrades (0 candidates): . done Processing candidates (0 candidates): . done Checking integrity… done (0 conflicting) Your packages are up to date. So why is it failing? EDIT:  I was able to resolve by reimaging another USB drive and restoring config to it.

@chuchuchu: maybe the bug is truely a bug ? [image: 4000951125_6d2591948a_m.jpg] ;) LOL

@NOYB: No idea.  Not my call.  If it were they would already be there.  As you can see by their age, they are not getting the attention we think they deserve. Just ran across this.  (It's been a week already, and it's only Weds.) I'll talk to jdillard about them.

its more then likely a bios setting of some sort. Have you tried resetting it to factory defaults?

Funny you should write that … Again, just did a box reset to default, then dropped the DHCP to use Static on the 192.168.x.x default Verified PC static at .1.16 via the ARP table ... that worked ... Then switched over to 172.28.1.1 LAN ... and static 172.28.1.16 PC It worked ... and ARP table agrees. Must have been my 501st try ;-) Thanks for the use of your magic wand.

this clicking the link and again clicking is makin me sick: direct link: https://atxfiles.pfsense.org/mirror/downloads/old/

hi … can you post result of sth like this: Console /: du -h -d 1 cheers chris

So, Vivaldi, and thus implicated, Chrome, didn't fare any better. Same old soup, "Cannot get data about interface" on any interface graph we'd care to look at. Seems browser independent, now. That timeout in accessing fastcgi://unix:/var/run/php-fpm.socket (in the error log from Oct. 28) looks weird though, now doesn't it?

Is it normal for startup to hang waiting for the F1 key to be depressed? No. is there any documentation about the syscalls (system calls)? https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/

Sounds like it was something transient then and only cosmetic anyway. That's the desired behaviour if for some reason it tries to start twice on the same interface. Keep an eye on the logs but if you don't see it again then you're all good. Steve

I agree that USB NICs aren't good to use with pfSense, I would never use it in anything important. But I'm currently checking my options for having a cheap pfSense router other than min IBM T43. And a old Acer Aspire One, with a USB NIC would be the cheapest way for me to get a OK pfSense router for home use :) I'll try tomorrow! Thanks! :)

[SOLVED] The system is new, but I checked via the System Update.  Showed 2.3.2_1 Up to Date. So used the GUI exec command interface to do the pkg update and that fixed it. The BSD command list popped up in the console window as intended. So, very accurate diagnosis! Thank You!

Yeah it does, the WAN is something like 192.168.1.146. But seems weird, because I think I remember that it has worked before? But hell, I might remember wrong.. Thanks I'll try it asap and report back! EDIT: works now!

^ agreed!!!  Wifi cards in pfsense never going to give you coverage or feature set or speed that just getting an AP would allow you do.  An AP that supports vlans and switching that allows for vlans you can create multiple wifi networks. Or could just go with different AP for your different wifi networks.  If you have some old wifi routers laying around they can be leveraged as just AP in a pinch.  But its going to be better to get true AP that support vlans in the long run.

You didn't understand me, I've just confirmed that DNS servers in System > General Setup are not XMLRPC synced by design. Of course we sync XMLRPC everything:) The issue is fixed. You were right when mentioning ISP. I've contacted them and it turned out it was their fault. They have had a route which routed all traffic to WAN VIP address, even though we are directly connected. So, all the replies for traffic sent from backup box WAN address, were sent to WAN VIP owned by primary box. The only weird thing is that ICMP traffic was passing (ping, traceroute -I), UDP was passing partially (DNS lookup, drill), and (I think) TCP wasn't passing at all (couldn't telnet to any site port 80 from backup box). Thank you, very much. You were of great help!