[Openswan Users] nat-t causes 'ERROR: asynchronous network error'

[Stefan Denker]

On Fri, Nov 10, 2006 at 04:35:08PM +0100, No body is Perfect wrote:
> This was XP behind nat-t connecting to an office network with openswan, 
> xl2tpd-1.1.05 and openswan 2.4.6 and newer.
> Openswan 2.4.4 with l2tpd-0.69-13 no problem. any ideas ?
> ERROR: asynchronous network error report on eth1 (sport=4500) for message to 
> 89.12.146.134 port 4500, complainant 217.110.17.180: No route to host [errno 
> 113, origin ICMP type 3 code 1 (not authenticated)]

Could be this is the same problem I had just this week. There is a bug
report on this: http://bugs.xelerance.com/view.php?id=693

Does your connection description include a "leftnexthop"? If not, try to
add "leftnexthop=your.gate.way" as a workaround and try again..

Stefan

-- 
"Don't try to put me at ease, Miss von Humpeding," he(Samuel Vimes) said.
"It makes me nervous when people do that. It's not though I have any ease
 to be put at."
                                                        [Terry Pratchett - Thud]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.openswan.org/pipermail/users/attachments/20061110/8c2f05c1/attachment.bin