Re: IPsec help: too much NAT!

2018-01-26 Thread Kenneth Gober
When faced with an ISP modem/router, I generally try to switch it to bridge mode and move the PPPoE / DHCP client formerly handled by the ISP hardware to the OpenBSD system instead. This rather simplifies things if you can make it work because then your OpenBSD system has the Internet-facing addre

Re: IPsec help: too much NAT!

2018-01-25 Thread Stuart Henderson
On 2018-01-25, Lyndon Nerenberg wrote: > I have an IPsec conundrum I'm trying to solve. Yes, the scenario > is somewhat absurd; it's also the problem I've been taksed with > solving, so spare the peanut gallery comments, okay? > > > NET-P GW-Q <-> internet <-> GW-H GW-V NET-V > > NET-P is 10.0

Re: IPsec help: too much NAT!

2018-01-25 Thread Lyndon Nerenberg
NET-P GW-Q <-> internet <-> GW-H GW-V NET-V In the schematic above, '' represents a NAT translation point. '<->' is a regular router interconnect. Except for where I screwed up, of course. That should read: NET-P GW-Q <-> internet <-> GW-H GW-V <-> NET-V I.e. the GW-V <-> NET-V interf

IPsec help: too much NAT!

2018-01-25 Thread Lyndon Nerenberg
I have an IPsec conundrum I'm trying to solve. Yes, the scenario is somewhat absurd; it's also the problem I've been taksed with solving, so spare the peanut gallery comments, okay? NET-P GW-Q <-> internet <-> GW-H GW-V NET-V NET-P is 10.0.2.0/24 NET-V is 10.0.11.0/24 GW-Q is an OpenBSD ho