On Thu, Jun 7, 2012 at 12:51 PM, Max Lock
<max@technoghetto.net> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi Eric,
I've done a lot of work making openwrt based hotspot networks in the
past. ddwrt is useful, but there's a couple of issues that come to mind.
Firstly with ddwrt using openvpn you'd have to make changes to
mirrorshades to support openvpn and do you really need the overhead of
encryption?
the mention of using openvpn was mostly intended as a nudge. While IPIP seems to be the defacto standard for amprnet tunneling, it's about the only place I've seen it used much. The tools for tunnels/vpn links are out there but something such as openvpn is much more widely supported than ipip.... now before all those still running nos scream - the whole intent of running such a device is at your network edge. such a device ELIMINATES the need for any tunnels within the local network as the local network just simply becomes a /xx of net 44. in the cases that we tunnel, especially when one has dedicated and easily managed hardware a group of widely supported tunneling (or vpn protocols) ought be employed. the suggestion of open vpn in this case is simply because it's already there in ddwrt-vpn builds, ipip is not (exactly).
Secondly with ddwrt the ability to tune to the ham band is only
possible by using a paid for version that has 'superchannel'
functionality.
This tuning functionality I believe is somewhat chipset dependent but no matter as my intent with the rf part of most boxes on which this runs is not to run 44net over the wireless interface provided on the box. most of the wifi radios on this consumer hardware are subpar anyway. note this is intended as an edge device that connects to one's broadband modem and provides the house network as it always has and the 44net /xx lan on a seperate vlan'd switch port. from there I'd attach servers and carrier class radios over ethernet.
It should be fairly simple to create an openwrt image that sets up an
unencrypted tunnel to mirrorshades, however I've never toyed with
setting odd frequencies on them. Also given that you wouldn't have
unused packages installed you could use the space to install something
amateur radio related.
I really don't see why you'd need to set odd frequencies. also see above.
Finally how would you stop non-ham access?
in light of the above I don't see what the problem is. If I used the wifi radio on said device at all it wouldn't be on 44net but instead a local nonroutable subnet such as 10/8 that was nat to the devices public ip. further, use of mac address filtering, and wpa/radius for authentication and in addition possibly requiring vlan authentication to the node all stand as ways to keep those who are not supposed to have access out. That said, what are you doing to keep non-hams from setting up a 1200 baud tnc attached to a hamband tranciever, assigning it something that looked like a callsign and using your node. I presume nothing, thus the above is or at least could be far more secure.
Eric
-Max G7UOZ.
On Thu, 2012-06-07 at 12:00 -0700, 44net-request@hamradio.ucsd.edu
wrote:
> Has anyone used ddwrt, especially the vpn version to setup a tunnel to ucsd
> > then run rip to get routing announcements? just sounds like a neat low
> > cost way to get a gateway running. This would be trivial if one could run
> > openvpn to mirrorshades.
> >
> > Eric
> > AF6EP
_________________________________________
44Net mailing list
44Net@hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net