17 Apr
2013
17 Apr
'13
6:06 p.m.
In NYC we have a similar problem. We are unable to connect directly to our
smaller hubs via RF.
A solution we are working on is based on OpenVPN. We don't have it in
production yet but it looks good so far. Our central hub (n2nov.ampr.org)
actually lives in a data center and so has no RF abilities but it is the
master gateway for our subnet and mail repo etc. The borough hubs should
connect back to the central hub over the Internet. This means that our
entire City wide network can function in the same way at every node/hub. We
also don't have to worry about varying infrastructure abilities at each
site as the OVPN client runs directly on the hub box. We use JNOS and
Debian.
In short, our gateway will handle all the external linking and
borough-to-borough connections which means that we only need user access
ports. In the event that we need a backup RF outlet we are able to connect
to a partner gateway in NJ which in turn has HF/VHF/Internet abilities.
On Wed, Apr 17, 2013 at 1:38 AM, <kb9mwr(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
I am running a gateway using rip, etc. I really only have wifi radio
range to a couple other hosts. And that is working well.
We have a couple other small wireless networks in town that I can't reach
by radio. They could be connected to the internet but unfortunately would
be behind firewalls that we cannot control.
So till we get things realigned and such, I am looking for examples on how
to create a private tunnel from my gateway to those locations.
It doesn't really make sense to put another gateway in the portal, as I
doubt the rip packets will pass though.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html