Hi,
On Sat, Jan 14, 2012 at 04:36:13PM -0500, Praetorian wrote:
> #6 In linux client config file should be dev tun-ipv6 and not just tun-ipv6
The command "tun-ipv6" is not there to set the device, but to enable IPv6
on tunnels :-) - and normally you don't need that command in the client
config at
I finally got around to doing that setup of my test network using the
openvpn debian snapshots and windows test installer. The network consists
of 1 static ip debian 6 linux hub server and 3 dynamic ip debian 6 linux
remote sites and 2 dynamic ip windows (vista and win7) road warriors. After
worki
Hi,
On Sat, Jan 14, 2012 at 12:52:39PM +0100, David Sommerseth wrote:
> | I'm running the master branch (commit 330baf2aee70b35) on a site where
> IPv6
> | tunnelling is not enabled. I found some odd IPv6 addresses in the log
> file
> | when clients connected. Attached is a patch solving this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/01/12 12:47, David Sommerseth wrote:
|
| Hi,
|
| I'm running the master branch (commit 330baf2aee70b35) on a site where IPv6
| tunnelling is not enabled. I found some odd IPv6 addresses in the log file
| when clients connected. Attached is a p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm running the master branch (commit 330baf2aee70b35) on a site where IPv6
tunnelling is not enabled. I found some odd IPv6 addresses in the log file
when clients connected. Attached is a patch solving this issue. It's
basically a bogus mess
