BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Subject: [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- Date: Mon, 21 Oct 2024 15:52:16 -0400
- In-reply-to: <bff819c5-2e6c-40a3-8852-2bd94a8116c3@borg.org>
- References: <20241020173752.44225391.Richard.Pieri@gmail.com> <03f1891735aa9d96d8dee07dfefc98f8.squirrel@mail.mohawksoft.com> <bff819c5-2e6c-40a3-8852-2bd94a8116c3@borg.org>
> On 10/21/24 09:24, markw at mohawksoft.com wrote: >> You set a rule that specific IPs be sent out through the VPN virtual >> interface. > > Just so long as you don't need access to the local version of those > addresses. (The hotel's gateway to get to the rest of the internet? DNS? > Room service?) Well, if there is an IP collision, you can use ports and/or protocols as well. You can also use iptables to direct either on its own or in tandem. > > Maybe use 10.<8-randomly-chosen-bits>.<8-randomly-chosen-bits>.00/24 for > your VPN, then put your key machines at randomly chosen addresses for > that last octet, and those set up rules for those specific IPs. You VPN needn't expose your home IP at all. All you need to do is create a routing table for a rule to use. When the rule identifies how a packet should be routed, it will choose the correct routing table to use. The VPN could be on a 10 or 172 address, or it could be any address, really, as long as it is reachable from your end. > > If you are really a birthday paradox worrier, put those key addresses on > two addresses each and switch rules if you need to. > > -kb > _______________________________________________ > Discuss mailing list > Discuss at lists.blu.org > https://lists.blu.org/mailman/listinfo/discuss >
- References:
- [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- From: kentborg at borg.org (Kent Borg)
- [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Prev by Date: [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Next by Date: [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Previous by thread: [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Next by thread: [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Index(es):