[fedora-arm] Simple routing device advice (mildly OT)

[Robert Moskowitz]

I am working with the Cubieboards doing similar things.  I got a 
Cubieboard 2 with case and 5v2a powersupply for $60.  Only one ethernet, 
you will need to add a USB nic.  Or a one arm router into a VLAN switch. 
Right now I am running F20 remix on it.  'Soon' F21 real will be 
available, and there is work on Centos 7 for v7 SOCs.

And the Cubieboard as a SATA2 interface, so your OS can be on it.

On 07/21/2014 07:59 PM, Pete Travis wrote:
> Hello Fedora ARM hackers,
>
> I'm shopping around for a device to provide basic routing and firewall
> functions.
>
> The goal is to provide remote access to an IP camera through satellite
> internet connection.  To keep the camera and link from getting buried or
> abused, I want to limit access to connections from a particular /25. If
> using a dynamic IP, the satellite modem uses NAT and does not offer
> firewall or port forwarding capability.  If using a static IP, a public IP
> is routed directly to the inside device, without a firewall.
>
> I'm thinking a small multipurpose ARM device would be a cost effective
> solution.  Any problems that can't be resolved via ssh will be dealt with
> by post or remote hands, so it must be fairly reliable, not require user
> intervention to survive power cycles, etc.  I'd like a dual Ethernet
> device, but a USB nic could do.  There will need to be a case or finished
> chassis of some sort, preferably one that could protect that second NIC
> from accidental disconnection or tampering.
>
> Is there anything on the market that fits the bill, or am I better off with
> some OpenWRT supported consumer router, or maybe something else?
>
> --Pete
>
>
>
> _______________________________________________
> arm mailing list
> arm at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/arm/attachments/20140721/3561f2ab/attachment.html>