Hi Gert,

Thank you very much for the reply.

Since the linux host is behind a firewall, there is no strict requirement
for it to have its own firewall, at least for security reasons. However, for
ipv4, ufw is used to nat the private address (10.8.0.x) to the lan address.
The VPN did not work at all for ipv4 until I added the masquerade rule to
ufw. (iptables can be used directly as well.) My understanding is that an
ip6tables rule is required to forward packets from the tun interface to the
eth interface.

Both ipv4 and ipv6 forwarding are turned on in the openvpn server.

The openvpn server is on the lan which has a default route for the delegated
prefix/64. From the openvpn server, it's possible to ping outside ipv4 and
ipv6 addresses. It's just not possible from the client, even though the
client and server can ping each other using both ipv4 and ipv6. Packets
don't seem to be getting across from the tun interface to the eth interface.

I'll do some further testing and post the results.

Cheers,
Daryl

-----Original Message-----
From: Gert Doering [mailto:[email protected]] 
Sent: Saturday, June 10, 2017 10:52 AM
To: [email protected]
Cc: [email protected]
Subject: Re: [Openvpn-users] Need help with Ubuntu 16.04 LTS OpenVPN 2.4
Dual-Stack Server Firewall Configuration

Hi,

On Sat, Jun 10, 2017 at 10:13:36AM -0700, [email protected] wrote:
> I found another tutorial from a few years ago for openvpn ipv6 on Debian.
It's here: https://www.tecmint.com/install-openvpn-in-debian/. Not clear of
all of the extra scripts are required, but it had some ip*tables rules.

Unless you need NAT, you should first try to make it work with no firewall
active at all - this can be hard enough, and if you're not sure if the
firewall is getting in your way or whether it's just plain routing,
searching gets more annoying.

When the firewall is *off*, verify the following:

 - ipv6 forwarding is turned on on the server (often overlooked)
 - the default router has a route for the openvpn IPv6 network towards
   the openvpn server  (for IPv4, it uses NAT with masquerading, but
   the IPv6 config with no NAT needs a route *back* so response packets
   can be delivered)
 - that you can ping openvpn client (::1000) -> openvpn server (::1)
   and back
 - if that works, try traceroute6 from the openvpn client towards a
   target that should be behind the VPN, and see how far you get
 - and do a traceroute6 from "somewhere out" towards the openvpn client,
   and see how far you get

(this is really basic *routing*, and not so much "openvpn setup", so most
people go looking in the wrong configs...)

For added insight

 - do tcpdump on all involved interfaces (openvpn client tun, openvpn
   server tun and LAN interface, next router's LAN and WAN interface)
   when you do the traceroutes, and see where the packets show up

gert
--
USENET is *not* the non-clickable part of WWW!
 
//www.muc.de/~gert/
Gert Doering - Munich, Germany
[email protected]
fax: +49-89-35655025
[email protected]


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to