There appears to be confusion about what client sites will look like. I have had the Client Node Routing <https://www.hamwan.org/t/tiki-index.php?page=Client+Node+Routing&structure=HamWAN> page up for a while, but it did not contain a clear pictographic view, nor a thorough textual description. I've now spent a little time to draw up a clear graphical representation of what to expect at your site. Just hit up that page to see. Your local router and wireless access point are staying, as is your Internet modem. The newly added HamWAN microwave modem + router will simply plug into the LAN side of your network. From a routing perspective, the HamWAN modem will announce routes to your main router via RIP /most likely/ (see below). These are subnets which are accessible via the microwave network and the packets for those subnets should be sent to the microwave modem. Default gateway /should/ (see below) stay as your main ISP. If you have received subnet routing services from HamWAN (ie: you have your own subnet which is announced into the rest of the HamWAN network) then you'll configure your LAN devices with your subnet's IPs. The open problems in this design are: 1) Asymmetric reply traffic when requests come into your HamWAN subnet from Internet IPs. The reply packets will attempt to leave via your ISP since it's your default gateway. We may have to do some policy routing on the main router to mitigate this, or multinet any network devices which want to talk out both networks. To be engineered. 2) DNS queries need to work for at least the HamWAN.net domain despite a total Internet failure (of both your local ISP and HamWAN's Internet links). DNS queries for regular Internet domains should be undisturbed during normal operation. HamWAN should not request any control over user routers beyond the HamWAN modem + router device. On the HamWAN modem + router device, users need to be free to define their own firewall rules and set other settings which do not conflict with HamWAN access policy. --Bart