OK, this worked, sort of.
Not sure if the configuration is bonkers or if the system threw a hissy-fit because it's configured for a fixed IP that won't work here…
...need to create a pseudo Internet gateway for it first and upload a 2.2.3 system from there.
Anyway, one way or the other I'll get it done ;)

Thanks!

it installed to mSATA drive, ada0. that must me the correct destination as this isn't the "nanobsd platform". its listed as "pfsense".

anyways, its up and running

Why don't you just do a full install on the HDD? On nanobsd, entire slice is rewritten on upgrades and switched to on reboot, totally unsuitable for similar "tweaks". (Beyond that, the size of /var and /tmp ramdisks is configurable, provided sufficient RAM size of course…)

Hello Again.

I´m up running Thank you for help.

It was the partitions size making the problem. Setting " /swap to 8 "      " / to 4 Gigabyte " added a new " /usr " on rest of the disk.
Will pfsense use the /usr partition or is it waste now ?

Either the packet or LBA adjustments have any effects.

/Brian

Similar problem here:
Hardware: Cisco SG500 in layer 2 mode and a old Astaro ASG 110/120 Rev. 3.  (the Astaro has four Intel 82559ER NICs)
After configuring the vlans on the SG500 and the Astaro DHCP over vlans did not work and I could not ping the gateway over the vlans.

The problem was solved by disabling the default vlan processing in hw:

A small script /usr/local/etc/rc.d/disable-vlanhwtag.sh

#!/bin/sh ifconfig fxp0 -vlanhwtag ifconfig fxp1 -vlanhwtag ifconfig fxp2 -vlanhwtag ifconfig fxp3 -vlanhwtag

is fixing the problem at startup.

@davysilb:

Solved it it was a faulty keyboard a rosewell gaming one

Damned gamers…  :P

Hmmm, not really. My experience in general is that

current optical media quality totally sucks current optical drives quality totally sucks the whole technology is a good riddance

Unless you have ancient HW not capable of booting from USB, the CD stuff is best avoided… (I'd suggest a PXE boot as alternative, but that's been screwed ever since FreeBSD 9.0 and noone cares.)

what are you using for dns, forwarding or the resolver?  Are you using dnssec if using the resolver?  There is one site I frequent that just doesn't really resolve very quickly..  With a short ttl.. So if have not hit the site in awhile, sometimes the first hit doesn't work and have to refresh browser because it is taking longer than normal to resolve via resolver.

This can be somewhat misleading to find because by time you look its resolved and cached..  So it doesn't jump out that its dns related.

As a side note - since your behind a nat, your cable "gateway" - modem to me screams no nat.. Ie my cable "modem" sb6120 doesn't do nat.. Modems don't do nat, gateways/routers do nat.  If you call it a cable "modem" I would think your not doing nat and getting public on pfsense wan.

Also on your dns if using forwarder are you pointing to the isp box for your dns, or directly to isp/public dns?

Judging by the name we just helped you get this going again in a support ticket.

To help others in a similar situation, it turns out that in this case it appears to have been your USB cable that didn't work correctly, which caused the COM port to not appear in your workstation.

Any chance of upgrading it to something a little more current so that you're not chasing old bugs?

You are better off on 2.2.3. The 2.2.3 snapshots at this point (From yesterday afternoon forward) are much more stable than 2.2.2 in just about every way except the official blessing of being a release.

Hi

When Navigating in the GUI, in general when applying any change after creating a rule it takes to much time, I have no special configuration, nat and port forwarding, I just started configuring it.

PFSense 2.2.2
AMD 2 core at 2.5
4GB Ram
32 GB USB

Sounds like failed upgrade with screwed permissions and without reboot. Reboot the box and reapply the upgrade.

@almabes:

Yes.  Just make sure you plug it in the correct slot.

i see what you mean as i see three slots.  the adi "component  layout internal connections" shows which one is mSata.

thanks!

It's NIC cards that matter more than the processor.  You want Intel gigabit NICs.  The little APU they sell at the pfSense store has a 1Ghz cpu, and craptastic realtek NICs.  I have one on my 100Mb comcast connection, and it works just fine.

Look, on any recent SSD, you can write hundreds of TBs of data and it will still be well alive and kicking. That's a usage that's never gonna happen with /tmp or /var on pfSense…