[OpenWrt-Devel] openconnect does not remove default routes [was: Some OpenConnect observations]

Nikos Mavrogiannopoulos nmav at gnutls.org
Mon Jan 5 03:31:19 EST 2015

On Mon, Jan 5, 2015 at 8:00 AM, Gottfried Haider
<gottfried.haider at gmail.com> wrote:
>> It seems that you use openconnect to set a default route, and that's why
>> I couldn't reproduce it. I don't think that openconnect handles default
>> routes differently, so it could be an issue in netifd. As I see default
>> routes are registered using proto_add_ipv4_route, and should have been
>> automatically removed when proto_kill_command is called in
>> openconnect.sh.
>> Most probably you'll have to check the log (readlog), and possibly add
>> some additional logging in:
>> /lib/netifd/netifd-proto.sh
>> /lib/netifd/proto/openconnect.sh
>> Sorry for not being able to help more. Maybe someone in the
>> openwrt-devel list will be able to help with that.
> Thanks for those pointers. I could follow the execution all the way to
> vpnc-script, so openconnect gets called with SIGINT and cleanly closes
> the connection. In the disconnect case in vpnc-script, I only see
> calls to proto_init_update and proto_send_update, whereas in connect
> the script did the heavy lifting to setup those routes... where do
> these calls go, do you happen to know? (primarily trying to figure out
> whether its openconnect or some part of netfid that I should look
> into)

My understanding is that they are rpc, go to netifd daemon, which
calls openconnect.sh shortly after that.

openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list