Hi, On Sat, Jun 10, 2017 at 11:53:55AM -0700, Daryl Morse wrote: > 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.
*if* ip6tables are active, *and* the default policy for "FORWARD" is
to drop packets, *then* you need to have a policy to permit, well,
forwarded packets.
If ip6tables are not active at all, or the default policy is "permit",
then no extra rule is needed.
I just prefer to have firewalls rules out of the way while diagnosing
packet forwarding, so I know "it is not the firewall" if it's not working :)
> 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.
Smells very much like "firewall" to me.
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]
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ 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
