[Openswan Users] L2TP/IPSEC Widnows Mobile 5.0

[Giovani Moda - MR Informática]

> You are running KLIPS, right? Then you can also do a tcpdump on ipsec0.

Yeap, and something really strange happens:

On the iPAQ:

18:22:19.055994 IP a.b.c.d.l2tp > w.x.y.z.l2tp:  l2tp:[L](52702/32917) 
{IPCP, Conf-Request (0x01), id 0, IP-Addr 0.0.0.0, Pri-DNS 0.0.0.0, Pri-NBNS 
0.0.0.0, Sec-DNS 0.0.0.0, Sec-NBNS 0.0.0.0, length 34}
18:22:19.058752 IP w.x.y.z.l2tp > a.b.c.d.l2tp:  l2tp:[L](24/1) {IPCP, 
Conf-Nack (0x03), id 0, IP-Addr 192.168.0.201, Pri-DNS inetserver, Pri-NBNS 
192.168.0.254, Sec-DNS inetserver, Sec-NBNS 192.168.0.254, length 34}
Segmentation fault

While on an Windows XP Box it goes like:

18:20:14.690646 IP a.b.c.d.l2tp > w.x.y.z.l2tp:  l2tp:[L](56080/29358) 
{IPCP, Conf-Request (0x01), id 6, IP-Addr 0.0.0.0, Pri-DNS 0.0.0.0, Pri-NBNS 
0.0.0.0, Sec-DNS 0.0.0.0, Sec-NBNS 0.0.0.0, length 34}
18:20:14.693710 IP w.x.y.z.l2tp > a.b.c.d.l2tp:  l2tp:[L](2/1) {IPCP, 
Conf-Nack (0x03), id 6, IP-Addr 192.168.0.201, Pri-DNS inetserver, Pri-NBNS 
192.168.0.254, Sec-DNS inetserver, Sec-NBNS 192.168.0.254, length 34}
18:20:14.700481 IP a.b.c.d.l2tp > w.x.y.z.l2tp:  l2tp:[L](56080/29358) 
{IPCP, Conf-Reject (0x04), id 1, IP-Comp VJ-Comp, length 10}
18:20:14.702021 IP w.x.y.z.l2tp > a.b.c.d.l2tp:  l2tp:[L](2/1) {IPCP, 
Conf-Request (0x01), id 2, IP-Addr 192.168.0.200, length 10}
18:20:14.750782 IP a.b.c.d.l2tp > w.x.y.z.l2tp:  l2tp:[L](56080/29358) 
{IPCP, Conf-Request (0x01), id 7, IP-Addr 192.168.0.201, Pri-DNS inetserver, 
Pri-NBNS 192.168.0.254, Sec-DNS inetserver, Sec-NBNS 192.168.0.254, length 
34}
18:20:14.752086 IP w.x.y.z.l2tp > a.b.c.d.l2tp:  l2tp:[L](2/1) {IPCP, 
Conf-Ack (0x02), id 7, IP-Addr 192.168.0.201, Pri-DNS inetserver, Pri-NBNS 
192.168.0.254, Sec-DNS inetserver, Sec-NBNS 192.168.0.254, length 34}
18:20:14.832819 IP a.b.c.d.l2tp > w.x.y.z.l2tp:  l2tp:[L](56080/29358) 
{IPCP, Conf-Ack (0x02), id 2, IP-Addr 192.168.0.200, length 10}
18:20:14.935592 IP a.b.c.d.l2tp > w.x.y.z.l2tp:  l2tp:[L](56080/29358) {IP 
192.168.0.201 > IGMP.MCAST.NET: igmp v3 report, 1 group record(s)}

And I really cant' debug this myself. Any clues?

> Size.

Could be a cert size problem then. How do I make it smaller?

> I.e. without RADIUS. If you use rp-l2tp with a static IP address
> for the client and a fix password then RADIUS is not required.
> This should help determine whether it is a RADIUS problem.

Yeap, done. Same problem. It's not radiusclient or freeradius.

By the way, tried changing from rp-l2tpd tp l2tpd. No changes.

Giovani