Re: [strongSwan] Route not working as expcted

2020-09-28 Thread strongswan . org
Hi Noel, Thank you for already looking in to this and your reply. All of a sudden everything started working about an hour ago. After asking it turns out the other end changed there settings and now all is working as expected. Kind rgds, Ben On 28-09-2020 11:33, Noel Kuntze wrote: Hello, P

[strongSwan] Separate logging details/logfile for each ike_name?

2020-09-28 Thread JR
Hi We're running multiple tunnels using StrongSWAN. It would be very useful to be able to set different debugging levels for different ike_name entries, and ideally to be able to output to different log files. Is this currently possible? I can see how to enable ike_name in the logging, but not h

Re: [strongSwan] updown - server which disconnects one roadworrior when another connects

2020-09-28 Thread Noel Kuntze
Hi, Sorry for the mistake. Kind regards Noel Am 28.09.20 um 11:52 schrieb Tobias Brunner: > Hi, > >> up-client is called for each combination of remote ts and local ts >> components, as is down-client, when a CHILD_sa is established/destroyed. >> So when a CHILD_SA is rekeyed, both are called

Re: [strongSwan] updown - server which disconnects one roadworrior when another connects

2020-09-28 Thread Noel Kuntze
Hi, > Is that behavior controllable somehow, configured somewhere > - would you know? > Or it's the user/admin which must take care of this > 'issue/phenomena' via the 'updown' script and the script alone? Not controllable, you need to deal with it in the script. Kind regards Noel Am 28.09.20

Re: [strongSwan] Route not working as expcted

2020-09-28 Thread Noel Kuntze
Hello, Please provide all information as listed on the HelpRequests[1] page. Kind regards Noel [1] https://wiki.strongswan.org/projects/strongswan/wiki/HelpRequests Am 27.09.20 um 16:36 schrieb strongswan@it-beheer.eu: > Hello everyone, > > I am having problems getting an ip range over a

Re: [strongSwan] updown - server which disconnects one roadworrior when another connects

2020-09-28 Thread Noel Kuntze
Hi, up-client is called for each combination of remote ts and local ts components, as is down-client, when a CHILD_sa is established/destroyed. So when a CHILD_SA is rekeyed, both are called in the order the CHILD_SAs are negotiated/destroyed. Kind regards Noel Am 28.09.20 um 10:58 schrieb le

Re: [strongSwan] Separate logging details/logfile for each ike_name?

2020-09-28 Thread Tobias Brunner
Hi, > Is this currently possible? I can see how to enable ike_name in the > logging, but not how to send to different output. No, that's not possible. You'd have to write your own logger plugin that does something like that, or do this in your logging daemon, or post-process the log files. Note

[strongSwan] updown - server which disconnects one roadworrior when another connects

2020-09-28 Thread lejeczek
Hi guys. I have a strongswan with 'updown' which controls tunnels, routes, etc. I took the script from doc examples and built upon it. What is perplexing totally to me is, that the scripts shows that when one roadwarrior is connected and another one is connecting then the server invokes 'down-clie

Re: [strongSwan] updown - server which disconnects one roadworrior when another connects

2020-09-28 Thread lejeczek
On 28/09/2020 10:52, Tobias Brunner wrote: > Hi, > >> up-client is called for each combination of remote ts and local ts >> components, as is down-client, when a CHILD_sa is established/destroyed. >> So when a CHILD_SA is rekeyed, both are called in the order the CHILD_SAs >> are negotiated/des

Re: [strongSwan] updown - server which disconnects one roadworrior when another connects

2020-09-28 Thread Tobias Brunner
Hi, > up-client is called for each combination of remote ts and local ts > components, as is down-client, when a CHILD_sa is established/destroyed. > So when a CHILD_SA is rekeyed, both are called in the order the CHILD_SAs are > negotiated/destroyed. The updown script is *not* called for IKE o

Re: [strongSwan] updown - server which disconnects one roadworrior when another connects

2020-09-28 Thread lejeczek
On 28/09/2020 10:05, Noel Kuntze wrote: > Hi, > > up-client is called for each combination of remote ts and local ts > components, as is down-client, when a CHILD_sa is established/destroyed. > So when a CHILD_SA is rekeyed, both are called in the order the CHILD_SAs are > negotiated/destroyed.