[PATCH -ocserv 4/5] Use distinct remote and local IPs when explicit_ipv[46] is specified
Nikos Mavrogiannopoulos
nmav at gnutls.org
Wed Feb 11 01:22:46 PST 2015
On Tue, Feb 10, 2015 at 11:10 AM, Nikos Mavrogiannopoulos
<nmav at gnutls.org> wrote:
> That would have to require additional configuration options. Thus,
> I've now applied Kevin's patch, and if addresses that are not managed
> by ocserv (i.e., explicit) are used, then only odd address will be
> accepted and the next even will be used as the local address.
Thinking of it again, would we have any problem if we always use the
first address of the setup network as our local address? That is use
192.168.1.0 (when our network is 192.168.1.0/255.255.255.0). That
would simplify quite a lot the current assignment process and free us
from reserving two IPs per connection.
More information about the openconnect-devel
mailing list