connect-script double call
Nikos Mavrogiannopoulos
nmav at gnutls.org
Sat Apr 12 01:57:33 PDT 2014
On Sat, 2014-04-12 at 15:56 +0800, Steve wrote:
> Hi, Nikos
>
> Tested the latest git, seems still not right, here the log from
> script, you can a fresh new connection will trigger connect twice and
> disconnect once. It should be only one connected log?
>
> User 'user1' from 'x.x.x.x' connected. Local IP is '172.16.220.149'
> User 'user1' from 'x.x.x.x' connected. Local IP is '172.16.220.149'
> User 'user1' from 'x.x.x.x' disconnected.
That's correct, and I couldn't avoid it. I've documented it as:
"Note that a "disconnect" call will not contain the IP information
of the client, if the client has reconnected with a cookie (and thus
re-used its IP addresses)."
and since I documented it, it is no longer a bug :) Seriously now, I
couldn't figure a better behavior. Sending the IP back would have been
wrong, as it is being used by another session.
> BTW, is it possible to send user's traffic bytes info in disconnect?
You could use ifconfig on the device of the user. The stats of the tun
device are the stats of the user. This is how occtl reports the traffic
bytes.
regards,
Nikos
More information about the openconnect-devel
mailing list