[Openvpn-devel] Working with 2.6
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 existing (commented out) directives in the devfs configuration for this. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson
Re: [Openvpn-devel] Working with 2.6
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 alter by devfs > configuration because the tun device has moved from /dev/net/tun to > /dev/misc/net/tun -- fortunately there are existing (commented out) > directives in the devfs configuration for this. > > -- > Democracy is two wolves and a sheep voting on what to have for dinner. > Liberty is two wolves attempting to have a sheep for dinner and > finding a well-informed, well-armed sheep. > > Jon Nelson > > > --- > This SF. Net email is sponsored by: GoToMyPC > GoToMyPC is the fast, easy and secure way to access your computer from > any Web browser or wireless device. Click here to Try it Free! > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl > ___ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel
Re: [Openvpn-devel] Working with 2.6
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 you want to simply test it out, do this: cd /dev/net ln -s ../misc . 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) config. > 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 alter by devfs > > configuration because the tun device has moved from /dev/net/tun to > > /dev/misc/net/tun -- fortunately there are existing (commented out) > > directives in the devfs configuration for this. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson
Re: [Openvpn-devel] Working with 2.6
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 solution is contained within. > If you want to simply test it out, do this: > > cd /dev/net > ln -s ../misc . > > 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) config. I'm not running 2.6 yet, but if someone gives me ssh access, I will fix. What precisely needs to be done? Is it just a matter of trying an alternate device node name, or is there more involved in porting to 2.6? James > > 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 alter by devfs > > > configuration because the tun device has moved from /dev/net/tun to > > > /dev/misc/net/tun -- fortunately there are existing (commented out) > > > directives in the devfs configuration for this. > > -- > Democracy is two wolves and a sheep voting on what to have for dinner. > Liberty is two wolves attempting to have a sheep for dinner and > finding a well-informed, well-armed sheep. > > Jon Nelson > > > --- > This SF. Net email is sponsored by: GoToMyPC > GoToMyPC is the fast, easy and secure way to access your computer from > any Web browser or wireless device. Click here to Try it Free! > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl > ___ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel > --
Re: [Openvpn-devel] Working with 2.6
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' devices, restarted devfsd, and it worked. > Is it just a matter of trying an alternate device node name, or is > there more involved in porting to 2.6? Again, not sure. BTW, beta14 shows nothing different over beta12, which is to say it runs just fine (with the aforementioned devfs config changes). Also note that since devfsd is now deprecated, I do *not* know what interface (if any) replaces it. I'm dipping my toe into this 2.6 water just as many others are. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson
Re: [Openvpn-devel] Working with 2.6
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) config. > > I'm not running 2.6 yet, but if someone gives me ssh access, I will fix. I can offer you daytime/evening (European time zones) access on a 2.6 BK (post -test9) machine if need be, however, I don't see any difficulties on my 2.6 machine talking to a FreeBSD 4.9 hosted OpenVPN 1.4.2. I don't use devfs, so my machine may not be what you need. James, if you still need ssh access, please send your ssh2 public key. It seems the problem is devfs related (and then might be worked around with the new --dev-* options).
