Ames Community Network   RoutingNodes UserPreferences
 
HelpContents FindPage Diffs Info Edit Subscribe XML Print View

on routing the various acn nodes

getting the various WireLess 10.140.0.0/14 [Self]nodes talking to each other, in absence of a complete city-wide mesh network, will require some sort of tunneling.

Waldo has set up an [WWW]OpenVPN server at dusty.dorkzilla.org (can i get an amescommunity.net subdomain or something?)

contact Waldo via the acn-discuss [WWW]mailing list to get an ssl cert.

this functionality will, obviously, require a router at your node that can run OpenVPN. This limits us for now to [WWW]OpenWRT-capable commodity routers and "real" computers.

a sample client config

client 
dev tun
proto udp
remote dusty.dorkzilla.org 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert acn-test.crt
key acn-test.key
comp-lzo
verb 3

Inter-node Routing

Currently all routing is done statically. In the future an interior gateway routing protocol will need to be employed. These protocols include RIPv2 (simple but lacking scalability) and OSPF (complicated and capable). An advantage of RIP is that an implementation of it is part of the *BSD base system.

using NetBSD routed(8)

(may also work on other *BSDs)

In an experiment conducted by JonathanKollasch this didn't work as well as expected. He used gif(4) to tunnel IPv4 between two NetBSD routers connected only via IPv6. The IPv4 routes only propagated in one direction. Suffice it to say this won't work. I've yet to try another implementation such as Quagga, Zebra or XORP.

In another attempt at the same setup it worked fine. This greatly surprised JonathanKollasch. He is unsure if he did anything differently. This unreliability does not bode well for routed(8).

Routed(8) over an OpenVPN tunnel has not worked so far.

The next experiment will likely involve an OpenVPN tunnel rather than a gif(4) tunnel.

what comes next?



PythonPowered