Search the forum how to get this card working. The search function is here: http://forum.pfsense.org/index.php?action=search

i purchased the alix box at pcengines.ch and ive tried 2 different cf cards where 1 was previously running with backtrack linux and the other cf is new ah and i used the new one to do the bios upgrade (with a dos image on the cf that worked)

If you want small with four interfaces, and possible VPN accelerator, and <$500, the Soekris boxes are nice. https://www.soekris.com/shop/product_info.php?products_id=129 You could add an Intel PCI GB card if you wanted to expand it. The vpn1411 cards are helpful on the Alix and Soekris boxes, but any modern CPU will be able to run IPSec faster than the card can. Just to pull some rough numbers out, on 1.2 I could do about 8mb 3DES or 15mb AES on a stock Alix. The vpn1411 got it to around 40mb 3DES or AES. A PC-based box with a mobile CPU ran about 50mb 3DES and 85mb AES. YMMV.

I had problems with my USP keyboard and some of my network cards. I´ve tried every solution that the forum could provide and then i accidentally found the 1.2.3 version. http://blog.pfsense.org/?p=377 This solved all my problems! The even the USB keyboard is working without any workarounds.

Hi, I was able to compile the driver in this way (usuing a computer with FreeBSD 7): tar zxvf Driver_FreeBSD_7830.tar.gz x Driver_FreeBSD_7830/README~ x Driver_FreeBSD_7830/if_mosreg.h x Driver_FreeBSD_7830/if_mos.c x Driver_FreeBSD_7830/README x Driver_FreeBSD_7830/Makefile cd Driver_FreeBSD_7830 vi if_mos.c Add the following #include <dev usb="" usb_port.h="">Then compile and load the module make kldload if_mos.ko You will see the interface as mos0 ifconfig mos0: flags=108802 <broadcast,simplex,multicast,needsgiant>metric 0 mtu 1500         ether 00:50:c5:70:1c:9b         media: Ethernet autoselect (none)         status: active I think if you want it to get it working in PFSense you should copy if_mos.ko to /boot/kernel and then add  if_mos_load="YES" to /boot/loader.conf so the module will be started every time you boot the system.. Regards, Juan Priotti</broadcast,simplex,multicast,needsgiant></dev>

So far I have added padlock_load="YES" to /bootl/loader.conf. When I look at dmesg I see padlock0: No ACE support. Googleing this seems to mean that the module isnt loaded. Anyone know anything special about this? I am using an extra via epia board right now, hence the c3 processor. I figured this being a more mature product would have better support than the nano board. Plus I can fubar it without taking down the network. thanks in advance for any help. $ dmesg Copyright 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE-p8 #0: Thu Jan  8 22:07:30 EST 2009     sullrich@freebsd7-releng_1_2_1.pfsense.org:/usr/obj.pfSense/usr/src/sys/pfSense.7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: VIA C3 Samuel 2 (800.03-MHz 686-class CPU)   Origin = "CentaurHauls"  Id = 0x673  Stepping = 3   Features=0x803035 <fpu,de,tsc,msr,mtrr,pge,mmx>real memory  = 528416768 (503 MB) avail memory = 502845440 (479 MB) wlan: mac acl policy registered kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Jan  8 2009 22:07:11) cryptosoft0: <software crypto="">on motherboard padlock0: No ACE support.</software></fpu,de,tsc,msr,mtrr,pge,mmx>

Yes, ae(4) was also added at some point in the past couple months.

Flawless w/daughterboards… http://www.logicsupply.com/products/nc92_330_lf (Jetway NC92-330-LF Dual Core Atom Mini-ITX Mainboard)

Damn! Didn't see dotdashs link before I wrote the above. Okidoki the card doesn't work as AccessPoint. Case closed. Thanks guys!

@jahonix: @jahonix: Usually they make pretty robust stuff and seem to be more common in industrial environments. Sorry, I was totally unclear here. I referred to the AlliedTelesyn stuff. Ahh, ok. Interesting, I might end up with one of their smartswitches some day. Looks ok, not to mention the prising.. To ktims: I was aware of the fan and have worked around other 19" switches so I knew they were (or could be) loud.. that's no issue in a server room though, so perhaps I should simply put it away somewhere in a closet or something, if I keep it.

I hope you can find what's wrong with Via, we almost lost any hope an we are currently trying to switch to another hardware (http://linitx.com/viewproduct.php?prodid=11714). We have got many troubles, going from wrong design in the PCI Raiser (D-Link card wouldn't start) to weird issues with interfaces flapping all the time. If you can solve the problems, please post your recipe. Good luck

thanks for the feedback. Our service over in Canada is much slower (around 4-5 Mbits on average for DSL and Cable) so running slow broadband speeds is not much of an issue for me, I am just happy if it works. I found a xircom 10/1000 dongle PCMCIA and I bought a 3Com 10/100 card today for cheap so hopefully it works out.

Support for the Sangoma may be making its way into pfSense before too long, there has been a bit of buzz on the topic over the last couple days. I know at least one dev has a Sangoma card (for FreeSWITCH) and there is interest in supporting these. Someone else mentioned having a couple on order but it may be 3+ months before anything is done with them. The FreeBSD drivers can be found here: http://www.freshports.org/misc/wanpipe/ Since it's already a FreeBSD port, it may not be that difficult to pull in the necessary bits. You'd just need to compile the KLD on a system that was of the same "vintage" (FreeBSD release) as the pfSense version you're running, copy it over, and have it load on boot. The downside of the Sangoma cards is cost, at $425-500 or so a piece, they have quite a price tag, but there are definitely cases where it is well worth the cost.

The Intel 82573 in the FWA-3710 are supported by the em(4) driver. The Intel 82562 management adapter is supported by the fxp(4) driver.

Do you see this sort of thing in the startup output of 1.2.3? re0: <realtek 8168="" 8168b="" 8168c="" 8168cp="" 8168d="" 8111b="" 8111c="" 8111cp="" pcie="" gigabit="" ethernet="">port 0xd800-0xd8ff mem 0xf7eff000-0xf7efffff,0xf7ee0000-0xf7eeffff irq 18 at device 0.0 on pci4 re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 re0: PHY write failed re0: PHY write failed re0: MII without any phy! device_attach: re0 attach returned 6</realtek> If so, see my remarks in http://forum.pfsense.org/index.php/topic,14994.0.html

Hey thanks for that. I will give it a try and see if it works Cheers Robin

It feels like I've been searching for this exact board for years, but I can never find it.  Yes, you got a good (and rare) choice for pfSense. If you can source any more, PM me.  :)

yes. i appologize, i posted this thread when i was still trying to use pfsense 1.2-stable….the driver in that version didn't work at all when i downloaded 1.2.3 i decided to make my post in that forum instead, seeing as it seemed to be an issue with that version (being based on freebsd 7.1)