What needs to change? Why isn't there Ubiquiti all over them mountain ranges?
If we could change the demographics of the hobby that would help. But to attract some younger tech minded folks is a chicken and egg type of thing. You have to have something first to entice them.
The second problem is regulatory. Data bandwidth issues, content issues.. all deturants.
How many people even know about the 44net space? Maybe we need to reach out to;
-The broadband-hamnet developers - presently they use 10.X.X.X address space
-VOIP developers, like IRLP, Echolink, and Allstar.
-Hams who run internet servers, like qsl.net, etc
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.
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@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of kb9mwr@gmail.com Sent: Wednesday, March 19, 2014 07:03 To: 44net@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@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
The thing that needs to change is that Dynamic AXIP links should be automatically set up by software between all on those on the encap list. That would get the traffic flowing. No more would I have to add and delete links as partners change. Is it possible? Does it exist? Imagine the nodes lists! Cheers Rob VK1KW
-----Original Message----- From: 44net-bounces+vk1kw=netspace.net.au@hamradio.ucsd.edu [mailto:44net-bounces+vk1kw=netspace.net.au@hamradio.ucsd.edu] On Behalf Of kb9mwr@gmail.com Sent: Wednesday, March 19, 2014 4:03 PM To: 44net@hamradio.ucsd.edu Subject: Re: [44net] 44net cool toys - not
(Please trim inclusions from previous messages) _______________________________________________
What needs to change? Why isn't there Ubiquiti all over them mountain ranges?
If we could change the demographics of the hobby that would help. But to attract some younger tech minded folks is a chicken and egg type of thing. You have to have something first to entice them.
The second problem is regulatory. Data bandwidth issues, content issues.. all deturants.
How many people even know about the 44net space? Maybe we need to reach out to;
-The broadband-hamnet developers - presently they use 10.X.X.X address space
-VOIP developers, like IRLP, Echolink, and Allstar.
-Hams who run internet servers, like qsl.net, etc
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@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
This is exactly what the RIPv2 approach does. The moment you change your tunnel endpoint's IP in the portal, the RIPv2 messages will be updated and ALL other partners using RIP will be updated automatically.
The only thing which is missing is an automated approach on the gateway update. Maybe this is a place to do some work on. Something like a dyndns update approach. Challenge/response authentication and automatic gateway update on the portal so that it could be done on a router...
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of vk1kw Sent: Wednesday, March 19, 2014 07:26 To: 'AMPRNet working group' Subject: Re: [44net] 44net cool toys - not
(Please trim inclusions from previous messages) _______________________________________________ The thing that needs to change is that Dynamic AXIP links should be automatically set up by software between all on those on the encap list. That would get the traffic flowing. No more would I have to add and delete links as partners change. Is it possible? Does it exist? Imagine the nodes lists! Cheers Rob VK1KW
__ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
kb9mwr＠gmail.com -
Marius Petrescu -
vk1kw