Admin/Resubnetting

The issue

The current setup is this: the gateway acts as an arp proxy from the 136.201.0.0/16 subnet that ul uses to the 136.201.105.0/24 subnet that skynet uses.

This has the following problem: if we add a second gateway, it'll also be in the 136.201.105.0/24 subnet, and therefore the first gateway will still try to do proxy arp for it, causing general badness.

If we want to have a redundant gateway, we have two choices:

  1. have the backup gateway not be addressible

  2. re-subnet our subnet to work around this

(A) is undesirable as we lose the ability to access the backup gateway externally, which will be needed if the primary gateway falls over and the failover fails. Therefore, (B) is the way forward.

The proposal

Move the gateways to the 136.201.105.240/28 subnet (host IPs 136.201.105.241 -> 136.201.105.254) for their external interfaces. Specifically, the active gateway should be 136.201.105.254, the backup gateway 136.201.105.253, with the static IPs for the gateways being 136.201.105.251 and 136.201.105.252. The subnet mask will be 255.255.255.240.

All other machines will be moved to the 136.201.105.0/26 subnet (host ips 136.201.105.1 -> 136.201.105.62). This has the advantage that they won't need to change their IPs, just their subnet masks and gateways (i.e. we don't have to change dns for a start).

The gateways internal interfaces will also be moved to the 136.201.105.0/26 subnet. The active gateway should be 136.201.105.62, the backup gateway will be 136.201.105.61, with the static IPs for the gateways being 136.201.105.60 and 136.201.105.59.

How/Why it works

There is no longer any problem with having multiple gateways. They are only trying to do proxy arp for the internal IPs, which are in a different subnet to the gateway IPs.

last edited 2006-07-08 21:21:07 by 87