LCP problem mit pppd

Post Reply
Message
Author
Micka

LCP problem mit pppd

#1 Post by Micka »

Hallo

Ich versuch mir eine L2TP over IPSec VPN Server aufzubauen.(Kernel2.6.8.1)
IPsec klppt auch schon und mein L2TP dienst scheint auch zu laufen.(Neueste Versionen)
nun hab ich beim Aufbau der Verbindung von einem Win XP rechner folgende Fehler.
Der Windows Client bricht nach einer weile beim Verbindungsaufbau ab (bei der meldung Benutzername und Passwort werden überprüft).
Mein Linux VPN Server gibt folgende letzte Meldung aus.

l2tpd[574]: firmware_rev_avp: peer reports firmware version 1280 (0x0500)
l2tpd[574]: hostname_avp: peer reports hostname 'testcomp'
l2tpd[574]: vendor_avp: peer reports vendor 'Microsoft\200^H'
l2tpd[574]: assigned_tunnel_avp: using peer's tunnel 1
l2tpd[574]: receive_window_size_avp: peer wants RWS of 8. Will use flow control.
check_control: control, cid = 0, Ns = 1, Nr = 1
l2tpd[574]: handle_avps: handling avp's for tunnel 20880, call 0
l2tpd[574]: message_type_avp: message type 3 (Start-Control-Connection-Connected)
l2tpd[574]: control_finish: Connection established to 192.168.2.9, 1701. Local: 20880, Remote: 1. LNS session is 'default'
check_control: control, cid = 0, Ns = 2, Nr = 1
l2tpd[574]: handle_avps: handling avp's for tunnel 20880, call 0
l2tpd[574]: message_type_avp: message type 10 (Incoming-Call-Request)
l2tpd[574]: message_type_avp: new incoming call
l2tpd[574]: ourcid = 28579, entropy_buf = 6fa3
l2tpd[574]: assigned_call_avp: using peer's call 1
l2tpd[574]: call_serno_avp: serial number is 0
l2tpd[574]: bearer_type_avp: peer bears: analog
l2tpd[574]: check_control: control, cid = 0, Ns = 3, Nr = 1
l2tpd[574]: check_control: control, cid = 1, Ns = 3, Nr = 2
l2tpd[574]: handle_avps: handling avp's for tunnel 20880, call 28579
l2tpd[574]: message_type_avp: message type 12 (Incoming-Call-Connected)
l2tpd[574]: tx_speed_avp: transmit baud rate is 100000000
l2tpd[574]: frame_type_avp: peer uses:sync frames
l2tpd[574]: ignore_avp : Ignoring AVP
l2tpd[574]: start_pppd: I'm running:
l2tpd[574]: "/usr/sbin/pppd"
l2tpd[574]: "passive"
l2tpd[574]: "-detach"
l2tpd[574]: "192.168.3.99:192.168.3.128"
l2tpd[574]: "refuse-pap"
l2tpd[574]: "auth"
l2tpd[574]: "require-chap"
l2tpd[574]: "name"
l2tpd[574]: "LinuxVPNserver"
l2tpd[574]: "debug"
l2tpd[574]: "file"
l2tpd[574]: "/etc/ppp/options.l2tpd"
l2tpd[574]: "/dev/ttya1"
l2tpd[574]:
l2tpd[574]: control_finish: Call established with 192.168.2.9, Local: 28579, Remote: 1, Serial: 0
l2tpd[574]: check_control: control, cid = 0, Ns = 4, Nr = 2
pppd[584]: pppd 2.4.2 started by root, uid 0
pppd[584]: using channel 1
pppd[584]: Using interface ppp0
pppd[584]: Connect: ppp0 <--> /dev/ttya1
pppd[584]: sent [LCP ConfReq id=0x1 <mru 1400> <asyncmap 0x0> <magic 0x46397620> <pcomp> <accomp>]
last message repeated 9 times
pppd[584]: LCP: timeout sending Config-Requests
l2tpd[574]: check_control: control, cid = 1, Ns = 4, Nr = 2
l2tpd[574]: handle_avps: handling avp's for tunnel 20880, call 28579
l2tpd[574]: message_type_avp: message type 14 (Call-Disconnect-Notify)
l2tpd[574]: result_code_avp: peer closing for reason 3 (Control channel already exists), error = 0 ()
l2tpd[574]: assigned_call_avp: using peer's call 1
l2tpd[574]: control_finish: Connection closed to 192.168.2.9, serial 0 ()
pppd[584]: Terminating on signal 15.


Kann mir jemmand sagen woran der Fehler beim LCP Handshake liegen kann?

Gruß Micha

CheersMichael

#2 Post by CheersMichael »

Also ich lese hier den Fehler

LCP: timeout sending Config-Requests

der dadurch verursacht wird, das via ttya1 keine LCP-Anworten eintreffen,
was dafür spricht, das auf der Gegenseite eine ppp gesprochen wird.

Cheers

Michael

Post Reply