No, because the FORWARD chain didn't have any drops or accepts, as stated in the first post. The config was missing something, which likely was the IPv6 routing I added before I went to bed. Anyway, if this is you leaving, thank you for your criticism. I will keep it in mind if and when sh*t hits the fan.
OpenVPN IPv4 + IPv6 tunnel (not working so far...)
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
-
- OpenVpn Newbie
- Posts: 13
- Joined: Sun Aug 05, 2018 9:56 am
Re: OpenVPN IPv4 + IPv6 tunnel (not working so far...)
-
- OpenVPN Protagonist
- Posts: 11137
- Joined: Fri Jun 03, 2016 1:17 pm
Re: OpenVPN IPv4 + IPv6 tunnel (not working so far...)
As a quick test, you might try without dropping root privileges ..
For example:
Sun Aug 5 09:52:13 2018 us=267119 xxx.yyy.118.252:53338 WARNING: Failed to stat CRL file, not (re)loading CRL.
For example:
Sun Aug 5 09:52:13 2018 us=267119 xxx.yyy.118.252:53338 WARNING: Failed to stat CRL file, not (re)loading CRL.
-
- OpenVpn Newbie
- Posts: 13
- Joined: Sun Aug 05, 2018 9:56 am
Re: OpenVPN IPv4 + IPv6 tunnel (not working so far...)
Or change the ownership of the files I don't want to run OpenVPN as root, I already run it on a non-SELinux system.TinCanTech wrote: ↑Tue Aug 07, 2018 2:08 pmAs a quick test, you might try without dropping root privileges ..
For example:
Sun Aug 5 09:52:13 2018 us=267119 xxx.yyy.118.252:53338 WARNING: Failed to stat CRL file, not (re)loading CRL.
-
- OpenVPN Protagonist
- Posts: 11137
- Joined: Fri Jun 03, 2016 1:17 pm
Re: OpenVPN IPv4 + IPv6 tunnel (not working so far...)
My point was, that is not all you have over looked .. and I did say "quick test" ......
-
- OpenVpn Newbie
- Posts: 13
- Joined: Sun Aug 05, 2018 9:56 am
Re: OpenVPN IPv4 + IPv6 tunnel (not working so far...)
It all works now. I now use PREFIX:3::/64 from my PREFIX::/48 range. All I needed to do was to add a static route in my router for this PREFIX:3::/64 to my local-link address on my eth0 of my Raspberry Pi.