141 reputation
117
bio website
location
age
visits member for 1 year, 10 months
seen Mar 12 at 20:30

Sep
24
comment Tunneling a public IP to a remote machine
"Also there is this..." Yeah, I mentioned Ethernet bridging in my question. It seems like this might be the only way to get things working without pulling my hair out, although I'd really prefer a point-to-point IP tunnel if possible.
Sep
24
comment Tunneling a public IP to a remote machine
"You are going to need to open a port somewhere for an OpenVPN server". All ports are open. A is directly on the Internet.
Sep
24
comment Tunneling a public IP to a remote machine
"it won't know if it should use the WAN, the LAN, or the OpenVPN" -- The OpenVPN server at A should be sending its packets back to their source address and port, which would be the NAT firewall at B (not in 8.8.8.0/29), so I don't think there's any confusion there. Note there's no LAN at A, just the WAN.
Sep
24
comment Tunneling a public IP to a remote machine
To be clear, I want to create tunnel directly between A and B, not on separate firewalls at each end.
Sep
24
comment Tunneling a public IP to a remote machine
I don't understand how intermediate firewalls are involved; they certainly won't be looking inside the OpenVPN packets between A and B. For the OpenVPN config itself, I was expecting that something like push "route 50.7.19.122 255.255.255.255 net_gateway" would ensure that the VPN data is still pushed over the normal network.
Sep
24
comment Tunneling a public IP to a remote machine
Michael: Yes, I changed the first three octets to 8 to obfuscate them, but still indicate that they're public. Sorry, Google.
Sep
24
comment Tunneling a public IP to a remote machine
Robert: A is a Linux server with some simple iptables rules. B is behind a NAT that is another Linux server running shorewall.