Just so you all know, I'm using OpenVPN 1.5beta12 (soon to be beta14)
with Linux 2.6.0-test9 (vanilla, no patching).
The only problem I encountered is that I had to alter by devfs
configuration because the tun device has moved from /dev/net/tun to
/dev/misc/net/tun -- fortunately there are existin
I've had a simular problem too. 2.6 and Openvpn are a no go.
Matt H.
On Tuesday 18 November 2003 08:18 am, Jon Nelson wrote:
> Just so you all know, I'm using OpenVPN 1.5beta12 (soon to be beta14)
> with Linux 2.6.0-test9 (vanilla, no patching).
>
> The only problem I encountered is that I had to
On Tue, 18 Nov 2003, Matt wrote:
> I've had a simular problem too. 2.6 and Openvpn are a no go.
Why? I easily got it running after just a few minutes of debugging.
Indeed, it's been working fine for me for the last few days.
Didn't you read the whole email? The solution is contained within.
If
Jon Nelson said:
> On Tue, 18 Nov 2003, Matt wrote:
>
> > I've had a simular problem too. 2.6 and Openvpn are a no go.
>
> Why? I easily got it running after just a few minutes of debugging.
> Indeed, it's been working fine for me for the last few days.
> Didn't you read the whole email? The
On Tue, 18 Nov 2003, James Yonan wrote:
> I'm not running 2.6 yet, but if someone gives me ssh access, I will
> fix.
No offence, but you're not about to get access to my network. ;-)
> What precisely needs to be done?
Honestly, I don't know. All I did was edit the devfs configuration for
'misc
On Tue, 18 Nov 2003, James Yonan wrote:
> > That should allow openvpn to open the tun interface.
> > If that works, and you can't figure out what lines in the devfs
> > configuration to edit, post to this list and I'll see if I can determine
> > what exactly it is that I changed in the (devfsd) co
