[Openswan Users] IPSec up, L2TP down
paul at xelerance.com
Mon Mar 7 19:29:38 EST 2011
On Sat, 5 Mar 2011, Cim Ryan wrote:
> Hi folks! I'm having trouble understanding the debug output from xl2tpd. Will one of you fluent in this mysterious
> tongue please help me understand what it's trying so hard to tell me?
First, make sure you are using 2.6.33. It fixes a related bug.
> -------- The log wraps up with the following block:
> network_thread: recv packet from 126.96.36.199, size = 36, tunnel = 0, call = 0 ref=0 refhim=0
> get_call: allocating new tunnel for host 188.8.131.52, port 38626.
> check_control: Received out of order control packet on tunnel -1 (got 1, expected 0)
> handle_packet: bad control packet!
> network_thread: bad packet
> build_fdset: closing down tunnel 30254
> network_thread: select timeout
That's odd. I have not seen that before. Have you tried with another device to see if
it is android specific?
> ======= Here's what the conversation looks like, according to tcpdump; what should I be looking for, here?
There is nothing to see in tcpdump really, it is all encrypted.
> Version: 1:2.6.26+dfsg-1
Yeah, I'd upgrade that.
> Package: xl2tpd
> State: installed
> Automatically installed: no
> Version: 1.2.6+dfsg-1
Try 1.2.8 as well.
If you have not done so, configure xl2tpd to specifically listen on the external IP address,
using listen-addr. I heard binding to * has caused problems for some people in the past.
More information about the Users