Support for 3.0 USB is just now being added to FreeBSD-CURRENT so I doubt we will see that until 9.0 RELEASE which is off in the future.  So at the earliest pfSense 2.1 which is mid-late next year.

@dreamslacker:

You do not, by any chance, have the onboard raid enabled, do you?

yes you are might be  right i am helping someone to build it on remote location i did asked at the beginning if its set to ACHI or PATA/IDE but still didn't got yet a clear answer.

Thanks

I  repair my hard ( victoria  , hdd regenerator,Low level Format) and change Ide cable
funny function
THX for conversation!

Nov 4 10:45:38 sshd[6791]: Accepted keyboard-interactive/pam for admin from 192.168.0.2 port 41079 ssh2
Nov 3 21:28:34 last message repeated 14 times
Nov 3 21:28:21 last message repeated 31 times
Nov 3 21:27:50 kernel: arp: 192.168.0.2 is on rl1 but got reply from 00:20:ed:69:37:f1 on vr0
Nov 3 21:27:50 php: : Processing -
Nov 3 21:27:50 php: : Processing start -
Nov 3 21:27:50 php: : Processing vr0 - start
Nov 3 21:27:50 check_reload_status: rc.linkup starting
Nov 3 21:27:49 kernel: arp: 192.168.0.2 is on rl1 but got reply from 00:20:ed:69:37:f1 on vr0
Nov 3 21:27:49 kernel: vr0: link state changed to UP
Nov 3 21:27:31 last message repeated 6 times
Nov 3 21:27:17 kernel: arp: 192.168.1.1 is on vr0 but got reply from 00:30:4f:69:73:3b on rl1
Nov 3 21:25:54 php: : Processing -
Nov 3 21:25:54 php: : Processing start -
Nov 3 21:25:54 php: : Processing rl0 - start
Nov 3 21:25:54 kernel: rl0: link state changed to UP
Nov 3 21:25:54 check_reload_status: rc.linkup starting
Nov 3 21:25:52 kernel: rl0: link state changed to DOWN
Nov 3 21:25:51 kernel: rl0: link state changed to UP
Nov 3 21:25:36 login: login on ttyv0 as root
Nov 3 21:25:34 check_reload_status: check_reload_status is starting
Nov 3 21:25:34 php: : Resyncing configuration for all packages.
Nov 3 21:25:33 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 3 21:25:33 dhcpd: All rights reserved.
Nov 3 21:25:33 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Nov 3 21:25:33 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
Nov 3 21:25:33 php: : Creating rrd update script
Nov 3 21:25:29 dnsmasq[578]: read /etc/hosts - 2 addresses
Nov 3 21:25:29 dnsmasq[578]: using nameserver 192.168.1.1#53
Nov 3 21:25:29 dnsmasq[578]: reading /etc/resolv.conf
Nov 3 21:25:29 dnsmasq[578]: compile time options: IPv6 GNU-getopt BSD-bridge ISC-leasefile no-DBus no-I18N TFTP
Nov 3 21:25:29 dnsmasq[578]: started, version 2.45 cachesize 150
Nov 3 21:25:29 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 3 21:25:29 dhcpd: All rights reserved.
Nov 3 21:25:29 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Nov 3 21:25:29 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
Nov 3 21:25:28 kernel: rl1: link state changed to UP
Nov 3 21:25:27 kernel: pflog0: promiscuous mode enabled
Nov 3 21:25:26 kernel: Trying to mount root from ufs:/dev/ad2s1a
Nov 3 21:25:26 kernel: ad2: 9541MB <wdc wd100eb-00csf0="" 04.01b04="">at ata1-master UDMA100
Nov 3 21:25:26 kernel: IPsec: Initialized Security Association Processing.
Nov 3 21:25:26 kernel: Timecounters tick every 1.000 msec
Nov 3 21:25:26 kernel: Timecounter "TSC" frequency 1462510354 Hz quality 800
Nov 3 21:25:26 kernel: uhub1: device problem (STALLED), disabling port 1
Nov 3 21:25:26 kernel: unknown: <pnp0c01>can't assign resources (memory)
Nov 3 21:25:26 kernel: speaker0: <pc speaker="">at port 0x61 pnpid PNP0800 on isa0
Nov 3 21:25:26 kernel: unknown: <pnp0303>can't assign resources (port)
Nov 3 21:25:26 kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 3 21:25:26 kernel: sio1: port may not be enabled
Nov 3 21:25:26 kernel: sio1: configured irq 3 not in bitmap of probed irqs 0</generic></pnp0303></pc></pnp0c01></wdc>

@No1451:

Now, I'm seriously new to this, since it has no video output how do I go about performing initial setup? I did notice that it has a serial port(I'm fearing this is how I perform the setup), but I lack any machine that actually HAS a serial port. All my computers are running enthusiast hardware, old standards die quickly for gamer hardware.

How does one go about this? Can I install on another machine to my HDD/CF card and then migrate the install or would that cause issues?

There are 2 choices:

1)  HDD full install.  You need a 2.5" PATA drive for this.  Do a full install on another machine but select the 'Embedded Kernel' when prompted.

2)  Embedded install on a CF card.  You need a serial port on another computer (I recommend getting a cheap USB to serial adapter).
Use physdiskwrite to write the image to the cf card and plug it in.
Then hook up the serial ports on both sets via a Null modem cable.
Fire up putty on the pc you're using to configure the box.  Settings are: (COM1 typically) 9600/8/N/1.
Once you've done the basic configuration (set the interfaces & IPs), you can proceed to do the rest of the work via the WebGUI.

@lpallard:

This thread is getting very interesting, at least IMO..

I might be overthinking this (my normal behavior) but..

the E5400 series might have more power per watt and therefore process faster at high power VS the atoms being lower power and slower but really, at idle, how is the difference?

The E5400 might process twice as fast at high power and idle the rest of the time, but if it idle at 2, 3 or even 4 times more power than the atom at peak processing, the E5400 would not be acceptable right?

You're not wrong in that respect - which is why I said it's not happening on a low throughput pfsense box.  However, if you do run stuff like Snort or IPSEC then (throughput aside) it would be much more evident.

I just get irritated by the stupid hoohah over the alleged power efficiency of the Atoms.

@clarknova:

Colour me impressed. I've seen much worse figures with realtek NICs, but obviously some are better than others. I think 10/100 vs gigabit hardware makes a big difference (in CPU usage) with that brand too, from what I've read.

Yep.  Realtek PCIe GBe NIC (RTL8111).  I'm not sure why anyone would choose the likes of the 8139 when Pro/100VE cards are available for the same price (sometimes even less if you find a bargain bin clearance unit) but there you have it.
TBH, I was suitably impressed too.  I was expecting the throughput to hover at about 200Mbps or slightly less with that kind of setup.

Edit:  The last letter for the 8111, I've found, makes for quite a bit of difference.  The 'B' and 'C' revisions are surprisingly quite decent as long as they don't crap out (I've had the unit on my D945GCLF2 die on me).  The 'D' revision is just plain horrible.

Even in Windows 7, the first few revisions of drivers supporting the 8111D usually gives a BSOD in odd scenarios.
It doesn't crap out when I'm pushing large files at 100MByte/s over the network.
It doesn't crap out during normal surfing.
However, the moment I stop streaming a video file over the network from a file share, I'm greeted by a BSOD.

Too slow, amigo!


thx

Using another appliance (Roper SuperLan adsl combo router) solved the problem.

@clarknova:

I have an HP t5710 thin client with an Infineon 1.2GHz CPU and 512/512 flash/RAM. I haven't installed pfsense to it, but I think others on the forum have. It uses 8.5-13.2W running LTSP.

I'm running on a T5720 with 1GHz, 2G/1G, and no problems.  I haven't checked the power consumption though.

Cheers.

I've already tried 2.0  betas both x64 and x86 with same result!

clarknova basically nailed it.
I'm not sure how much latencies would be incurred by NFS but it's definitely much better than traversing the internet to retrieve the data.  With enough knowledge/ help, I do suppose he could try to implement iscsi or gasp FC-HBA for better performance.
That said, this is out of the realms of us mere mortals without much in-depth knowledge of the OS's or coding and re-compiling them.

If you just want to stick to one box, I vaguely recall seeing a guide on the forums for attaching and mounting a separate hdd just for Squid.  That could be a way to go for embedded with a separate mechanical drive for caching so your flash drive doesn't get thrashed.

Also, since you have the budget for a SSD, I do suppose you can go for more RAM and a Velociraptor.  Whilst the latter won't quite hold its own against the SSDs for small files IOPS, it is remarkably decent for larger files.  You can always tune Squid to cache smaller files in memory (hence, the beefing up on ram) and larger files on the Veloci. (reducing the 'penalties' of small I/Os which isn't quite its forte).

Whether you go for SSD or mechanical drives, you'll still want a UPS for full installs to lower the risk of corruption (half written files on SSD is no less corruption than on a mech. drive during power losses).

ugen means that it is not finding a driver on the system for the USB device.

Did you ever get this working??

Yeah im going to keep an eye out for a Peak but they don't come up on fleabay as much as the X cores, it would be good to ditch the realtek nics!

The main reason I upgraded the processor was heat, the P3 runs a lot cooler than the Celeron with the bonus that it is more powerful :)

that means I can run less/slower fans as it is bloody noisy stock!

Im not sure about the 100meg pushing the box, I think it could well push the realteks with all the optimisations disabled.

Yes I am running load balancing between the 2 wans I have seen download speeds of 7.7Mb a second which is pretty quick the load balancing and fail over is fantastic, much better than on my old Draytek Vigor 2930.

The firebox seems to handle these speeds fine even with Snort using 75% of the rules on both interfaces and that was just with the Celeron and pfsense 1.2.3 (as I cant get snort running on 2.0 embedded)

snort, squid, whatever is big and does a lot.

@iorx:

I there a way to jump out to shell and edit files while booting the Live-CD?

I don't know of a way to do what you describe (unless what I describe below qualifies). Especially since you can't "easily" permanently change the files on the CD.

Clearly you have a problem creating the initial configuration with VLANs. If there were two NICs in your system (you could temporarily add a supported USB wired NIC or WiFi NIC or maybe even assign the parallel port as an interface) you could boot from CD, install to hard drive, edit the file, reboot and assign interfaces from the console menu and then setup your VLANs. From memory, pfSense 1.2.3 requires two interfaces. During the "install to hard drive" phase you don't need functioning interfaces so you could leave the VLAN configuration until after you have installed to hard drive.

From memory, pfSense 1.2.3 includes drivers so the parallel port and firewire ports can be used as IP interfaces if the necessary hardware is present in your system. Therefore it might be pretty easy to configure two interfaces to get through the initial install to hard drive, even if your system doesn't include two more conventional NICs.

All gone, sold. Mods may delete thread.

@netphreak:

But I don't like it though… Only manual firmware update to future firmware releases

Wasn't that also the case with pfSense prior to 1.2.3 when the images were still known as "embedded".

Cheers.