The following sections represent some of the various ways in which a local area network (LAN) can be integrated with the HamWAN network. Please consult the following symbol legend when studying the depicted configurations:
In this mode, a dedicated computer connects to the HamWAN modem and sets its default gateway to point at the HamWAN modem.
In this mode, a second network card is configured to sit on the same subnet as the HamWAN modem. Routing considerations are described below.
In the Dedicated VLAN mode, a virtual network card is configured to sit on the same subnet as the HamWAN modem. The ability to do this is operating system and driver dependent.
In the Shared VLAN mode, no changes are made to the network card, but routes are added to the computer. Routing considerations are described below.
In this mode, the HamWAN router is connected via a dedicated network to the main site router. This leaves the routers to do the routing. Any computers attached to the LAN will benefit from HamWAN routing without any special configuration.
This is the simplest configuration which offers a complete and simple routing picture. A computer simply has its default gateway configured to point at the HamWAN modem and that's it. If only 44-net communication is desired, the computer can be set to learn routes from the HamWAN modem. This is operating-system dependent though.
From a routing perspective, these are all similar configurations. A network card (physical or virtual or pre-existing) is configured to share a common subnet with the HamWAN modem. Then, computer routing table entries are added to tell the computer that certain networks (44-net) are available via the HamWAN modem IP address. This can be as simple as manually adding a static route for 126.96.36.199/8 or as complicated as standing up a routing protocol (BGP / OSPF) between the HamWAN modem and the computer. The ability of the computer to support routing protocols is dependent on the operating system.
This configuration is prone to asymmetrical routing issues, described below.
The routing situation here is much like the one above (Dedicated Network Card / Dedicated VLAN / Shared VLAN). The router dedicates an interface (physical or virtual) to communicating with the HamWAN modem. It then adds routing table entries for 44-net subnets and points them at the HamWAN modem. Most routers have the ability to use routing protocols, so in this sense the situation is improved through automation.
This configuration is also prone to asymmetrical routing issues, described below. However, most routers also have the ability to fix these issues.
There is a potential problem when a packet reaches the computer from 44-space via the ISP connection. Depending on the computer's or main router's routing table, it may send the reply via the HamWAN network. If the computer in question is behind a Network Address Translation (NAT) device and features a private (eg: RFC1918) IP address, the reply packet sent via the HamWAN modem will either carry this private IP address or the HamWAN modem's public address, depending upon the HamWAN modem's egress NAT (SNAT) configuration.
The way to solve this is to ensure that any:
always have their reply packets sent out via the main router's public interface. This can be accomplished on any Linux-based routing platform, and should also be possible on other platforms. Here is a sample RouterOS implementation:
Routing policy to handle asymmetrical responses
/ip firewall connection tracking set enabled=yes /ip firewall mangle add action=mark-connection chain=prerouting dst-address=<Your Public IP> in-interface=<Your Public Interface> new-connection-mark=PublicAMPR src-address=188.8.131.52/8 add action=mark-routing chain=prerouting connection-mark=PublicAMPR new-routing-mark=PublicAMPR /ip route add gateway=<Your Public Gateway> routing-mark=PublicAMPR /ip rule add action=lookup-only-in-table routing-mark=PublicAMPR table=PublicAMPR
The 44-net address pool is small. It's a good idea to use the IP addresses conservatively, especially if your allocation is small. If the goal is to run 44-net IPs on the LAN, then their use can be optimized by only assigning them to the devices which need to be addressable on 44-net directly. The other devices on the LAN which do not participate in 44-net communication or are fine with just outbound 44-net communication can retain private IP space assignments and rely on NAT to communicate with 44-net. The following diagram will be used to depict the various packet flows when a private transit network is used on the LAN.
Both routers in the LAN are speaking OSPF to each other. The HamWAN router is announcing the availability of the user's subnet (184.108.40.206/30) via BGP to HamWAN. On the main router, there exist two static route entries:
The main router is also configured to generate ICMP redirect messages.
Set ICMP redirect generation on RouterOS (default on)
/ip settings set send-redirects=yes
For the sake of this example, we'll assume that the 220.127.116.11/30 subnet is part of a larger HamWAN BGP announcement to the Internet, and is therefore fully routable via HamWAN.
When an external Internet IP wants to communicate with computer A, it sends a packet to 18.104.22.168. This subnet is announced to the Internet via HamWAN, so the packet is delivered to the user's HamWAN router via the microwave interface. Since the HamWAN router has learned of a route for 22.214.171.124/32 via the OSPF session with the Main router, it forwards the packet to the Main router. The Main router then uses its static route for 126.96.36.199/32 and sends the packet to the MAC address of 192.168.0.2. This is computer A, which is the right destination for the packet.
When computer A responds to the packet it just received, it uses its default gateway, which sends the response to the Main router. The Main router needs to apply a routing policy at this point and recognize that the packet is coming from 44-space and going to non-44 space. This means it must leave via an Internet peering point appropriate for the source IP, otherwise it may be subject to egress filtering. In this case, that means it must leave via HamWAN. The Main router forwards the packet to the HamWAN router, and the HamWAN router uses its BGP-learned default route to forward the packet to the HamWAN cell site for the return trip.
|LAN Configuration||HamWAN via||AMPRnet via||Internet via|
|Standalone Private LAN||ISP w/ NAT||ISP w/ NAT||ISP w/ NAT|
|Standalone Private LAN + HamWAN Dish||ISP w/ NAT, HamWAN Dish||ISP w/ NAT, HamWAN Dish||ISP w/ NAT, HamWAN Dish|
|AMPRnet LAN||AMPR Tunnel, ISP w/ NAT||AMPR Tunnel, ISP w/ NAT||ISP w/ NAT, UCSD Tunnel|
|AMPRnet LAN + HamWAN Dish||AMPR Tunnel, ISP w/ NAT, HamWAN Dish||AMPR Tunnel, ISP w/ NAT, HamWAN Dish||ISP w/ NAT, UCSD Tunnel, HamWAN Dish|
|AMPRnet LAN + BGP||ISP, AMPR Tunnel||AMPR Tunnel, ISP||ISP|
|AMPRnet LAN + BGP + HamWAN Dish||ISP, AMPR Tunnel, HamWAN Dish||AMPR Tunnel, ISP, HamWAN Dish||ISP, HamWAN Dish|
Even though HamWAN provides access to all AMPR networks, your commercial Internet service can provide this too! Please do keep packets off the microwave when it's feasible. To accomplish this, your main router should participate in the AMPR tunnel mesh. HamWAN has published software for doing this on RouterOS available here:
When you're importing routes from the HamWAN microwave modem, you may wish to increase their cost compared to these AMPR tunnels you're holding directly.
When you're participating in Internet-facing BGP, you should give preference to the un-tunnelled routes to other AMPR networks. This means your router needs to hold the entire Internet IPv4 table to make a decision between the same prefix being available via IPIP or your ISP. Responses should be handled via either interface.
During a failover event, if NAT is being used, connections will be severed. This is an unpleasant experience for users and applications. If the use of NAT is avoided, the re-routing of packets to a different network can be a seamless operation. HamWAN and AMPR and IANA provide public IP address space to users. If computers are configured to use these guaranteed-unique address spaces, the use of NAT can be avoided, and a seamless failover/failback can be achieved.
When your AMPR subnet is used on a network with more than one BGP peer to the Internet, it is possible to establish redundancy so that neither peer site going down will put your AMPR network offline. To do this, announce a small network to the Internet from your peering locations. At time of writing, the samllest announcable IPv4 network is a /24. A single IP in this network will serve as the IPIP tunnel gateway point announced to the rest of the AMPR participants. This same IP will be used at all of your BGP peering sites (an anycast IP system) to terminate the IPIP tunnels. AMPR partiipants who do not participate in Internet BGP (the majority) will only know to send their AMPR traffic to this one gateway IP. When one of your sites goes down, your peer BGP session will stop, and the Internet will stop sending traffic for your gateway IP to that peer location. Instead, it'll send it to your alternate locations. AMPR participants will not experience any downtime (beyond the dead-peer-detection or BFD interval, and Internet route propagation delay), and AMPR communications will continue as intended.