I totally agree. Adding leftnexthop is only a workaround which worked in
my case (I'm the original reporter but I've changed my e-mail address).
The bug seems to show itself when left=%defaultroute and right=%any
which confuses Libreswan. Openswan worked in this case. I would love a
full fix. 

Regards, 

Nick 

On 2014-05-07 09:09, Wolfgang Nothdurft wrote: 

> Am 06.05.2014 23:09, schrieb Nick Howitt:
> 
>> Not by any chance bug #86 <https://bugs.libreswan.org/show_bug.cgi?id=86 
>> [1]>? Try also setting leftnexthop=%defaultroute.
> 
> I think the problem is using the whole routing table for parsing, when the 
> destination address is not known. (see comment in the ticket)
> 
> I have attached a patch to the ticket which I'm testing at the moment.
> 
> _______________________________________________
> Swan mailing list
> [email protected]
> https://lists.libreswan.org/mailman/listinfo/swan [2]
 

Links:
------
[1] https://bugs.libreswan.org/show_bug.cgi?id=86
[2] https://lists.libreswan.org/mailman/listinfo/swan
_______________________________________________
Swan mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan

Reply via email to