[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] Exiting from 'Management Interface' causes openvpn 2.0rc7 daemon to die


  • Subject: Re: [Openvpn-users] Exiting from 'Management Interface' causes openvpn 2.0rc7 daemon to die
  • From: Christian Røsnes <christian@xxxxxxxxx>
  • Date: Thu, 13 Jan 2005 18:13:14 +0100

On Thursday 13 January 2005 14:51, Christian Sander Røsnes wrote:
> I've got OpenVPN 2.0rc7 running on an OpenBSD 3.6 DS10 Alpha server.
> The OpenVPN server works fine as far as tunneling goes.
>
> However, when I exit the 'Management Interface', the OpenVPN daemon
> for this Management Interface dies.
>
>
> # server3.cfg
> chroot /openvpn/chroot
> dev tun3
> ...
> user nobody
> group nobody
> comp-lzo
> persist-key
> persist-tun
> log  /openvpn/chroot/openvpn3.log
> verb 3
> status  /openvpn/chroot/openvpn3.status 10
> status-version 2
> management 127.0.0.1 1103

The problem occurs when I run the daemon as user 'nobody'.
Commenting out the "user nobody" parameter, ie. running as root, fixes the 
problem.

Log running as 'root':
Thu Jan 13 18:11:23 2005 MANAGEMENT: Client connected from 127.0.0.1:1103
Thu Jan 13 18:11:24 2005 MANAGEMENT: CMD 'exit'
Thu Jan 13 18:11:24 2005 MANAGEMENT: Client disconnected
Thu Jan 13 18:11:24 2005 MANAGEMENT: TCP Socket listening on 127.0.0.1:1103


However, I wonder why user 'nobody' is not allowed to bind to port 1103 ?

Christian


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users