On 12/10/16 11:13, Arne Schwabe wrote:
> This option was useful when Ipv6 tun support was non standard and was
> an internal/user specified flag that tracked the Ipv6 capability of
> the tun device.
>
> All supported OS support IPv6. Also tun-ipv6 is pushable by the
> remote so not putting tun-ip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please disregard this mail. I will resent it again without getting it
destroyed by Engimail's text wrapping.
David S.
On 13/10/16 17:52, David Sommerseth wrote:
> On 12/10/16 11:13, Arne Schwabe wrote:
>> This option was useful when Ipv6 tun supp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/16 11:13, Arne Schwabe wrote:
> This option was useful when Ipv6 tun support was non standard and
> was an internal/user specified flag that tracked the Ipv6
> capability of the tun device.
>
> All supported OS support IPv6. Also tun-ipv6 is
Thanks to both Gert and Arne for their answers.
On Wed, Oct 12, 2016 at 9:12 AM, Arne Schwabe wrote:
>> What I should have asked is: with this patch will an OpenVPN client
>> still send out IPv4 packets if there are no IPv6 options specified or
>> pulled from the server?
> What I should have asked is: with this patch will an OpenVPN client
> still send out IPv4 packets if there are no IPv6 options specified or
> pulled from the server?
In short: Behave exactly as before.
Longer explaination:
Without the patch OpenVPN refuses ifconfig-ipv6 and route-ipv6 without
Hi,
On Wed, Oct 12, 2016 at 08:53:02AM -0400, Jonathan K. Bullard wrote:
> What I should have asked is: with this patch will an OpenVPN client
> still send out IPv4 packets if there are no IPv6 options specified or
> pulled from the server?
Yes. Basically, the tun interface is now always in "du
Thanks, Arne. Sorry if I wasn't a clear as I should have been.
On Wed, Oct 12, 2016 at 8:08 AM, Arne Schwabe wrote:
>
> Am 12.10.16 um 13:17 schrieb Jonathan K. Bullard:
> > Hi.
> >
> > On Wed, Oct 12, 2016 at 5:13 AM, Arne Schwabe wrote:
> >> This option was useful when Ipv6 tun support was
> >
Am 12.10.16 um 13:17 schrieb Jonathan K. Bullard:
> Hi.
>
> On Wed, Oct 12, 2016 at 5:13 AM, Arne Schwabe wrote:
>> This option was useful when Ipv6 tun support was
>> non standard and was an internal/user specified flag
>> that tracked the Ipv6 capability of the tun device.
>>
>> All supported
Hi.
On Wed, Oct 12, 2016 at 5:13 AM, Arne Schwabe wrote:
>
> This option was useful when Ipv6 tun support was
> non standard and was an internal/user specified flag
> that tracked the Ipv6 capability of the tun device.
>
> All supported OS support IPv6. Also tun-ipv6 is
> pushable by the remote s
Hi,
On Sat, Sep 17, 2016 at 12:36:16PM +0200, Arne Schwabe wrote:
> @@ -1127,6 +1127,8 @@ do_ifconfig (struct tuntap *tt,
>if ( do_ipv6 )
> {
> #ifdef NETBSD_MULTI_AF
> +#error no IPv6 support for tun interfaces on NetBSD before 4.0, upgrade your
> system.
> +#endif
If we keep thi
10 matches
Mail list logo
