VPN - connectable but unaddressable

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
jstrauss
DD-WRT Novice


Joined: 17 Jun 2006
Posts: 41

PostPosted: Mon Jun 19, 2006 21:15    Post subject: VPN - connectable but unaddressable Reply with quote
Hi,

I just installed the VPN version of DD-WRT (http://www.dd-wrt.com/dd-wrtv2/downloads/index.php?path=untested_alpha_unstable/dd-wrt.v23 SP1 multilanguage/2006 - 0619/&download=dd-wrt.v23_vpn_wrt54g.bin)

Setup the VPN server according to the wiki (using certificates). I'm able to connect to the VPN server from my MS client using OpenVPN, but I am unable to route to the new network. Here is an ASCII of my devices:

Code:

Internet
|
|-Linksys (wrt54gs)  (external IP/192.168.1.1)
  |
  |- M$ client with OpenVPN (192.168.1.127)
  |- DD-WRT (wrt54GL)       (192.168.1.3  /  192.168.10.1)
         |
         |- Linux (ubuntu)       (192.168.10.102)


I would think that once I have the VPN setup, I could ssh from my M$ client to my ubuntu server (i.e. from 192.168.1.127 -> 192.168.10.102) or even go to the administration page on the DD-WRT (via the VPN). But no joy on either of those.

Is there something I'm missing? My M$ OpenVPn client says "connected", my log is (way below)

Also when I do: ipconfig
on my M$ client I don't see the 192.168.10.x network listed.

Any help would be much appreciated
Thank you
Jay

Code:

C:\Documents and Settings\jstrauss>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : e1705
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . :

Ethernet adapter Local Area Connection:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Cont
roller
        Physical Address. . . . . . . . . : 00-14-22-F7-1D-9F

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . : wan
        Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
k Connection
        Physical Address. . . . . . . . . : 00-13-02-5B-34-CD
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.127
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.1.1
        Primary WINS Server . . . . . . . : 192.168.1.1
        Lease Obtained. . . . . . . . . . : Monday, June 19, 2006 3:39:46 PM
        Lease Expires . . . . . . . . . . : Tuesday, June 20, 2006 3:39:46 PM

Ethernet adapter Local Area Connection 4:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : TAP-Win32 Adapter V8
        Physical Address. . . . . . . . . : 00-FF-57-CA-FF-D8
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        Autoconfiguration IP Address. . . : 169.254.111.2
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Bluetooth Personal Area Network from
 TOSHIBA
        Physical Address. . . . . . . . . : 00-16-41-5C-0F-60


Code:

Mon Jun 19 16:02:08 2006 Connection reset, restarting [0]
Mon Jun 19 16:02:08 2006 TCP/UDP: Closing socket
Mon Jun 19 16:02:08 2006 SIGUSR1[soft,connection-reset] received, process restarting
Mon Jun 19 16:02:08 2006 Restart pause, 5 second(s)
Mon Jun 19 16:02:13 2006 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Mon Jun 19 16:02:13 2006 Re-using SSL/TLS context
Mon Jun 19 16:02:13 2006 LZO compression initialized
Mon Jun 19 16:02:13 2006 Control Channel MTU parms [ L:1576 D:140 EF:40 EB:0 ET:0 EL:0 ]
Mon Jun 19 16:02:13 2006 Preserving previous TUN/TAP instance: Local Area Connection 4
Mon Jun 19 16:02:13 2006 Data Channel MTU parms [ L:1576 D:1450 EF:44 EB:135 ET:32 EL:0 AF:3/1 ]
Mon Jun 19 16:02:13 2006 Local Options hash (VER=V4): '31fdf004'
Mon Jun 19 16:02:13 2006 Expected Remote Options hash (VER=V4): '3e6d1056'
Mon Jun 19 16:02:13 2006 Attempting to establish TCP connection with 192.168.1.3:44044
Mon Jun 19 16:02:13 2006 TCP connection established with 192.168.1.3:44044
Mon Jun 19 16:02:13 2006 TCPv4_CLIENT link local: [undef]
Mon Jun 19 16:02:13 2006 TCPv4_CLIENT link remote: 192.168.1.3:44044
Mon Jun 19 16:02:13 2006 TLS: Initial packet from 192.168.1.3:44044, sid=67a8d13d fc86304d
Mon Jun 19 16:02:14 2006 VERIFY OK: depth=1, /C=US/ST=IL/L=Chicago/O=g_Mortgage/CN=OpenVPN-CA/emailAddress=jay@adf.com
Mon Jun 19 16:02:14 2006 VERIFY OK: nsCertType=SERVER
Mon Jun 19 16:02:14 2006 VERIFY OK: depth=0, /C=US/ST=IL/O=g_Mortgage/CN=server/emailAddress=jay@adf.com
Mon Jun 19 16:02:15 2006 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jun 19 16:02:15 2006 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jun 19 16:02:15 2006 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jun 19 16:02:15 2006 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jun 19 16:02:15 2006 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Mon Jun 19 16:02:15 2006 [server] Peer Connection Initiated with 192.168.1.3:44044
Mon Jun 19 16:02:16 2006 Initialization Sequence Completed
Mon Jun 19 16:04:16 2006 Connection reset, restarting [0]
Mon Jun 19 16:04:16 2006 TCP/UDP: Closing socket
Mon Jun 19 16:04:16 2006 SIGUSR1[soft,connection-reset] received, process restarting
Mon Jun 19 16:04:16 2006 Restart pause, 5 second(s)
Mon Jun 19 16:04:21 2006 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Mon Jun 19 16:04:21 2006 Re-using SSL/TLS context
Mon Jun 19 16:04:21 2006 LZO compression initialized
Mon Jun 19 16:04:21 2006 Control Channel MTU parms [ L:1576 D:140 EF:40 EB:0 ET:0 EL:0 ]
Mon Jun 19 16:04:21 2006 Preserving previous TUN/TAP instance: Local Area Connection 4
Mon Jun 19 16:04:21 2006 Data Channel MTU parms [ L:1576 D:1450 EF:44 EB:135 ET:32 EL:0 AF:3/1 ]
Mon Jun 19 16:04:21 2006 Local Options hash (VER=V4): '31fdf004'
Mon Jun 19 16:04:21 2006 Expected Remote Options hash (VER=V4): '3e6d1056'
Mon Jun 19 16:04:21 2006 Attempting to establish TCP connection with 192.168.1.3:44044
Mon Jun 19 16:04:21 2006 TCP connection established with 192.168.1.3:44044
Mon Jun 19 16:04:21 2006 TCPv4_CLIENT link local: [undef]
Mon Jun 19 16:04:21 2006 TCPv4_CLIENT link remote: 192.168.1.3:44044
Mon Jun 19 16:04:21 2006 TLS: Initial packet from 192.168.1.3:44044, sid=13fe7336 f2c76962
Mon Jun 19 16:04:21 2006 VERIFY OK: depth=1, /C=US/ST=IL/L=Chicago/O=g_Mortgage/CN=OpenVPN-CA/emailAddress=jay@adf.com
Mon Jun 19 16:04:21 2006 VERIFY OK: nsCertType=SERVER
Mon Jun 19 16:04:21 2006 VERIFY OK: depth=0, /C=US/ST=IL/O=g_Mortgage/CN=server/emailAddress=jay@adf.com
Mon Jun 19 16:04:22 2006 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jun 19 16:04:22 2006 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jun 19 16:04:22 2006 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jun 19 16:04:22 2006 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jun 19 16:04:22 2006 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Mon Jun 19 16:04:22 2006 [server] Peer Connection Initiated with 192.168.1.3:44044
Mon Jun 19 16:04:23 2006 Initialization Sequence Completed
Sponsor
krikkit
DD-WRT User


Joined: 07 Jun 2006
Posts: 68
Location: Vienna

PostPosted: Mon Jun 19, 2006 21:42    Post subject: Reply with quote
i think you need to set up a dhcp server... because you don't get a IP adress on your "TAP-Win32 Adapter" ...another option would be to set a static ip of 192.168.1.x to this tap-win32 adapter..

also have a look on this thread: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=541

_________________
Using Firmware:
DD-WRT v24-sp2 (01/29/09) vpn
(SVN revision 11514) on WRT54G v3.1
jstrauss
DD-WRT Novice


Joined: 17 Jun 2006
Posts: 41

PostPosted: Tue Jun 20, 2006 2:30    Post subject: Reply with quote
I concur with the above post. The newest VPN version is broke. But 6/16/2006 works fine

Thanks for the help
Jay
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum