next »

[deadmalc]

I've done a search on the forum for arm support, and can't find anything.
I'm really interested in this, and I have a spare guruplug (changed my router to a dreamplug) and I've ordered a raspberry pi as well. (pi would have to be a dodgy usb ethernet for secondary ethernet....:-( )
Assuming there isn't already a port, is it just a case of using the same version of freebsd as pfsense and compiling it all together?
I figure using a vm is the best way to start this off?
Ideas and suggestions very welcome.

Cheers,

Malcolm

[cmb]

if you can get stock nanobsd to work, you should be able to adapt our build tools to work as well. You're in for a significant amount of work though, and will need to be familiar or get familiar with the FreeBSD build process. All the files you need are in https://github.com/bsdperimeter/pfsense-tools

[Efonne]

The ethernet port on the Raspberry Pi board is internally connected through the USB, IIRC.

[commsbyte]

There are a few peopl I know including myself who are fans of pfsense and already use this is VM.

We are also watching the Rasberry PI.

Would be really pleased if pfsense is ported to ARM processor, so we cna make use of the PI Model B.
Yes a second USB ethernet port would need the drivers working to use it.

It would be useful if someone could create an online survey to record support for this to see how many people are actually interested in using pfsense on an arm processor. If its quie a lot then it would add support to getting it developed and more people helping behind it.

Have seen stuff online about people trying to run off guru plug, but i think the PI looks like a good contender.

[stephenw10]

It would be interesting to know what sort of take up there would be.
Here's some further reading for anyone:
http://wiki.freebsd.org/FreeBSDAvila

Steve

[matguy]

Arm compiling aside, just a thought about the hardware limitations: If your switch supports vlans, couldn't the Pi just tag the WAN and LAN interfaces to vlans on the single port, then your switch could map the vlans to untagged ports on the switch, one for WAN vlan and all the others to the LAN vlan(s).  If I recall correctly, isn't that basically how a WRT54G works internally, single interface to the routing component and the ports are all vlan'd.

Of course, at that point, making sure you have a switch with vlan support probably negates some of the reasons you're looking at a Pi (cost, power, etc.)

[Efonne]

The Netgear ProSafe Plus switches are a fairly inexpensive option for VLAN support.  They do require that you have access to a Windows installation to configure them, though.  The configuration tool does work in a virtual machine that is running Windows.

[robi]

I've also got a bricked GuruPlug plus board (two gigabit ports), would be indeed interesting to recover it and run pfSense on top. I bricked it while installing, so didn't run much time.

I think I could donate it to pfSense community, maybe somebody has enough time to play with it. I offered it too to the DD-WRT community, but nobody was interested.

[tickett]

Very interested. I too am currently virtualizing my pfsense box but might be tempted to move to raspberry pi in an effort to reduce costs.

I can't see that you'd need to have more than one network interface although it would be a nice to have. My virtual machine currently has 3 virtual nics but just one physical nic.