[Openswan Users] L2TP problem... I think

[Andrew Tolboe]

Paul,

Yeah, I'm not sure if the server is hanging up on the client or the 
other way around, but I'm sure something is timeout.  However, that does 
not explain why everything works fine when I'm on the same subnet as the 
server.
Something else that I noticed that didn't seam right is that I could 
ping client ip until it connected, then I would get destination host 
unreachable (from the firewall).  However, when I connect from the ip on 
the same subnet I can ping that IP the whole time (before and after 
connecting).  I look at look at the routes and it seamed pppd was adding 
an odd route when the connection came up.

lre-east-2-238. *               255.255.255.255 UH    0      0        0 br0    <-- Is this right?  The lre-east bit is the client rdns
192.168.0.248   *               255.255.255.255 UH    0      0        0 ppp0   <-- This looks ok

br0 is the port that is connected to the internet.
Both of those come and go when the connection goes up or down.

I will look into setting up xl2tpd

Thanks
-Andrew T.



Paul Wouters wrote:
> On Thu, 28 Feb 2008, Andrew Tolboe wrote:
>
>   
>> Here are the logs from the server for l2tpd
>>     
>
> xl2tpd fixes many issues from l2tpd. I suggest you try that first to
> see if that fixes your problem.
>
>   
>> Feb 27 22:22:00 firewall pppd[22773]: rcvd [LCP TermReq id=0x8
>>     
>
> Is TermReq a request to terminate the connection? If so, then your windows
> machine is hanging up on your server.
>
>   
>> Feb 27 22:22:14 firewall pluto[22666]: "l2tp-X.509"[2] 155.98.80.197 #1:
>> received and ignored informational message
>> Feb 27 22:22:14 firewall pluto[22666]: "l2tp-X.509"[2] 155.98.80.197 #1:
>> received Delete SA payload: deleting ISAKMP State #1
>>     
>
> I think your windows machine is terminating the connection here. An idle
> timeout?
>
> Paul
>