The moment you start building a high speed network which is ham-only, you
don't need ripd and stuff anymore, except on edge routers.
Insisde that network, all addresses can be 44s, and no tunneling is needed.
And inside one can do a lot of that fancy BGP/OSPF stuff.
(HAMNET in DE and AT is a good example)
Access for hams can be via a simple second network card dedicated to
44.0.0.0/8 WiFi access, so no content issue arrises.
And VPNs can offer a good isolation method on dual stacked networks.
As an example, my home network is done using private IPs (192.168.x.x), with
the usual public IP gateway.
My desktop machine connects via VPN to my local router providing a 44
address for that specific machine (and forwarding the 44 traffic to my 44net
gateway).
Usual traffic goes via local IPs, ham traffic (44.0.0.0/8) via VPN to the
gateway. All other users in my home are on private IPs only with no access
to 44net.
Only traffic from my 44 address to 44 addresses go via VPN, the rest is
regulary routed and NATed.
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of
kb9mwr(a)gmail.com
Sent: Wednesday, March 19, 2014 07:03
To: 44net(a)hamradio.ucsd.edu
Subject: Re: [44net] 44net cool toys - not
(Please trim inclusions from previous messages)
_______________________________________________
...
It would probably help to have our own custom firmware or recommended
hardware. I have to admit, I have been doing everything on a
raspberry pi with a usb ethernet dongle for the second port. I
haven't tried to install the custom rip daemon on something like a
WRT54G or ??
Then there is the issue of how to integrate 44net into your home network.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net