Domäne selektiv über StronVPN erreichen

supr3m3 · Beitrag von **supr3m3** » 12 Mär 2012, 11:11

OT:

Firefox 10.0.2, wenn mans jetzt weiss erledigen sich so einige fragen =)

aag · Beitrag von **aag** » 23 Mär 2012, 05:50

MPPE wird von StrongVPN unterstützt, sowie ich verstehe. Siehe http://strongvpn.com/forum/viewtopic.php?pid=268#p268
Ich habe mal 128bit für die Encryption eingestellt. Trotzdem, no joy!

backslash · Beitrag von **backslash** » 23 Mär 2012, 11:58

Hi aag,

mach doch mal einen PPP-Trace vom Verbinsungsaufbau (entweder per Telnet auf das Gerät und trace # ppp eingeben oder den LANmonitor...)

Gruß
Backslash

aag · Beitrag von **aag** » 23 Mär 2012, 19:12

gemacht. die antwort von telnet ist PPP ON. Ich nehme an, der trace ended in irgendeien log?

backslash · Beitrag von **backslash** » 23 Mär 2012, 19:49

Hi aag,

die antwort von telnet ist PPP ON

das ist schonmal OK...

Ich nehme an, der trace ended in irgendeien log?

nein... sobald eine PPP-Verbindung aufgabaut wird, rauscht der Trace über's Telnet...

Du mußt nun also noch die Verbindung aufbauen...

Gruß
Backslash

aag · Beitrag von **aag** » 24 Mär 2012, 12:39

Aha. Der trace gibt nichts her. Ich denke, die routing-Tabelle ist falsch. Ich hatte die Netflix-IP angeschaut, aber wenn ich sniffe was mein Browser angibt, kommen allerlei andere IPs raus.

Ich probiere mal, alle gesniffte IPs in die routing table einzutragen. Bei den Routing-Table-Einträgen gibt es aber au ch noch netmask und routing tag. Welche Werte muss ich dort eingeben?

backslash · Beitrag von **backslash** » 26 Mär 2012, 11:29

Hi aag

Bei den Routing-Table-Einträgen gibt es aber au ch noch netmask und routing tag. Welche Werte muss ich dort eingeben?

255.255.255.255 und 0...

ganz nebenbei: ein nslookup liefert folgendes:

C:\>nslookup www.netflix.com
Server: xxxxx
Address: 10.1.1.11

Nicht autorisierte Antwort:
Name: wwwservice--frontend-373494752.eu-west-1.elb.amazonaws.com
Addresses: 176.34.185.50, 176.34.185.102, 176.34.186.229, 176.34.187.142
176.34.188.229, 176.34.184.243
Aliases: www.netflix.com

d.h. du mußt für alle dort gelistetem Adressen einen Routing-Eintrag erstellen...

Gruß
Backslash

aag · Beitrag von **aag** » 26 Mär 2012, 19:52

kann man eigentlich in der Routing Table ein Range eingeben, z.B. alles was mit 176.34.184.* anfängt? Asterisks werden vom Lanconfig verworfen...

aag · Beitrag von **aag** » 26 Mär 2012, 20:10

OK, ich habe es zumindest soweit gebracht, dass der trace funktioniert. Richtig schlau werde ich aber davon nicht. Hier eine Kostprobe...

Code: Alles auswählen


                                                                         
[TraceStarted] 2012/03/26 20:05:19,617
Used config:
# Trace config
trace + PPP

# Show commands
show bootlog 
[ShowCmd] 2012/03/26 20:05:21,325
Result of command: "show bootlog "
Boot log (3197 Bytes):

****

03/24/2012 11:07:05  System boot after manual coldboot request

DEVICE:           LANCOM 1781EF
HW-RELEASE:       B
VERSION:          8.60.0134RC2 / 13.01.2012

****

03/26/2012 03:46:15  LCOS-Watchdog
Task name = SG  Type=e300: DSI Interrupt (Protection error on store access @0x0000003c)
Code=0x00000300 Task=01358b20/0127c648 Nest=0x00000000

 R00=0x0089a080  SP =0x0135c3ac  R02=0x00dc3000  R03=0x00000000 
 R04=0x00000001  R05=0x009cbc4c  R06=0x000090b2  R07=0x009cbbdc 
 R08=0x0000001b  R09=0x00ca4c78  R10=0x00000005  R11=0x00000014 
 R12=0x00896818  R13=0x01193630  R14=0x00000000  R15=0x00000000 
 R16=0x00000000  R17=0x00000000  R18=0x00000000  R19=0x00000000 
 R20=0x00000000  R21=0x0135ca64  R22=0x0135c640  R23=0x0135c450 
 R24=0x00000000  R25=0x07ffdc10  R26=0x07fe7b40  R27=0x07ff83c0 
 R28=0x01358b20  R29=0x07fda360  R30=0x07fffbb8  R31=0x01190000 

 CR  =0x02004024  XER =0x20000000  LR  =0x0089a080  CTR =0x00896818 
 DAR =0x0000003c  DSR =0x0a000000  TBL =0x0c655c2e  TBU =0x00000454 
 IBCR=0x00e20000  DBCR=0x00e20000  DBR =0x07ffffef  DBR2=0x07ffffc7 
 HID0=0xc090c000  HID1=0x0c000000  HID2=0x04e40000  MBAR=0x00000000 
 SPR0=0x00000014  SPR1=0x00000000  SPR2=0x00000001  SPR3=0x000010b2 
 SPR4=0x00000000  SPR5=0x00000000  SPR6=0x00000000  SPR7=0x00000005 
 TGR0=0x00001080  TGR1=0x0000003c  TGR2=0x00000000  TGR3=0x000b90b2 

 SRR0(PC) =0x0089a088
 SRR1(MSR)=0x000090b2



DEVICE:           LANCOM 1781EF
HW-RELEASE:       B
VERSION:          8.60.0134RC2 / 13.01.2012

****

03/26/2012 03:46:25  System boot after LCOS-Watchdog

DEVICE:           LANCOM 1781EF
HW-RELEASE:       B
VERSION:          8.60.0134RC2 / 13.01.2012

[PPP] 2012/03/26 20:05:21,294  Devicetime: 2012/03/26 20:05:18,186
Positive Restart-Timeout event for LCP
Stop waiting for connection
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer STRONGVPN-PPTP
Inserting local MRU 1460
Inserting local authentication protocol CHAP with DES encryption (MS-CHAPv2)
Inserting local magic number 4c518e6c
Sending LCP configure-request with ID 00 and length 19 to peer STRONGVPN-PPTP (channel 0)
Starting LCP restart timer with 3000 milliseconds

[PPP] 2012/03/26 20:05:21,496  Devicetime: 2012/03/26 20:05:18,303

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-ack with ID 00 and size 19
Configure-Ack-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds

[PPP] 2012/03/26 20:05:21,496  Devicetime: 2012/03/26 20:05:18,303

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-request with ID 00 and size 26
Peer MRU 1400 accepted
Peer requests authentication protocol CHAP with DES encryption (MS-CHAPv2), accepted
Peer magic number 4c3261c9 accepted
Peer requests protocol field compression, rejected
Peer requests address- and controlfield compression, rejected
Peer requests callback via callback control protocol, rejected
Negative Configure-Request-Received event for LCP
Sending LCP configure-reject with ID 00 and length 11 to peer STRONGVPN-PPTP (channel 0)

[Sysinfo] 2012/03/26 20:05:21,538
Result of command: "sysinfo"

DEVICE:           LANCOM 1781EF
HW-RELEASE:       B
SERIAL-NUMBER:    4002089118100075
MAC-ADDRESS:      00a0571915f3
IP-ADDRESS:       100.100.100.1
IP-NETMASK:       255.255.255.0
INTRANET-ADDRESS: 0.0.0.0
INTRANETMASK:     0.0.0.0
LANCAPI-PORT:     75
VERSION:          8.60.0134RC2 / 13.01.2012
NAME:             RouterAnkleide
CONFIG-STATUS:    1056;0;81024cb6a35b5f4c48d22ddb135b3ee66fc05a16.17581726032012.126
FIRMWARE-STATUS:  1;1.4;1.2;8.50.0214RU4.13122011.3;8.60.0134RC2.13012012.4
HW-MASK:          00000000000000000000000000000011
FEATUREWORD:      00000000001000000000000100011100
REGISTERED-WORD:  00000000001000000000000100011100
FEATURE-LIST:     02/F
FEATURE-LIST:     03/F
FEATURE-LIST:     04/F
FEATURE-LIST:     08/F
FEATURE-LIST:     15/F
TIME:             20051826032012
HTTP-PORT:        80
HTTPS-PORT:       443
TELNET-PORT:      23
TELNET-SSL-PORT:  992
SSH-PORT:         22
Production-Date:  2011-10-13
MOD-Level:        B0
LOCATION:         Ankleide
COMMENT:          

[PPP] 2012/03/26 20:05:21,496  Devicetime: 2012/03/26 20:05:18,417

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-request with ID 01 and size 19
Peer MRU 1400 accepted
Peer requests authentication protocol CHAP with DES encryption (MS-CHAPv2), accepted
Peer magic number 4c3261c9 accepted
Positive Configure-Request-Received event for LCP
Sending LCP configure-ack with ID 01 and length 19 to peer STRONGVPN-PPTP (channel 0)
Stopping LCP restart timer
This-Layer-Up action for LCP
Change phase to AUTHENTICATE for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:21,651  Devicetime: 2012/03/26 20:05:18,527
PPTP call control: received SetLinkInfo from 173.195.0.48 for call id 6674 with SendACCM=0xffffffff, ReceiveACCM=0xffffffff

[PPP] 2012/03/26 20:05:21,651  Devicetime: 2012/03/26 20:05:18,530

Received CHAP frame from peer STRONGVPN-PPTP (channel 0)
Got CHAP-Challenge from peer STRONGVPN-PPTP
Challenge = f2 53 84 9f 9c d1 e4 36 5b 2b 42 7c 54 6a 47 c7
Unknown peer-id STRONGVPN-PPTP
Administrative-Close event for LCP
This-Layer-Down action for LCP
Lower-Layer-Down event for IPV6CP
Lower-Layer-Down event for BACP
Lower-Layer-Down event for CCP
Lower-Layer-Down event for IPCP
Lower-Layer-Down event for IPXCP
Initializing LCP restart timer to 3000 milliseconds
Change phase to TERMINATE for STRONGVPN-PPTP
Sending LCP terminate-request with ID 03 and length 4 to peer STRONGVPN-PPTP (channel 0)
Starting LCP restart timer with 3000 milliseconds

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,644

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Terminate-Ack-Received event for LCP
Stopping LCP restart timer
This-Layer-Finish action for LCP
Disconnecting because LCP was finished

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,645
Change phase to DEAD for STRONGVPN-PPTP
Stopping LCP restart timer
Stopping IPCP restart timer
Stopping CCP restart timer
Stopping BACP restart timer
Stopping IPV6CP restart timer

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,646
selecting next remote gateway using strategy eFirst for STRONGVPN-PPTP
     => no remote gateway selected

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,646
selecting first remote gateway using strategy eFirst for STRONGVPN-PPTP
     => CurrIdx=0, IpStr=>vpn-in48.reliablehosting.com<, IpAddr=173.195.0.48, IpTtl=3600s

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,646
PPTP call control: closing call for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,648
PPTP: Error: Unkn.-CHAP-Peer (0x8025) for STRONGVPN-PPTP (173.195.0.48)

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,654
PPTP call control: call destroyed for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,654
PPTP control channel: closing TCP connection to 173.195.0.48

[PPP] 2012/03/26 20:05:21,652  Devicetime: 2012/03/26 20:05:18,654
PPTP control channel: TCP connection to 173.195.0.48 closed

[PPP] 2012/03/26 20:05:22,879  Devicetime: 2012/03/26 20:05:19,646
PPTP control channel: connecting to STRONGVPN-PPTP (173.195.0.48)
PPTP control channel: waiting for TCP connect for STRONGVPN-PPTP (173.195.0.48)
PPTP control channel: use local port: 10496 for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:22,879  Devicetime: 2012/03/26 20:05:19,757
PPTP control channel: TCP connection to 173.195.0.48 established
PPTP control channel: StartControlConnectionRequest sent to 173.195.0.48

[PPP] 2012/03/26 20:05:22,879  Devicetime: 2012/03/26 20:05:19,863
PPTP control channel: received StartControlConnectionReply from 173.195.0.48
PPTP call control: OutgoingCallRequest sent for call id 1154 to 173.195.0.48

[PPP] 2012/03/26 20:05:23,084  Devicetime: 2012/03/26 20:05:19,970
Change phase to ESTABLISH for STRONGVPN-PPTP
Lower-Layer-Up event for LCP
Initializing LCP restart timer to 3000 milliseconds
Waiting up to 200ms for connection
Starting LCP restart timer with 200 milliseconds

[PPP] 2012/03/26 20:05:23,084  Devicetime: 2012/03/26 20:05:19,970
PPTP call control: received OutgoingCallReply from 173.195.0.48 for call id 1154: peer call id 12341
PPTP call control: SetLinkInfo sent for call id 1154 to 173.195.0.48 with SendACCM=0x00000000 and ReceiveACCM=0x00000000
PPTP call control: set remote window to 8192 for STRONGVPN-PPTP
PPTP call control: connect request for PPP sent

[PPP] 2012/03/26 20:05:23,289  Devicetime: 2012/03/26 20:05:20,170
Positive Restart-Timeout event for LCP
Stop waiting for connection
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer STRONGVPN-PPTP
Inserting local MRU 1460
Inserting local authentication protocol CHAP with DES encryption (MS-CHAPv2)
Inserting local magic number e432b2ed
Sending LCP configure-request with ID 00 and length 19 to peer STRONGVPN-PPTP (channel 0)
Starting LCP restart timer with 3000 milliseconds

[PPP] 2012/03/26 20:05:23,494  Devicetime: 2012/03/26 20:05:20,288

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-request with ID 00 and size 26
Peer MRU 1400 accepted
Peer requests authentication protocol CHAP with DES encryption (MS-CHAPv2), accepted
Peer magic number 65ab67c1 accepted
Peer requests protocol field compression, rejected
Peer requests address- and controlfield compression, rejected
Peer requests callback via callback control protocol, rejected
Negative Configure-Request-Received event for LCP
Sending LCP configure-reject with ID 00 and length 11 to peer STRONGVPN-PPTP (channel 0)

[PPP] 2012/03/26 20:05:23,494  Devicetime: 2012/03/26 20:05:20,288

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-ack with ID 00 and size 19
Configure-Ack-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds

[PPP] 2012/03/26 20:05:23,494  Devicetime: 2012/03/26 20:05:20,402

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-request with ID 01 and size 19
Peer MRU 1400 accepted
Peer requests authentication protocol CHAP with DES encryption (MS-CHAPv2), accepted
Peer magic number 65ab67c1 accepted
Positive Configure-Request-Received event for LCP
Sending LCP configure-ack with ID 01 and length 19 to peer STRONGVPN-PPTP (channel 0)
Stopping LCP restart timer
This-Layer-Up action for LCP
Change phase to AUTHENTICATE for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:23,699  Devicetime: 2012/03/26 20:05:20,511

Received CHAP frame from peer STRONGVPN-PPTP (channel 0)
Got CHAP-Challenge from peer STRONGVPN-PPTP
Challenge = 67 b5 74 e7 f0 bc c4 ec 98 c3 ff 07 e5 d9 ec 29
Unknown peer-id STRONGVPN-PPTP
Administrative-Close event for LCP
This-Layer-Down action for LCP
Lower-Layer-Down event for IPV6CP
Lower-Layer-Down event for BACP
Lower-Layer-Down event for CCP
Lower-Layer-Down event for IPCP
Lower-Layer-Down event for IPXCP
Initializing LCP restart timer to 3000 milliseconds
Change phase to TERMINATE for STRONGVPN-PPTP
Sending LCP terminate-request with ID 03 and length 4 to peer STRONGVPN-PPTP (channel 0)
Starting LCP restart timer with 3000 milliseconds

[PPP] 2012/03/26 20:05:23,699  Devicetime: 2012/03/26 20:05:20,511
PPTP call control: received SetLinkInfo from 173.195.0.48 for call id 1154 with SendACCM=0xffffffff, ReceiveACCM=0xffffffff

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,622

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Terminate-Ack-Received event for LCP
Stopping LCP restart timer
This-Layer-Finish action for LCP
Disconnecting because LCP was finished

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,623
Change phase to DEAD for STRONGVPN-PPTP
Stopping LCP restart timer
Stopping IPCP restart timer
Stopping CCP restart timer
Stopping BACP restart timer
Stopping IPV6CP restart timer

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,624
selecting next remote gateway using strategy eFirst for STRONGVPN-PPTP
     => no remote gateway selected

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,624
selecting first remote gateway using strategy eFirst for STRONGVPN-PPTP
     => CurrIdx=0, IpStr=>vpn-in48.reliablehosting.com<, IpAddr=173.195.0.48, IpTtl=3600s

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,623
PPTP call control: closing call for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,625
PPTP: Error: Unkn.-CHAP-Peer (0x8025) for STRONGVPN-PPTP (173.195.0.48)

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,631
PPTP call control: call destroyed for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:23,700  Devicetime: 2012/03/26 20:05:20,632
PPTP control channel: closing TCP connection to 173.195.0.48

[PPP] 2012/03/26 20:05:23,701  Devicetime: 2012/03/26 20:05:20,632
PPTP control channel: TCP connection to 173.195.0.48 closed

[PPP] 2012/03/26 20:05:24,825  Devicetime: 2012/03/26 20:05:21,624
PPTP control channel: connecting to STRONGVPN-PPTP (173.195.0.48)
PPTP control channel: waiting for TCP connect for STRONGVPN-PPTP (173.195.0.48)
PPTP control channel: use local port: 8768 for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:24,825  Devicetime: 2012/03/26 20:05:21,738
PPTP control channel: TCP connection to 173.195.0.48 established
PPTP control channel: StartControlConnectionRequest sent to 173.195.0.48

[PPP] 2012/03/26 20:05:24,825  Devicetime: 2012/03/26 20:05:21,845
PPTP control channel: received StartControlConnectionReply from 173.195.0.48
PPTP call control: OutgoingCallRequest sent for call id 4385 to 173.195.0.48

[PPP] 2012/03/26 20:05:25,030  Devicetime: 2012/03/26 20:05:21,955
Change phase to ESTABLISH for STRONGVPN-PPTP
Lower-Layer-Up event for LCP
Initializing LCP restart timer to 3000 milliseconds
Waiting up to 200ms for connection
Starting LCP restart timer with 200 milliseconds

[PPP] 2012/03/26 20:05:25,030  Devicetime: 2012/03/26 20:05:21,954
PPTP call control: received OutgoingCallReply from 173.195.0.48 for call id 4385: peer call id 4221
PPTP call control: SetLinkInfo sent for call id 4385 to 173.195.0.48 with SendACCM=0x00000000 and ReceiveACCM=0x00000000
PPTP call control: set remote window to 8192 for STRONGVPN-PPTP
PPTP call control: connect request for PPP sent

[PPP] 2012/03/26 20:05:25,235  Devicetime: 2012/03/26 20:05:22,150
Positive Restart-Timeout event for LCP
Stop waiting for connection
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer STRONGVPN-PPTP
Inserting local MRU 1460
Inserting local authentication protocol CHAP with DES encryption (MS-CHAPv2)
Inserting local magic number ca50f5b5
Sending LCP configure-request with ID 00 and length 19 to peer STRONGVPN-PPTP (channel 0)
Starting LCP restart timer with 3000 milliseconds

[PPP] 2012/03/26 20:05:25,440  Devicetime: 2012/03/26 20:05:22,259

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-request with ID 00 and size 26
Peer MRU 1400 accepted
Peer requests authentication protocol CHAP with DES encryption (MS-CHAPv2), accepted
Peer magic number 7ebc2e2b accepted
Peer requests protocol field compression, rejected
Peer requests address- and controlfield compression, rejected
Peer requests callback via callback control protocol, rejected
Negative Configure-Request-Received event for LCP
Sending LCP configure-reject with ID 00 and length 11 to peer STRONGVPN-PPTP (channel 0)

[PPP] 2012/03/26 20:05:25,440  Devicetime: 2012/03/26 20:05:22,260

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-ack with ID 00 and size 19
Configure-Ack-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds

[PPP] 2012/03/26 20:05:25,441  Devicetime: 2012/03/26 20:05:22,371

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Evaluate configure-request with ID 01 and size 19
Peer MRU 1400 accepted
Peer requests authentication protocol CHAP with DES encryption (MS-CHAPv2), accepted
Peer magic number 7ebc2e2b accepted
Positive Configure-Request-Received event for LCP
Sending LCP configure-ack with ID 01 and length 19 to peer STRONGVPN-PPTP (channel 0)
Stopping LCP restart timer
This-Layer-Up action for LCP
Change phase to AUTHENTICATE for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:25,644  Devicetime: 2012/03/26 20:05:22,480

Received CHAP frame from peer STRONGVPN-PPTP (channel 0)
Got CHAP-Challenge from peer STRONGVPN-PPTP
Challenge = b5 8b f0 e6 e2 e9 f6 bd b7 77 34 76 f3 09 c7 0d
Unknown peer-id STRONGVPN-PPTP
Administrative-Close event for LCP
This-Layer-Down action for LCP
Lower-Layer-Down event for IPV6CP
Lower-Layer-Down event for BACP
Lower-Layer-Down event for CCP
Lower-Layer-Down event for IPCP
Lower-Layer-Down event for IPXCP
Initializing LCP restart timer to 3000 milliseconds
Change phase to TERMINATE for STRONGVPN-PPTP
Sending LCP terminate-request with ID 03 and length 4 to peer STRONGVPN-PPTP (channel 0)
Starting LCP restart timer with 3000 milliseconds

[PPP] 2012/03/26 20:05:25,644  Devicetime: 2012/03/26 20:05:22,483
PPTP call control: received SetLinkInfo from 173.195.0.48 for call id 4385 with SendACCM=0xffffffff, ReceiveACCM=0xffffffff

[PPP] 2012/03/26 20:05:25,645  Devicetime: 2012/03/26 20:05:22,588

Received LCP frame from peer STRONGVPN-PPTP (channel 0)
Terminate-Ack-Received event for LCP
Stopping LCP restart timer
This-Layer-Finish action for LCP
Disconnecting because LCP was finished

[PPP] 2012/03/26 20:05:25,645  Devicetime: 2012/03/26 20:05:22,589
Change phase to DEAD for STRONGVPN-PPTP
Stopping LCP restart timer
Stopping IPCP restart timer
Stopping CCP restart timer
Stopping BACP restart timer
Stopping IPV6CP restart timer

[PPP] 2012/03/26 20:05:25,645  Devicetime: 2012/03/26 20:05:22,590
selecting next remote gateway using strategy eFirst for STRONGVPN-PPTP
     => no remote gateway selected

[PPP] 2012/03/26 20:05:25,646  Devicetime: 2012/03/26 20:05:22,590
selecting first remote gateway using strategy eFirst for STRONGVPN-PPTP
     => CurrIdx=0, IpStr=>vpn-in48.reliablehosting.com<, IpAddr=173.195.0.48, IpTtl=3600s

[PPP] 2012/03/26 20:05:25,646  Devicetime: 2012/03/26 20:05:22,590
PPTP call control: closing call for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:25,646  Devicetime: 2012/03/26 20:05:22,592
PPTP: Error: Unkn.-CHAP-Peer (0x8025) for STRONGVPN-PPTP (173.195.0.48)

[PPP] 2012/03/26 20:05:25,646  Devicetime: 2012/03/26 20:05:22,598
PPTP call control: call destroyed for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:25,646  Devicetime: 2012/03/26 20:05:22,598
PPTP control channel: closing TCP connection to 173.195.0.48

[PPP] 2012/03/26 20:05:25,646  Devicetime: 2012/03/26 20:05:22,599
PPTP control channel: TCP connection to 173.195.0.48 closed

[PPP] 2012/03/26 20:05:25,849  Devicetime: 2012/03/26 20:05:22,695
PPTP control channel: connecting to STRONGVPN-PPTP (173.195.0.48)
PPTP control channel: waiting for TCP connect for STRONGVPN-PPTP (173.195.0.48)
PPTP control channel: use local port: 10384 for STRONGVPN-PPTP

[PPP] 2012/03/26 20:05:25,850  Devicetime: 2012/03/26 20:05:22,819
PPTP control channel: TCP connection to 173.195.0.48 established
PPTP control channel: StartControlConnectionRequest sent to 173.195.0.48

[TraceStopped] 2012/03/26 20:05:25,890
Used config:
# Trace config
trace + PPP

# Show commands
show bootlog 
[Legend] 2009/07/09 00:00:00,000
PPP, TraceStarted, TraceStopped, Sysinfo, ShowCmd
[Index] 2009/07/09 00:00:00,000
1,117,7;4,7086,120;0,535,11;0,267,7;0,647,13;3,1097,35;0,572,13;0,195,3;0,743,18;0,269,8;0,256,8;0,178,4;0,234,4;0,122,3;0,143,3;0,124,3;0,132,3;0,131,3;
0,282,5;0,210,4;0,226,4;0,285,7;0,408,6;0,535,11;0,647,13;0,267,7;0,572,13;0,743,18;0,195,3;0,269,8;0,256,8;0,178,4;0,234,4;0,122,3;0,143,3;0,124,3;0,132,3;
0,131,3;0,281,5;0,210,4;0,226,4;0,285,7;0,407,6;0,535,11;0,647,13;0,267,7;0,572,13;0,743,18;0,195,3;0,269,8;0,256,8;0,178,4;0,234,4;0,122,3;0,143,3;0,124,3;
0,132,3;0,131,3;0,282,5;0,210,4;2,117,7;

backslash · Beitrag von **backslash** » 26 Mär 2012, 20:57

Hi aag

hier steht doch schon, was falsch ist:

Received CHAP frame from peer STRONGVPN-PPTP (channel 0)
Got CHAP-Challenge from peer STRONGVPN-PPTP
Challenge = f2 53 84 9f 9c d1 e4 36 5b 2b 42 7c 54 6a 47 c7
Unknown peer-id STRONGVPN-PPTP

du mußt "STRONGVPN-PPTP" nicht nur in der PPTP-Liste eintragen, sondern auch in der PPP-Liste, denn irgemndwo mußt du ja auch noch Username und Paßwort hinterlegen...

edit:

Achte darauf, daß du in der PPP-Liste bei "Authetifizierung der Gegenstelle" *nichts* anhakst und bei "Authetifizierung durch Gegenstelle" *nur* MSCHAPv2

Gruß
Backslash

aag · Beitrag von **aag** » 26 Mär 2012, 21:44

Bingo! Ich glaube, die Verbindung steht! Siehe trace unten.

Netflix funktioniert aber immer noch nicht - ich nehme an, dass ich noch nicht die richtige IP-Adresse des Netflix-Servers gefunden habe. Kann ich temporär alles Verkehr über STRONVPN umleiten? Ich nehme an, indem ich INTERNET mit STRONGVPN-PPTP in der routing table ersetze. Dann müsste auf jeden Fall die Sache funktionieren...

Code: Alles auswählen


03/26/2012 03:46:25  System boot after LCOS-Watchdog

DEVICE:           LANCOM 1781EF
HW-RELEASE:       B
VERSION:          8.60.0134RC2 / 13.01.2012

[Sysinfo] 2012/03/26 21:38:05,459
Result of command: "sysinfo"

DEVICE:           LANCOM 1781EF
HW-RELEASE:       B
SERIAL-NUMBER:    4002089118100075
MAC-ADDRESS:      00a0571915f3
IP-ADDRESS:       100.100.100.1
IP-NETMASK:       255.255.255.0
INTRANET-ADDRESS: 0.0.0.0
INTRANETMASK:     0.0.0.0
LANCAPI-PORT:     75
VERSION:          8.60.0134RC2 / 13.01.2012
NAME:             RouterAnkleide
CONFIG-STATUS:    1056;0;7bff471958b2fc0db15946ad27a7d4a8a493c29f.17581726032012.127
FIRMWARE-STATUS:  1;1.4;1.2;8.50.0214RU4.13122011.3;8.60.0134RC2.13012012.4
HW-MASK:          00000000000000000000000000000011
FEATUREWORD:      00000000001000000000000100011100
REGISTERED-WORD:  00000000001000000000000100011100
FEATURE-LIST:     02/F
FEATURE-LIST:     03/F
FEATURE-LIST:     04/F
FEATURE-LIST:     08/F
FEATURE-LIST:     15/F
TIME:             21380126032012
HTTP-PORT:        80
HTTPS-PORT:       443
TELNET-PORT:      23
TELNET-SSL-PORT:  992
SSH-PORT:         22
Production-Date:  2011-10-13
MOD-Level:        B0
LOCATION:         Ankleide
COMMENT:          

[PPP] 2012/03/26 21:38:06,395  Devicetime: 2012/03/26 21:38:02,567
PPTP control channel: received EchoRequest from 173.195.0.48 with id 0x04000000
PPTP control channel: EchoReply sent to 173.195.0.48


[PPP] 2012/03/26 21:38:17,339  Devicetime: 2012/03/26 21:38:13,530

LCP polling timeout for peer STRONGVPN-PPTP - data received during last interval


[PPP] 2012/03/26 21:38:36,982  Devicetime: 2012/03/26 21:38:32,900
suppress DNS resolution for STRONGVPN-PPTP
IpStr=>vpn-in48.reliablehosting.com<, IpAddr=173.195.0.48, IpTtl=3600s


[PPP] 2012/03/26 21:38:47,423  Devicetime: 2012/03/26 21:38:43,530

LCP polling timeout for peer STRONGVPN-PPTP - data received during last interval


[PPP] 2012/03/26 21:39:06,496  Devicetime: 2012/03/26 21:39:02,600
PPTP control channel: echo timeout for 173.195.0.48
PPTP control channel: EchoRequest sent with id 0x035170c2 to 173.195.0.48

[PPP] 2012/03/26 21:39:06,496  Devicetime: 2012/03/26 21:39:02,601
PPTP control channel: received EchoRequest from 173.195.0.48 with id 0x05000000
PPTP control channel: EchoReply sent to 173.195.0.48

[PPP] 2012/03/26 21:39:06,496  Devicetime: 2012/03/26 21:39:02,710
PPTP control channel: received EchoReply from 173.195.0.48 for id 0x035170c2 - echo retry counter reset


[PPP] 2012/03/26 21:39:17,534  Devicetime: 2012/03/26 21:39:13,530

LCP polling timeout for peer STRONGVPN-PPTP - data received during last interval


[PPP] 2012/03/26 21:39:47,335  Devicetime: 2012/03/26 21:39:43,530

LCP polling timeout for peer STRONGVPN-PPTP - data received during last interval


[PPP] 2012/03/26 21:40:06,713  Devicetime: 2012/03/26 21:40:02,710
PPTP control channel: echo timeout for 173.195.0.48
PPTP control channel: EchoRequest sent with id 0x2e57183c to 173.195.0.48

[PPP] 2012/03/26 21:40:06,713  Devicetime: 2012/03/26 21:40:02,821
PPTP control channel: received EchoReply from 173.195.0.48 for id 0x2e57183c - echo retry counter reset


[TraceStopped] 2012/03/26 21:40:15,090
Used config:
# Trace config
trace + PPP

# Show commands
show bootlog 
[Legend] 2009/07/09 00:00:00,000
PPP, TraceStarted, TraceStopped, Sysinfo, ShowCmd
[Index] 2009/07/09 00:00:00,000
1,117,7;4,7086,120;3,1097,35;0,206,5;0,155,5;0,187,5;0,155,5;0,198,4;0,205,4;0,176,4;0,155,5;0,155,5;0,198,4;0,176,4;2,117,7;

aag · Beitrag von **aag** » 26 Mär 2012, 21:50

habe getestet. wenn ich alles über STRONGVPN umleite, geht Netflix tadellos. Jetzt muss nur noch herausfinden, welche IP-Anschriften (es sind mehrere Server) umgeleitet werden müssen. Ich danke Euch für die hervorragende Hilfe! Meine Lancom-Anschaffung hat sich sehr gelohnt!!!

aag · Beitrag von **aag** » 11 Apr 2012, 19:50

Ich bin immer noch am Feilen dieser Lösung. Nun sieht meine Routing Table so aus:

Code: Alles auswählen

#    IP-Address       IP-Netmask       Rtg-tag  Peer-or-IP        Distance  Masquerade  Active   Comment                                                         
#    -----------------------------------------------------------------------------------------------------------------------------------------------------------------
add  10.0.0.0         255.255.255.255  0       {Peer-or-IP}  "0.0.0.0"        {Distance}  0        {Masquerade}  No         {Active}  Yes     {Comment}  "block private network: 10.x.y.z"
add  69.53.236.17     255.255.255.255  0       {Peer-or-IP}  "STRONGVPN-PPTP" {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  "Netflix"
add  172.16.0.0       255.255.255.255  0       {Peer-or-IP}  "0.0.0.0"        {Distance}  0        {Masquerade}  No         {Active}  Yes     {Comment}  "block private networks: 172.16-31.x.y"
add  192.168.0.0      255.255.255.255  0       {Peer-or-IP}  "0.0.0.0"        {Distance}  0        {Masquerade}  No         {Active}  Yes     {Comment}  "block private networks: 192.168.x.y"
add  224.0.0.0        224.0.0.0        0       {Peer-or-IP}  "0.0.0.0"        {Distance}  0        {Masquerade}  No         {Active}  Yes     {Comment}  "block multicasts: 224-255.x.y.z"
add  107.20.137.117   255.255.255.255  0       {Peer-or-IP}  "STRONGVPN-PPTP" {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  "Netflix"
add  107.20.232.200   255.255.255.255  0       {Peer-or-IP}  "STRONGVPN-PPTP" {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  "Netflix"
add  107.21.96.127    255.255.255.255  0       {Peer-or-IP}  "STRONGVPN-PPTP" {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  "Netflix"
add  50.19.103.125    255.255.255.255  0       {Peer-or-IP}  "STRONGVPN-PPTP" {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  "Netflix"
add  50.19.119.154    255.255.255.255  0       {Peer-or-IP}  "STRONGVPN-PPTP" {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  "Netflix"
add  50.19.99.64      255.255.255.255  0       {Peer-or-IP}  "STRONGVPN-PPTP" {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  "Netflix"
add  255.255.255.255  0.0.0.0          0       {Peer-or-IP}  "INTERNET"       {Distance}  0        {Masquerade}  on         {Active}  Yes     {Comment}  ""

Wenn ich aber ein Trace einstelle, scheint mir, dass nichts über StrongVPN geroutet wird. Kann es sein dass der letzte Eintrag alles andere overridet? Mir ist nicht klar, wie die Routing Table so konfiguriert werden soll, dass alles über INTERNET geroutet wird ausser diese speziellen Adressen...

backslash · Beitrag von **backslash** » 12 Apr 2012, 12:06

Hi aag,

die Routing-Tabelle ist korrekt... der letzte Eintrag ist die Defaultroute, die genommen wird, wenn es keine andere Route gibt...

das einzige, was mir auffällt ist, daß du offenbar die Netzmasken der Sperr-Routen geändert hast... mit korrekten Netzmasken und sortiert sieht sie so aus:

Code: Alles auswählen

IP-Address       IP-Netmask       Rtg-tag  Peer-or-IP        Distance  Masquerade  Active   Comment                                                         
------------------------------------------------------------------------------------------------------------------------------------
50.19.99.64      255.255.255.255  0        STRONGVPN-PPTP    0        on           Yes      Netflix
50.19.103.125    255.255.255.255  0        STRONGVPN-PPTP    0        on           Yes      Netflix
50.19.119.154    255.255.255.255  0        STRONGVPN-PPTP    0        on           Yes      Netflix
69.53.236.17     255.255.255.255  0        STRONGVPN-PPTP    0        on           Yes      Netflix
107.20.137.117   255.255.255.255  0        STRONGVPN-PPTP    0        on           Yes      Netflix
107.20.232.200   255.255.255.255  0        STRONGVPN-PPTP    0        on           Yes      Netflix
107.21.96.127    255.255.255.255  0        STRONGVPN-PPTP    0        on           Yes      Netflix
192.168.0.0      255.255.0.0      0        0.0.0.0           0        No           Yes      block private networks: 192.168.x.y
172.16.0.0       255.240.0.0      0        0.0.0.0           0        No           Yes      block private networks: 172.16-31.x.y
10.0.0.0         255.0.0.0        0        0.0.0.0           0        No           Yes      block private network: 10.x.y.z
224.0.0.0        224.0.0.0        0        0.0.0.0           0        No           Yes      block multicasts: 224-255.x.y.z
255.255.255.255  0.0.0.0          0        INTERNET          0        on           Yes

ping doch einfach mal diese Adressen an und mache einen IP-Router-Trace (trace # ip-router) - und du wirst sehen, daß die pings nach STRONGVPN-PPTP geoutert werden...

Gruß
Backslash