Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save paigeadelethompson/c36507a6bfc5b2c1650de3adeb6285a5 to your computer and use it in GitHub Desktop.

Select an option

Save paigeadelethompson/c36507a6bfc5b2c1650de3adeb6285a5 to your computer and use it in GitHub Desktop.
say you have a VPS ..
- it has a wan address of 208.79.92.66/24
- you can assign more addresses but it doesn't do you a hell of a lot of good because you want to pilfer addresses from that
/24 for other servers
- create a tunnel between your VPS and the host that you want to have use the address, lets say we're going to use
208.79.92.67/24 and 208.79.92.68/24
- tunnel remote is 10.0.0.1 tunnel local is 10.0.0.2
- add a route to 208.79.92.67/32 via 10.0.0.1
- add an ARP proxy entry; what this does is sends ARP saying 208.79.92.67 is at <mac address of interface that 208.79.92.66/24
is assigned to>. Ordinarily, when you assign an address to an interface it does this, but we don't want to assign the address,
we simply want to advertise ARP
What this accomplishes:
- all traffic destined for 208.79.92.67 will be forwarded to the mac of the VPS WAN interface in the ethernet portion of the
header. Your machine receives it, and sees that it doesn't have this address assigned to a local interface but does see that
there is a /32 entry in the routing table and assuming forwarding is enabled--forwards it thru 10.0.0.1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment