Check out the linitx device. It's based on a C3 1GHz and has 6 nics, one even being gbit: http://linitx.com/product_info.php?products_id=909

Just an update…

I've got PFSense RC1a running on the box just fine with transparent proxying working (although it took an act of congress to get the script to work correctly), but no QoS. I'm still fighting the packet scheduler not liking the order in which the port forward rule is tossed into the rule set. I'm not sure if there's a way to make them compatible.

Anyone know of a way to get RC1a to be happy with transparent proxying port 80 and doing QoS? (P.s. I know this is off topic, but nobody replied about this in the addons area either).

Thanks.

oki
so i triede these modems ( isdn)
draytek isdn 2000
single isp - ok…..
dual wan - a very very poor performance . only one wan works - btw - both are connected
so ill try both isdn with pfsense netzt few days
ps: i think draytek works - but only in failover mode - and cannot merge 2 wans.....+
of course - not channelbonding - but draytek cannot differ beteween pc´s oder download/skype 4 example...

Run this again.  I fixed this 2 days ago IIRC.

Run cvs_sync.sh releng_1 from a shell prompt and reboot.

Skip checkout and skip rsync?

You should probably allow one of those to run.  I'd leave the checkout in there and set rsh=ssh.

That's the FreeBSD admin in me talking and not a pfSense dev, so YMMV. :)

Side note, I have a Token Ring Jetdirect card for a color laserjet sitting here that mistakenly shipped with my printer.  Have a use for it? :D

FAQ.  It updates with all the fixes on the 1.0 release branch.

@sullrich:

2. Open the unit and move the serial cable to serial #1.. It's most likely on COM2.

That doesn't apply to the 1041C. The front serial port already is COM1. See http://www.mail-archive.com/support@pfsense.com/msg03811.html for how to get the nexcom 1041c work with pfSense. I have 3 1041c out for production use, 2 with hdd installs, 1 with cf-card embedded version. All of them working great.

Gotcha thanks for the info!

Please be aware of the following bug.  Been haunting me on the Hacom units for the last week:

http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/88610

When we're talking multi-interface systems, this becomes an issue.  I was trying to build an 11 interface box (to handle all of the carp interfaces since you can't alias) and if it weren't for this bug I'd have no problems…

I case you want to use the hdd in this device you sould have a full install running at the hdd without a cf-card. The cf-card version won't utilize a hdd or any other media without preforming unsupported hacks.

@Sifter:

Mine is an AMD-K6-2 400 mhz chip.  It has 2 slots for memory, one which is filled with 256 meg of PC100 memory.

Would you mind taking a good high-resolution photo of the CPU area, like this one?

http://criggie.dyndns.org/tech/ip330/images/rear_slot.jpg

I'm specifically interested in JP2.

This option was removed.

@rcasas:

I have purchased 2 units of this hardware, and I have problems installing pfSense the full version on a 2,5'' HDD. The problems are about UDMA, and it seems to be the 44 pin cable because I've used other cable (the one which is included in a Soekris hard disk kit) and pfSense installed with no problem. The big problem is that the Soekris cable is only 1cm long.

Has anyone installed pfSense full version in the FX5620?

Yes I had the same problem:

I found that the problem was due to it trying to use UDMA100, and that's
not really possible on a 2.5" drive with a 44 pin cable.

atacontrol mode ad0 udma33

in the shell allowed me to complete the install

then I added

hw.ata.ata_dma="0"

into /boot/loader.conf which turns off dma for the hard drive
seems to have fixed all the issues.

I tried adding <earlyshellcmd>atacrontrol mode ad0
udma33</earlyshellcmd> into config.xml but didn't manage to get that to
work.

Nick.
http://linitx.com

I might actually have an answer, though I can't say for sure until I get in to the office: the very high interrupt load caused by the flood of incoming connections could be tripping the watchdog timer, and looking at the init code here, it looks like the watchdog is enabled at boot. Looking at the watchdogd manpage it looks like I can kill watchdogd to disable the checking – I'll try that in the morning and let you know how it goes.

@.Joel:

I am currently using monowall and it is not shaping my VOIP properly.  Basically controls the upload fine, but the download shaping isn't there so if we are downloading the voice goes all choppy.

You can't effectively control download using any type of QoS or traffic shaping.  You'd have to control your ISP's end of the link to control download speed.

Well they are working a version 2 so maybe they will offer more ram with them.

@Sifter:

Im not sure, but I dont think that is possible on the IP330's since the only way to watch them boot is through the management port and hyperterm.  There is no boot loader prompt.

Bollocks.  You need to get a proper null modem cable.  There is a BIOS that looks like a text version of a normal AWARD bios.

I had exactly the same issue using a three-wire null modem, where you really need all the handshake lines etc.   The FreeBSD stuff starts coming up after the boot loader prompt, if you have the wrong serial cable.

The cable is worth under $10 in any currency.  G'luck!

http://criggie.dyndns.org/tech/ip330/  <– lots of pictures and info on IP330 and pfSense.

There is another encryption card on ebay like the one above if anyone wants to grab it for testing.

http://cgi.ebay.com/Nokia-NIF4107-VPN-Luna-Accelerator-Card-for-IP330_W0QQitemZ9731660302QQcategoryZ51167QQssPageNameZWDVWQQrdZ1QQcmdZViewItem

nm solved the problem. ntop was running in the backgroup although not displayed in the gui.

@ginosteel:

done …i have beta 4 now but still got this problem
May 11 01:54:15 last message repeated 22 times
May 11 01:52:26 last message repeated 49 times
...
May 11 01:50:12 last message repeated 6 times
May 11 01:50:12 dhcpd: lease 192.168.11.66: no subnet..............etc etc

If you can increase the number of lines of syslog output, then try and give some earlier lines would be helpful.