<html><head>
</head>
<body style="padding-bottom:40px">
<div style="font-size: 10pt; "><p dir="ltr" style="margin-top:0;margin-bottom:0;"><br></p></div>
<div style="font-size: 10pt; "><div id="LGEmailHeader" dir="ltr" style="margin-top:0;margin-bottom:0;"><p dir="ltr" style="margin-top:0;margin-bottom:0;">Hi Tobias,</p><p dir="ltr" style="margin-top:0;margin-bottom:0;"><br></p><p dir="ltr" style="margin-top:0;margin-bottom:0;">I forgot to mention that I use my own updown script based on your default script to integrate strongswan into my firewall. I'm simpling writing all environment variables I'm interested in from that script into a file if client-up is called. My routing tables are also a bit different than in a normal setup. I decided to handle the routes myself and took your script as a starting point. Now I know where I went wrong.</p><p dir="ltr" style="margin-top:0;margin-bottom:0;">ip route get <peer_ip></p><p dir="ltr" style="margin-top:0;margin-bottom:0;">gives me the parameter I was looking for.</p><p dir="ltr" style="margin-top:0;margin-bottom:0;">So never mind and thanks.</p><p dir="ltr" style="margin-top:0;margin-bottom:0;"><br></p><p dir="ltr" style="margin-top:0;margin-bottom:0;">------ Originalnachricht------</p><p dir="ltr" style="margin-top:0;margin-bottom:0;"><b>Von: </b>Tobias Brunner<tobias@strongswan.org></tobias@strongswan.org></p><p dir="ltr" style="margin-top:0;margin-bottom:0;"><b>Datum: </b>Di., 17. Feb. 2015 14:38</p><p dir="ltr" style="margin-top:0;margin-bottom:0;"><b>An: </b>Christian Liebscher<a href="mailto:;users@lists.strongswan.org">;users@lists.strongswan.org</a>;</p><p dir="ltr" style="margin-top:0;margin-bottom:0;"><b>Betreff:</b>Re: [strongSwan] updown script not adding routes</p><p dir="ltr" style="margin-top:0;margin-bottom:0;"><br></p></div><pre>Hi Christian,> I've noticed something about the updown script that doesn't seem right.> With Revision 881e9a7e of src/_updown/_<a href="http://updown.in">updown.in</a> the> description of PLUTO_NEXT_HOP got removed, because it is not supported> by charon. But the usage still remains and is still there @master. What> currently happens is that the routes are not added at all, because the> generated command line for "iproute2" is not <a href="http://valid.Th">valid.Th</a>ese commands have never been used by charon. Charon installs routesdirectly via Netlink/PF_ROUTE.> Because> PLUTO_NEXT_HOP is not supported by charon this script will try to add a> route via the peer itself. The peer, in almost all setups, is not in the> same subnet, so adding this route will <a href="http://fail.Th">fail.Th</a>e script will do no such thing because it will never be called withthe route-* commands by the updown plugin. The reason this obsoletestuff is still in the script is because nobody yet felt a need to removeit. But since you brought it up, I will give it a go :)> Did I miss something?A route should still get installed to table 220 by the kernel-netlinkplugin (on Linux). If that's not the case check the log for <a href="http://errors.Re">errors.Re</a>gards,Tobias</pre></div></body></html>