@Paul47:

I was just wondering about the construction, "/dev/ufs/pfsense0". I'm unfamiliar with that. I was expecting something like "/dev/da0s1a", that's all.

It's a GEOM label, so we can refer to the slice by name instead of by its physical designation. So we don't have to worry about the disk driver/device name at all, we use our own label for the filesystem.

@Paul47:

I know about the read-only business in nanobsd, except for a couple details: I'm guessing a restore operation automatically mounts the cf partition rw? It had to have, otherwise my restore wouldn't have worked. I'm a little shakey on where the gui automatically mounts it rw, and where I have to do it manually. I will dig into that some more.

It handles that automatically for changes made in the GUI. If you want to manually make changes at the shell or over scp, etc, then you'll need to switch it manually.

@Paul47:

As to clicking on the logo, that makes little sense. What's wrong with a nice, obvious "cancel" button? Then people don't have to field so many newbie questions in the forum.  :)

I added some text to the wizard to state that clicking the logo gets out of it.

@stephenw10:

@Nachtfalke:

Perhaps they are updating all sites and mirros for pfsense 2.0.3 !?

Positive thinking. Nice. ;)

Steve

pfsense.org and packages are up again but no pfsense 2.0.3  ;)

@Wamba:

Thank you Sir!

Toggling with hard drive options in BIOS solved the problem!

I ran into the same issue last night after a mobo/cpu/ram upgrade.  I had to change hard drive access from AHCI to IDE to allow installation. Switching back to AHCI after install causes pfSense not to boot.

There's this:
http://doc.pfsense.org/index.php/Automatically_Restore_During_Install
Not completely unattended though.

Steve

Thanks :):) It`s work :):)

Thanks for all the feedback guys,  I have to admit I have found about 3 different ways to do things and as you say sometimes one way is better depending on what you want to do.

I have to admit though, this is one very very good product that I simply can not fault.  Well that's not entirely true, some of the documentation is a little vague in places but then again with so much flexibility that's to be expected.

@joako:

I'm facing similar issues attempting to run SquidGuard on embedded (NanoBSD.) The /var partition is not large enough to store the URL blacklist download, then the extracted files, etc.

Simply put is there any way to increase the size of the /var partition? Then whatever issues exist with files missing after a reboot can be solved with the package itself.

Well, I've recently addressed this question, e.g. NanoBSD + Squid, in this forum. Maybe, this thread is helpful:
http://forum.pfsense.org/index.php/topic,59932.msg322453.html

Well you should be able to find them on your network just do a nbtstat -A to the Ips and that should give you the hostname.

They are clearly clients, looking for those devices.  I guest printers from the MFC in their name.

As to such problems on a guest vlan - their broadcasts would be limited to your guest vlan, so not sure how it would be a problem?

As to periodically?  That 192.168.0.175 box really wants to find that printer, the is broadcasting every half second or so for it ;)

If I were you I would spend some time watching your broadcast traffic and cleaning up - if they are looking for something that does not exist fix the client so he has the new name, or remove the old device from his setup.  if your seeing broadcast for stuff that answers - look to why it got all the way to broadcasting for it, broadcasting is normally last method.

Should look to host, lmhost first then dns, then if node type is hybrid it would do lookup to wins if your running it then finally broadcast for the name.  So fix your name resolution, are clients/printers not registering themselves in dns?  Are they dhcp or static - pretty much any device on your network that would ever be accessed should be in dns.  And while  your at it get your reverse zones setup as well, so you can just query PTR for 192.168.0.175 and know what its hostname is, etc.

remove the package and then from the shell run pkg_add -r libxml2

Or backup your config, edit out the bad package, reinstall from an iso, then restore your config

Hi Jimp, I configured the following system tunables:

kern.ipc.nmbclusters=131072
hw.igb.num_queues=1
hw.em.num_queues=1
hw.igb.fc_setting=0
hw.em.fc_setting=0

mbuf usage sometimes is 19000+ or 20000, average of 20000

my wan download is at 10mbps while my upload is at 1mbps

I have a 4GB on order…...... Will keep you posted on how I get on.....

Once again.. thanks for your assistance

Regards

Martin

^ seems like a long way to go about it, cloning

Why not just take a snapshot of your pfsense VM, and then do your update - if everything goes good your on the new machine in a simple 1 step update.  If goes wrong, just rollback to your snap

Cloning and then bringing up new vm seems like more work to me ;)

TRy setting the raid controller in pass through and using gMirror part of pfsense. Otherwise, the raid controller is too new for pfsense (freebsd 8.1 in the case of pfsense 2.0.2). You could try 2.1 to see if the drivers are in there. Otherwise search the internet for installing freebsd 8.1 on a dell r710.

well nothing worked;
i decided id wasted enough time, reinstalled and built up from scratch.

problem solved.

Thanks :)

Steve Thanks I did not select option 3 on the menu, once I did I knew it was going to work!

Thank You again for your help.

We have 2 boxes with this Supermicro board and PFsense 2.0.1 running. One Year it was no problems at all, no restarts, very stable. Since today morning we have the same problem with these two boxes. Suddenly reboots, weird hdd problems (says it's full but it isn't full and fsck  and smart and vendor tools say it's all right with hdds). ram is OK. CPU temp on one box 38 and another box 21 Celsius. It's looks like something with cable or sata controller. It's runs with one hdd, no raid.

For 3 month I had the same issue with another boxes (absolut the same hardware configs) at my customers Datacenter. All was running about 6 month good and suddenly both boxes weird problems, reboots and so on. Those problem was solved changing sata cables and hdds from WD black scorpio 160 GB 2,5" to Seagate. Now they running 4 Month with no problems.

And today these problems in our Infrastrucure too :( There was IPMI update at supermicro website -> now installed and waiting if it helps. box #2 since 5 hours -> OK, box #1 since 1 hour updated -> no crashes.

I'll keep You updated if anything goes wrong, but for me now: no more these Boards with pfsense.

Thanks, just what I'm looking for. With old XP boxes in our store I doubt we are doing any UPnP; it's a pretty static system anyway. This also saves me buying a switch…

Yes, providing you have modified the appropriate sysctl to enable it.

Steve