Hey all, We're still working in the Washington, DC area on our HSMM Mesh network. At this point, I've been solving an issue when - those who have gateways and routes to AMPR will properly route. The only solution thus far is - those in the area with direct interconnections to AMPR as well as the Internet, will have to route them (lol). This requires announcing specific routes on the network. Mesh uses OLSR. My plan: - I'll make an Ethernet interface that is on the Mesh, we plan to get an allocation from AMPRNet (soon) for this - I'll run OLSR on this interface The script: - The current dynamic firewall script that now runs (see Wiki), will take the 44 networks and announce them in HNA I need assistance with developing that new portion of the script. I'm currently working on setting up a test to an adjacent HSMM node. Why can't the Mesh speak RIP44? - It will, we plan to setup another service with public keys that will change our DDNS name to the main router, it will start an election for if an Operator looses a good route via their Internet to AMPRGW. - While we plan to run the Mesh's tunnel with BGP eventually, the network will be configured to assume that the route to 0.0.0.0/0 is general on OLSR, and there are multiple gateways, others authorized to announce the Internet will use more specific routes like 0.0.0.0/1 and 128.0.0.0/1...etc...the main router will announce the Internet to the mesh by 255 /8 networks. - This network will be hybrid, unless you connection track the packet, it can return any direction - Masquerade when necessary, lol 73, - Lynwood KB3VWG