Re: [strongSwan] Tunnel established, but 'no acceptable ENCRYPTION_ALGORITHM found'

2018-05-02 Thread Jafar Al-Gharaibeh
Very Helpful, Thanks, Jafar On 5/2/2018 3:22 AM, Tobias Brunner wrote: Hi Jafar,     Makes sense, but just to understand what is going on and know how to read the logs, are you saying that each "ESP:" prefix signifies a separate proposal that is parsed independently (log below)? A single

Re: [strongSwan] Tunnel established, but 'no acceptable ENCRYPTION_ALGORITHM found'

2018-05-02 Thread Tobias Brunner
Hi Jafar, >     Makes sense, but just to understand what is going on and know how > to read the logs, are you saying that each "ESP:" prefix signifies a > separate proposal that is parsed independently (log below)? A single > proposal might have one or more algorithms separated by slashes,

Re: [strongSwan] Tunnel established, but 'no acceptable ENCRYPTION_ALGORITHM found'

2018-05-01 Thread Jafar Al-Gharaibeh
Tobias,     Makes sense, but just to understand what is going on and know how to read the logs, are you saying that each "ESP:" prefix signifies a separate proposal that is parsed independently (log below)? A single proposal might have one or more algorithms separated by slashes, correct ?

Re: [strongSwan] Tunnel established, but 'no acceptable ENCRYPTION_ALGORITHM found'

2018-05-01 Thread Tobias Brunner
Hi, > I see an error in the strongswan > logs and I'm not sure what is going on here, and what I should do to > correct this: There is nothing to correct as the connection gets successfully established. If you have a closer look at the log you see that the client sends not one, but four ESP

Re: [strongSwan] Tunnel established, but 'no acceptable ENCRYPTION_ALGORITHM found'

2018-04-30 Thread Jafar Al-Gharaibeh
It is weird! As you pointed out, right after the ''no acceptable... " line, you have "proposal matches", and obviously that works.  What is  your config config on the phone? Sun Apr 29 15:47:19 2018 daemon.info : 06[CFG] selecting proposal: Sun Apr 29 15:47:19 2018 daemon.info : 06[CFG]   no