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

Re: [Openvpn-users] 2.0 Feature Freeze Discussion


  • Subject: Re: [Openvpn-users] 2.0 Feature Freeze Discussion
  • From: James Yonan <jim@xxxxxxxxx>
  • Date: Sat, 4 Dec 2004 17:22:56 -0700 (MST)

On Sun, 5 Dec 2004, Vlada Macek wrote:

> George Ross wrote:
> 
> > As I say, you can work around it by running two or more servers,
> > but you're then obliged to guess in advance how to partition up
> > your ifconfig-pool space. It seems a pity, when the server is
> > managing that space anyway.
> 
> I totally support James's effort to keep the software as simple as
> possible. But I also understand your concern that you have to divide
> the ifconfig-pool between multiple daemons prior to run...
> 
> Wouldn't it be the solution to have some sort of shared resource
> between multiple daemons? Shared file or shared memory. This way the
> dynamic IP pool de/allocation events (and possibly some more info)
> could be interchanged.

Yes, that's one of the ideas behind the plugin interface.  You could write 
a plugin (or a script) that would allow multiple daemons, even multiple 
daemons running on different machines, to share the same IP address pool 
configuration.

James


____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users