Hi, gilf, hi Scott!
I solved this problem without additional soapbox (hub).
I just mapped LAN interface to ath0, which is "virtually" always on.

*** Welcome to pfSense 1.0-BETA1-TESTING-SNAPSHOT-2-5-06-embedded on pfsense ***   OPT2(LANBRIDGE)          ->  sis0    ->      NONE   WAN*                    ->  sis1    ->      172.16.128.11(DHCP)   OPT1(DMZ)                ->  sis2    ->      192.168.2.1   LAN                      ->  ath0    ->      192.168.1.1

…and here is my ifconfig output -

sis0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>mtu 1500         options=8 <vlan_mtu>inet6 fe80::200:24ff:fec5:6ebc%sis0 prefixlen 64 scopeid 0x1         ether 00:00:24:c5:6e:bc         media: Ethernet autoselect (none)         status: no carrier sis1: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500         options=8 <vlan_mtu>inet6 fe80::200:24ff:fec5:6ebd%sis1 prefixlen 64 scopeid 0x2         inet 172.16.128.11 netmask 0xffff0000 broadcast 172.16.255.255         ether 00:00:24:c5:6e:bd         media: Ethernet autoselect (100baseTX <full-duplex>)         status: active sis2: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500         options=8 <vlan_mtu>inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255         inet6 fe80::200:24ff:fec5:6ebe%sis2 prefixlen 64 scopeid 0x3         ether 00:00:24:c5:6e:be         media: Ethernet autoselect (none)         status: no carrier ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>mtu 1500         inet6 fe80::20b:6bff:fe37:579d%ath0 prefixlen 64 scopeid 0x4         inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255         ether 00:0b:6b:37:57:9d         media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated         ssid mms channel 1 bssid 00:0b:6b:37:57:9d         authmode WPA privacy MIXED deftxkey 2 AES-CCM 2:128-bit         AES-CCM 3:128-bit txpowmax 40 protmode OFF burst dtimperiod 1         bintval 100 pfsync0: flags=41 <up,running>mtu 2020         pfsync: syncdev: lo0 maxupd: 128 pflog0: flags=100 <promisc>mtu 33208 lo0: flags=8049 <up,loopback,running,multicast>mtu 16384         inet 127.0.0.1 netmask 0xff000000         inet6 ::1 prefixlen 128         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 bridge0: flags=8043 <up,broadcast,running,multicast>mtu 1500         ether ac:de:48:f9:56:39         priority 32768 hellotime 2 fwddelay 15 maxage 20         member: sis0 flags=3 <learning,discover>member: ath0 flags=3 <learning,discover></learning,discover></learning,discover></up,broadcast,running,multicast></up,loopback,running,multicast></promisc></up,running></hostap></up,broadcast,running,promisc,simplex,multicast></vlan_mtu></up,broadcast,running,simplex,multicast></full-duplex></vlan_mtu></up,broadcast,running,simplex,multicast></vlan_mtu></up,broadcast,running,promisc,simplex,multicast>

I think - problem still exists, with two ethernet interfaces and without wireless i need hub again ;(
Thanks, Arnis.

Ok hoba, thank you very much for your response!
It's such a shame becouse i love pfSense and i wanted to run it on that computer… I´ll keep trying. Thank you again.
Cheers

Nice, you seem to use it to the max  ;D
However the additional hardware does need additional power. Make sure the PSU is not at it's limit. While performing a reset it might need a power peak from the PSU to reinitialise everything.

We have started documentation. Have you already found this: http://doc.pfsense.org/index.php/Chapter_3:_Installing_pfSense ?

http://wiki.pfsense.com/wikka.php?wakka=BuildingpFSense
http://wiki.pfsense.com/wikka.php?wakka=VMWareDevelopersEdition

Yes, the *.img files are for the embeddeds.

We have 2 methods of developing you're own image.  The VMWare developers edition and the pfSense developers edition.

We do not plan on adding more work to a already complicated/time cosnuming release process.

Please try this: http://wiki.pfsense.com/wikka.php?wakka=BootTroubleShooting
The newer versions have a completely different installer.

ok will try that setup lter on today.. hope that works

swap will be nearly never used unless you run out of RAM, which shouldn't happen unless your RAM is too small for what you are trying to do.

indeed.  You can't ping what?  from where?

@christianb:

I managed to get the install on a 2.5" disk.

First I put the disk into my old laptop, and swapped out the intel2200bg card for an atheros one, so there would be two interfaces. PF sense intsalled, went through everything and hit 99 option for hdd install and even allocated 1gb of swap.

Then put the 2.5" disk into the soekris, and interestingly console worked enough to tell me that it could not find the original LAN interface, but let me assign a new one, from there it was GUI all the way.

It definately runs quicker from a GUI point of view, even though no swap space used as yet, I shall do some testing at some point to see if on HDD it works better under load. I have seen soekris have launched a version with 256mb of embedded memory BTW.

Has there been any thought to having a dual HDD and CF install? with read-only on CF, swap and storage on HDD. Basically it could be a CF install, then a script similar to the one to allocate free space on a CF card, but to HDD, and add packages in the process?

Thanks again for all your help, and look forward to seeing the usb boot version

That's on my list of things I'd like to work on at some point (I've got a couple Nexcom that are spinning platters that are entirely unused right now).

–Bill

here is the Captive portal topic
http://forum.pfsense.org/index.php?topic=490.msg3076#msg3076

You can do manual upgrades for non embedded versions. For embedded versions we provide mini update files. These however only upgrade the webgui.

Okay thanks, I'll check it out.