Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: vpnc: devel

VPNC connects but no traffice

 

 

vpnc devel RSS feed   Index | Next | Previous | View Threaded


info at arkansassoftball

Dec 30, 2008, 11:30 AM

Post #1 of 10 (2336 views)
Permalink
VPNC connects but no traffice

I am using the vpnc vs 0.5.3 with Cgwin on a XP windows 32. The tunnel
connects fine I get an IP and the TAP adapter (Openvpn vs 2.1rc15) connects
fine and the tunnel comes up without any errors; however, I am not passing
any traffic. The default route is established and I looked on the ASA and it
is getting 0 decaps or encaps.



Following is default.config



## generated by pcf2vpnc

IPSec ID PBR-Remote

IPSec gateway xxxxxxx

IPSec secret xxxxxxxxxx

Xauth username xxxx

IKE Authmode psk









Interface name TAP-Win32-V9

Interface mode tap

Local Port 1000

NAT Traversal Mode cisco-udp



Script /etc/vpnc/custom-script-pbr

/etc/vpnc/pbr.conf (END)





Here is partial capture from debug 3 after tunnels comes up.



sending: ========================>

BEGIN_PARSE

Recieved Packet Len: 60

i_cookie: 324f5012 3a70cd8c

r_cookie: 6b969266 d9f10e0f

payload: 08 (ISAKMP_PAYLOAD_HASH)

isakmp_version: 10

exchange_type: 20 (ISAKMP_EXCHANGE_IKE_QUICK)

flags: 01

message_id: 57c8525d

len: 0000003c



PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)

next_type: 00 (ISAKMP_PAYLOAD_NONE)

length: 0014

ke.data: 5f127994 370cd4cb ac765b47 1af8cf99

DONE PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)



PARSING PAYLOAD type: 00 (ISAKMP_PAYLOAD_NONE)

PARSE_OK



S7.7 QM_packet3 sent

[2008-12-30 13:21:29]



S7.8 setup ipsec tunnel

[2008-12-30 13:21:29]

generating 44 bytes keymat (cnt=3)

generating 44 bytes keymat (cnt=3)



S7.9 main loop (receive and transmit ipsec packets)

[2008-12-30 13:21:29]

rx.key_cry:

c70f3091 4116dd38 56aecc12 e1b0d0d2 e12c1375 2a6b78d0

rx.key_md:

e5546dae f8dc6a9e 15417d8f 1de3752b b91865fc

tx.key_cry:

1b1fd3de 37c734b8 ed5d597d 81ff7d91 bc4bc7c5 cf67a6a2

tx.key_md:

f5f3772e b2f875d9 96d97960 4a743f70 483f6e49

remote -> local spi: 0x9f41a24a

local -> remote spi: 0xdf2d0de1

VPNC started in foreground...

Rx pkt:

ffffffff ffff00ff f5fbcd76 08060001 08000604 000100ff f5fbcd76 c0a8c802

00000000 0000c0a8 c802

Rx pkt:

01005e00 001600ff f5fbcd76 08004600 0028e975 00000102 d298c0a8 c802e000

00169404 00002200 863d0000 00010400 0000ef53 646d

sending packet: len = 84, padding = 6

iv: 88421982 afc3c9b9 39727dcf 9c1f99df

sending ESP packet (before crypt):

00000000 00000000 00000000 00000000 00000000 df2d0de1 00000001 88421982

afc3c9b9 39727dcf 9c1f99df 46000028 e9750000 0102d298 c0a8c802 e0000016

94040000 2200863d 00000001 04000000 ef53646d 01020304 05060604

sending ESP packet (after crypt):

00000000 00000000 00000000 00000000 00000000 df2d0de1 00000001 88421982

afc3c9b9 39727dcf 9c1f99df 3197fc86 99d9d795 dea47101 94b5dcc2 6704cf1e

ed925f4a cc58be23 581ac216 5f0d8d86 046fbc45 39ff96af daefc930

sending ESP packet (after ah):

00000000 00000000 00000000 00000000 00000000 df2d0de1 00000001 88421982

afc3c9b9 39727dcf 9c1f99df 3197fc86 99d9d795 dea47101 94b5dcc2 6704cf1e

ed925f4a cc58be23 581ac216 5f0d8d86 046fbc45 39ff96af daefc930 ddf03c62

b265f239 93558c39

size = 52, blksz = 16, padding = 12



sending: ========================>

BEGIN_PARSE

Rx pkt:

01 00Recieved Packet Len: 92

5e 00i_cookie: 32001600ff f5fbcd76 08004600 0028e977 00004f01500212
d23a967

c0cda88c

c8 02r_cookie: e06b0096

92006616 94d904f1 0e000f00

22 00payload: 08 (ISAKMP_PAYLOAD_HASH)

86isakmp_version: 10

3d 00exchange_type: 05 (ISAKMP_EXCHANGE_INFORMATIONAL)

00 flags: 01

00 01message_id: 0400 0000ef53 646d

0a 6bsending packet: len = 84, padding = 6

87 8civ:

4d ddlen: 0000005c

4d b9

b8PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)

59 d1next_type: 0b (ISAKMP_PAYLOAD_N)

a4 length: 0014

b9 d3ke.data: 60f8c18f 7c103a20 3f372e3b

93 80sending ESP packet (before crypt):

458d009b683800b3 c8e1a76100f6008c

40 DONE PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)

32 ff

ff PARSING PAYLOAD type: 0b (ISAKMP_PAYLOAD_N)

0a e1next_type: 00 (ISAKMP_PAYLOAD_NONE)

1a 73length: 0020

cefffb5e df2d0de1 00000002 4ddd4db9

b8n.doi: 00000001 (ISAKMP_DOI_IPSEC)

59 d1n.protocol: 01 (ISAKMP_IPSEC_PROTO_ISAKMP)

a4 n.spi_length: 10

b9 d3n.type: 8d28 (ISAKMP_N_R_U_THERE)

60 c1n.spi: 32104f20503f122e 3a467000cd008c28 6b969266 d9f10e0f

e9 77n.data: 00e80053 ac017802

d2 96DONE PARSING PAYLOAD type: 0b (ISAKMP_PAYLOAD_N)

c0

a8 c8PARSING PAYLOAD type: 00 (ISAKMP_PAYLOAD_NONE)

02 PARSE_OK

e0000016

94040000 2200863d 00000001 04000000 ef53646d 01020304 05060604

sending ESP packet (after crypt):

45lifetime status: 0 of 28800 seconds used, 0|0 of 0 kbytes used

006800 c8a70000 4032ffff 0ae11a73 cefffb5e df2d0de1 00000002 4ddd4db9

received something on ike fd..

b859d1a4 b9d360c1 10203f2e got late ike paket: 188 bytes

ae BEGIN_PARSE

41cd 1bRecieved Packet Len: 188

i_cookie: 324f5012 3a70cd8c

r_cookie: 6b969266 d9f10e0f

1e 96payload: 08 (ISAKMP_PAYLOAD_HASH)

b6 2eisakmp_version: 10

7a875815 e8c85f8e df0ac81f

e5exchange_type: 20 (ISAKMP_EXCHANGE_IKE_QUICK)

dc e5flags: 01

cf c9e89ec3 fe55f44d 96ce1bca 0d3cac22 8de29638 9ab5c496

message_id: 57c8525d

sending ESP packet (after ah):

len: 000000bc

45 00

68 00PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)

c8a70000 4032ffff 0ae11a73 cefffb5e df2d0de1 00000002 4ddd4db9

b8next_type: 62 (unknown)



















sending ESP packet (after ah):

45002801 c8d50000 40325fe8 0ae11a73 cefffb5e df2d0de1 00000030 e706bdc9

546e73df 72451005 cdxx5 5502a5b9 eb1eca22 df9fbdab d0c3336e 14ad84d1

ed05a3bd 15bd04d7 18859917 70172082 5383d0e3 a3328bea 39130374 54ab171d

765d70cb e3142767 580423f1 de082c92 e592462c d92bf2d3 63da66d2 e294e9ed

eae49106 fbc4d22f 853dfc37 6f979f0e 8762a7d5 6c689563 7f905604 f31f3763

6abcbe0f 3efae2c9 d958152b 4aab7b7f de1fc38d f09f16bc c78d8087 d34a20bcx

73c22ef4 58b697f7 0e98f740 24dde122

957f8bb2 2de155fb e5ae957b ea93dfc1 c2f7c9a0 cb021b55 6bea1efd a36bea9b

21fab428 80b3ee2d dd69d742 8e53c18a 56adef3e 3e249fc1 16272279 21c3e2d0

79240128 dcd51e6f

Rx pkt:

ffffffff ffff00ff f5fbcd76 08060001 08000604 000100ff f5fbcd76 c0a8c802

00000000 00000a64 6402

ARP reply:

00fff5fb cd7680ff f5fbcd76 08060001 08000604 000280ff f5fbcd76 0a646402

00fff5fb cd76c0a8 c802

Rx pkt:

80fff5fb cd7600ff f5fbcd76 08004500 003ced82 00008001 562dc0a8 c8020a64

64020800 445c0400 05006162 63646566 6768696a 6b6c6d6e 6f707172 73747576

77616263 64656667 6869

sending packet: len = 104, padding = 2

iv: 2173a9ee 031ab770 fb5c7786 e3d5a43a

sending ESP packet (before crypt):

45002801 c8d60000 40323a5b 0ae11a73 cefffb5e df2d0de1 00000031 2173a9ee

031ab770 fb5c7786 e3d5a43a 4500003c ed820000 8001562d c0a8c802 0a646402

0800445c 04000500 61626364 65666768 696a6b6c 6d6e6f70 71727374 75767761

62636465 66676869 01020204

sending ESP packet (after crypt):

45002801 c8d60000 40323a5b 0ae11a73 cefffb5e df2d0de1 00000031 2173a9ee

031ab770 fb5c7786 e3d5a43a fa7f3740 d99d7312 585628f9 7f78aa71 2fa9343a

ce281ba2 ccfaa7cb e121b86f dc991da1 b2ae476b 9cc63ddb c869d254 d0506fa7

e0bfbb12 55259566 f456919b

sending ESP packet (after ah):

45002801 c8d60000 40323a5b 0ae11a73 cefffb5e df2d0de1 00000031 2173a9ee

031ab770 fb5c7786 xxx3a fa7f3740 d99d7312 585628f9 7f78aa71 2fa9343a

ce281ba2 ccfaa7cb e121b86f dc991da1 b2ae476b 9cc63ddb c869d254 d0506fa7

e0bfbb12 55259566 f456919b 94f8ec40 c52e32c0 178f7868

Rx pkt:

80fff5fb cd7600ff f5fbcd76 08004500 003ced8f 00008001 5620c0a8 c8020a64

64020800 435c0400 06006162 63646566 6768696a 6b6c6d6e 6f707172 73747576

77616263 64656667 6869

sending packet: len = 104, padding = 2

iv: 10166fe6 2e395ee5 1c7d835b e388a191

sending ESP packet (before crypt):

45007800 c8d70000 40325fe7 0ae11a73 cefffb5e df2d0de1 00000032 10166fe6

2e395ee5 1c7d835b e388a191 4500003c ed8f0000 80015620 c0a8c802 0a646402

0800435c 04000600 6xxx 65666768 696a6b6c 6d6e6f70 71727374 75767761

62636465 66676869 01020204

sending ESP packet (after crypt):

45007800 c8d70000 4xxxfe7 0ae11a73 cefffb5e df2d0de1 00000032 10166fe6

2e395ee5 1c7d835b e388a191 437400ce ad0a6c59 c357ec68 dcbb9800 44747bad

389ab60d 74c81f36 30e2e326 66332d96 16296dfd b7a940f2 bee426c4 7dd1fb15

55dcc171 c12c7f72 2b03ac65

sending ESP packet (after ah):

45007800 c8d70000 40325fe7 0ae11a73 cefffb5e df2d0de1 00000032 10166fe6

2e395ee5 1c7d835b e3xxxx1 437400ce ad0a6c59 c357ec68 dcbb9800 44747bad

389ab60d 74c81f36 30e2e326 66332d96 16296dfd b7a940f2 bee426c4 7dd1fb15

55dcc171 c12c7f72 2b03ac65 dbcc1b01 0bc9d527 7197cac7

Rx pkt:

80fff5fb cd7600ff xx 003ced94 00008001 561bc0a8 c8020a64

64020800 425c0400 07006162 63646566 6768696a 6b6c6d6e 6f707172 73747576

77616263 64656667 6869

sending packet: len = 104, padding = 2

iv: 51fe647c 0475c29e b605e91b a274c34e

sending ESP packet (before crypt):

45007800 c8d80000 40xxxx5a 0ae11a73 cefffb5e df2d0de1 00000033 51fe647c

0475c29e b605e91b a274c34e 4500003c ed940000 8001561b c0a8c802 0a646402

0800425c 04000700 61626364 65666768 696a6b6c 6d6e6f70 71727374 75767761

62636465 66676869 01020204

sending ESP packet (after crypt):

45007800 c8d80000 403xxxa 0ae11a73 cefffb5e df2d0de1 00000033 51fe647c

0475c29e b605e91b a274c34e f6a85dad 0f86bea0 2a794e28 0571eb87 42c65f00

42b335ca 78a33ec8 a95c4813 ea901d07 97ec7e3b 9fee2f7b 227efffd 37086ecf

682f0696 e9a440d1 ef8522dd

sending ESP packet (after ah):

45007800 c8d80000 40xxxea5a 0ae11a73 cefffb5e df2d0de1 00000033 51fe647c

0475c29e b605e91b a274c34e f6a85dad 0f86bea0 2a794e28 0571eb87 42c65f00

42b335ca 78a33ec8 a95c4813 ea901d07 97ec7e3b 9fee2f7b 227efffd 37086ecf

682f0696 e9a440d1 ef8522dd ac7cbd31 252ceab1 affdf138

lifetime status: 159 of 28800 seconds used, 0|6 of 0 kbytes used

pnc: PID 432: select: Interrupted system call

pnc: PID 432: terminated by signal: 2



7.10 send ipsec termination message

[2008-12-30 13:24:08]

size = 40, blksz = 16, padding = 8



sending: ========================>

BEGIN_PARSE

Recieved Packet Len: 76

i_cookie: 324f5012 3a70cd8c

r_cookie: 6b969266 d9f10e0f

payload: 08 (ISAKMP_PAYLOAD_HASH)

isakmp_version: 10

exchange_type: 05 (ISAKMP_EXCHANGE_INFORMATIONAL)

flags: 01

message_id: ed000000

len: 0000004c



PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)

next_type: 0c (ISAKMP_PAYLOAD_D)

length: 0014

ke.data: 34129634 43147858 c9f475f7 8d8ad967

DONE PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)



PARSING PAYLOAD type: 0c (ISAKMP_PAYLOAD_D)

next_type: 00 (ISAKMP_PAYLOAD_NONE)

length: 0014

d.doi: 00000001 (ISAKMP_DOI_IPSEC)

d.protocol: 03 (ISAKMP_IPSEC_PROTO_IPSEC_ESP)

d.spi_length: 04

d.num_spi: 0002

d.spi: 9f41a24a

d.spi: df2d0de1

DONE PARSING PAYLOAD type: 0c (ISAKMP_PAYLOAD_D)



PARSING PAYLOAD type: 00 (ISAKMP_PAYLOAD_NONE)

PARSE_OK



7.11 send isakmp termination message

[2008-12-30 13:24:08]

size = 48, blksz = 16, padding = 0



sending: ========================>

BEGIN_PARSE

Recieved Packet Len: 76

i_cookie: 324f5012 3a70cd8c

r_cookie: 6b969266 d9f10e0f

payload: 08 (ISAKMP_PAYLOAD_HASH)

isakmp_version: 10

exchange_type: 05 (ISAKMP_EXCHANGE_INFORMATIONAL)

flags: 01

message_id: 78000000

len: 0000004c



PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)

next_type: 0c (ISAKMP_PAYLOAD_D)

length: 0014

ke.data: 02cabe01 8e3bd46d f71ffe02 3a6ece89

DONE PARSING PAYLOAD type: 08 (ISAKMP_PAYLOAD_HASH)



PARSING PAYLOAD type: 0c (ISAKMP_PAYLOAD_D)

next_type: 00 (ISAKMP_PAYLOAD_NONE)

length: 001c

d.doi: 00000001 (ISAKMP_DOI_IPSEC)

d.protocol: 01 (ISAKMP_IPSEC_PROTO_ISAKMP)

d.spi_length: 10

d.num_spi: 0001

d.spi: 324f5012 3a70cd8c 6b969266 d9f10e0f

DONE PARSING PAYLOAD type: 0c (ISAKMP_PAYLOAD_D)



PARSING PAYLOAD type: 00 (ISAKMP_PAYLOAD_NONE)

PARSE_OK



8 close_tunnel

[2008-12-30 13:24:08]

icrosoft (R) Windows Script Host Version 5.7

opyright (C) Microsoft Corporation. All rights reserved.


anaxagorasbc at yahoo

Dec 31, 2008, 4:51 PM

Post #2 of 10 (2250 views)
Permalink
Re: VPNC connects but no traffice [In reply to]

I am experiencing a similar problem. I'm sure it's just not routes being setup correctly. I need all of my traffic to go through TAP interface.


info at arkansassoftball

Jan 2, 2009, 6:21 AM

Post #3 of 10 (2243 views)
Permalink
Re: VPNC connects but no traffice [In reply to]

When I do a route print the routes appear correct.

IE

10.x.x.x mask 255.0.0.0 via 192.168.x.x (tap interface).



I know traffic is routing through tap because I can do an extended ping when
I disconnect the interface I get "hardware error" instead of request time
out on a few packets. The hardware error is when the TAP

interface gets disconnected.



From: vpnc-devel-bounces [at] unix-ag
[mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of Nick
Sent: Wednesday, December 31, 2008 6:51 PM
To: vpnc-devel [at] unix-ag
Subject: Re: [vpnc-devel] VPNC connects but no traffice



I am experiencing a similar problem. I'm sure it's just not routes being
setup correctly. I need all of my traffic to go through TAP interface.


gary at webguild

Jan 2, 2009, 1:00 PM

Post #4 of 10 (2239 views)
Permalink
Re: VPNC connects but no traffice [In reply to]

I have been trying for a couple weeks to get this working without success,
though I think I am close.



I have downloaded Cygwin (plus libgcrypt, make, perl and gcc), vpnc 0.5.3,
openvpn 2.1.rc15 (installing only the Tap selection).



I compiled vpnc; edited the vpnc-script-win.js file to fix the recognition
of the default gateway (for Vista and Win Server 2008, see below). I created
the vpnc.conf file based on my Cisco pcf file and ran make install.



I renamed the network connection from openvpn to be "Tap".



I then started the Cygwin terminal by running as admin and typed vpnc (some
numbers have been altered for security).



$ vpnc

> route print 0.0.0.0

Default Gateway :192.168.0.1

VPN Gateway: 12.0.173.37

Internal Address: 10.243.56.75

Internal Netmask: 255.255.254.0

Interface: "Tap"

Configuring "Tap" interface...

> netsh interface ip set address "Tap" static 10.243.56.75 255.255.254.0

> route add 12.0.173.37 mask 255.255.255.255 192.168.0.1

> netsh interface ip add wins "Tap" 10.243.32.72 index=1

> netsh interface ip add wins "Tap" 10.243.32.113 index=2

> netsh interface ip add dns "Tap" 10.243.32.25 index=1

> netsh interface ip add dns "Tap" 10.243.32.26 index=2

done.

Configuring networks:

Gateway did not provide network configuration.

Route configuration done.

VPNC started in foreground...



The lines below starting with ">" are from an echo I added to the run
function as shown below (also note the replaced line in getDefaultGateway():





function run(cmd)

{

echo("> " + cmd);

return (ws.Exec(cmd).StdOut.ReadAll());

}



function getDefaultGateway()

{

if (run("route print 0.0.0.0").match(/0\.0\.0\.0 *0\.0\.0\.0 *([^
]*)/)) {

return (RegExp.$1);

}

return ("");

}



This is output from route print after the vpnc was set up:



===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 10

10.243.56.0 255.255.254.0 On-link 10.243.56.75 286

10.243.56.75 255.255.255.255 On-link 10.243.56.75 286

10.243.57.255 255.255.255.255 On-link 10.243.56.75 286

12.0.173.37 255.255.255.255 192.168.0.1 192.168.0.2 11

127.0.0.0 255.0.0.0 On-link 127.0.0.1 306

127.0.0.1 255.255.255.255 On-link 127.0.0.1 306

127.255.255.255 255.255.255.255 On-link 127.0.0.1 306

192.168.0.0 255.255.255.0 On-link 192.168.0.2 266

192.168.0.2 255.255.255.255 On-link 192.168.0.2 266

192.168.0.255 255.255.255.255 On-link 192.168.0.2 266

224.0.0.0 240.0.0.0 On-link 127.0.0.1 306

224.0.0.0 240.0.0.0 On-link 192.168.0.2 266

224.0.0.0 240.0.0.0 On-link 10.243.56.75 286

255.255.255.255 255.255.255.255 On-link 127.0.0.1 306

255.255.255.255 255.255.255.255 On-link 192.168.0.2 266

255.255.255.255 255.255.255.255 On-link 10.243.56.75 286

===========================================================================

Persistent Routes:

None



Ipconfig /all (Why no Default Gateway?? Does it need a Primary DNS
Suffix??):



Windows IP Configuration



Host Name . . . . . . . . . . . . : Server

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Tap:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : TAP-Win32 Adapter V9

Physical Address. . . . . . . . . : 00-FF-68-3C-63-DB

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . :
fe80::c8a5:b17a:30b4:9b17%25(Preferred)

IPv4 Address. . . . . . . . . . . : 10.243.56.75(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.254.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 10.243.32.25

10.243.32.26

Primary WINS Server . . . . . . . : 10.243.32.72

Secondary WINS Server . . . . . . : 10.243.32.113

NetBIOS over Tcpip. . . . . . . . : Enabled



My vpnc.conf



## generated by pcf2vpnc

IPSec ID TunnelGroup

IPSec gateway 12.0.173.37

IPSec secret [decrypted secret]



Xauth username gary

Domain ABCFL

IKE Authmode psk

Xauth password [password]

Interface name Tap

Interface mode tap

Local Port 0

No detach



The properties of the network connections for the Tap interface have Status
showing as Unidentified network, Device Name as Tap-Win32 Adapter V9 and
Connectivity as Access to Local only, though I have also seen Limited
connectivity.



This home network is connected through a Trendnet router and cable modem to
Comcast.



Everything looks set up pretty much OK but I get no connectivity to the
servers at the other side of the VPN.



I have tried this on two Vista-64 systems and one Win Server 2008 (32-bit)
system all with the same problem.



Thanks,

Gary



From: vpnc-devel-bounces [at] unix-ag
[mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of
info [at] arkansassoftball
Sent: Friday, January 02, 2009 9:22 AM
To: 'vpnc list to send bug reports and discussions with developers'
Subject: Re: [vpnc-devel] VPNC connects but no traffice





When I do a route print the routes appear correct.

IE

10.x.x.x mask 255.0.0.0 via 192.168.x.x (tap interface).



I know traffic is routing through tap because I can do an extended ping when
I disconnect the interface I get "hardware error" instead of request time
out on a few packets. The hardware error is when the TAP

interface gets disconnected.



From: vpnc-devel-bounces [at] unix-ag
[mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of Nick
Sent: Wednesday, December 31, 2008 6:51 PM
To: vpnc-devel [at] unix-ag
Subject: Re: [vpnc-devel] VPNC connects but no traffice



I am experiencing a similar problem. I'm sure it's just not routes being
setup correctly. I need all of my traffic to go through TAP interface.


tilman.schroeder at tu-dortmund

Jan 4, 2009, 3:08 PM

Post #5 of 10 (2234 views)
Permalink
Re: VPNC connects but no traffice [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gary Davis wrote:
> I have been trying for a couple weeks to get this working without
> success, though I think I am close.
>
>
>
> I have downloaded Cygwin (plus libgcrypt, make, perl and gcc), vpnc
> 0.5.3, openvpn 2.1.rc15 (installing only the Tap selection).
>
>
>
> I compiled vpnc; edited the vpnc-script-win.js file to fix the
> recognition of the default gateway (for Vista and Win Server 2008, see
> below). I created the vpnc.conf file based on my Cisco pcf file and ran
> make install.
>
>
>
> I renamed the network connection from openvpn to be “Tap”.
>
>
>
> I then started the Cygwin terminal by running as admin and typed vpnc
> (some numbers have been altered for security).
>
>
>
> $ vpnc
>
>> route print 0.0.0.0
>
> Default Gateway :192.168.0.1
>
> VPN Gateway: 12.0.173.37
>
> Internal Address: 10.243.56.75
>
> Internal Netmask: 255.255.254.0
>
> Interface: "Tap"
>
> Configuring "Tap" interface...
>
>> netsh interface ip set address "Tap" static 10.243.56.75 255.255.254.0
>
>> route add 12.0.173.37 mask 255.255.255.255 192.168.0.1
>
>> netsh interface ip add wins "Tap" 10.243.32.72 index=1
>
>> netsh interface ip add wins "Tap" 10.243.32.113 index=2
>
>> netsh interface ip add dns "Tap" 10.243.32.25 index=1
>
>> netsh interface ip add dns "Tap" 10.243.32.26 index=2
>
> done.
>
> Configuring networks:
>
> Gateway did not provide network configuration.
>
> Route configuration done.
>
> VPNC started in foreground...
>
>
>
> The lines below starting with “>” are from an echo I added to the run
> function as shown below (also note the replaced line in getDefaultGateway():
>
>
>
>
>
> function run(cmd)
>
> {
>
> *echo("> " + cmd);*
>
> return (ws.Exec(cmd).StdOut.ReadAll());
>
> }
>
>
>
> function getDefaultGateway()
>
> {
>
> if *(run("route print 0.0.0.0").match(/0\.0\.0\.0 *0\.0\.0\.0
> *([^ ]*)/)) {*
>
> return (RegExp.$1);
>
> }
>
> return ("");
>
> }
>
>
>
> This is output from route print after the vpnc was set up:
>
>
>
> ===========================================================================
>
> Active Routes:
>
> Network Destination Netmask Gateway Interface Metric
>
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 10
>
> 10.243.56.0 255.255.254.0 On-link 10.243.56.75 286
>
> 10.243.56.75 255.255.255.255 On-link 10.243.56.75 286
>
> 10.243.57.255 255.255.255.255 On-link 10.243.56.75 286
>
> 12.0.173.37 255.255.255.255 192.168.0.1 192.168.0.2 11
>
> 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
>
> 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
>
> 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
>
> 192.168.0.0 255.255.255.0 On-link 192.168.0.2 266
>
> 192.168.0.2 255.255.255.255 On-link 192.168.0.2 266
>
> 192.168.0.255 255.255.255.255 On-link 192.168.0.2 266
>
> 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
>
> 224.0.0.0 240.0.0.0 On-link 192.168.0.2 266
>
> 224.0.0.0 240.0.0.0 On-link 10.243.56.75 286
>
> 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
>
> 255.255.255.255 255.255.255.255 On-link 192.168.0.2 266
>
> 255.255.255.255 255.255.255.255 On-link 10.243.56.75 286
>
> ===========================================================================
>
> Persistent Routes:
>
> None
>
>
>
> Ipconfig /all (Why no Default Gateway?? Does it need a Primary DNS
> Suffix??):
>
>
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : Server
>
> Primary Dns Suffix . . . . . . . :
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
>
>
> Ethernet adapter Tap:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : TAP-Win32 Adapter V9
>
> Physical Address. . . . . . . . . : 00-FF-68-3C-63-DB
>
> DHCP Enabled. . . . . . . . . . . : No
>
> Autoconfiguration Enabled . . . . : Yes
>
> Link-local IPv6 Address . . . . . :
> fe80::c8a5:b17a:30b4:9b17%25(Preferred)
>
> IPv4 Address. . . . . . . . . . . : 10.243.56.75(Preferred)
>
> Subnet Mask . . . . . . . . . . . : 255.255.254.0
>
> Default Gateway . . . . . . . . . :
>
> DNS Servers . . . . . . . . . . . : 10.243.32.25
>
> 10.243.32.26
>
> Primary WINS Server . . . . . . . : 10.243.32.72
>
> Secondary WINS Server . . . . . . : 10.243.32.113
>
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
>
>
> My vpnc.conf
>
>
>
> ## generated by pcf2vpnc
>
> IPSec ID TunnelGroup
>
> IPSec gateway 12.0.173.37
>
> IPSec secret [decrypted secret]
>
>
>
> Xauth username gary
>
> Domain ABCFL
>
> IKE Authmode psk
>
> Xauth password [password]
>
> Interface name Tap
>
> Interface mode tap
>
> Local Port 0
>
> No detach
>
>
>
> The properties of the network connections for the Tap interface have
> Status showing as *Unidentified network*, Device Name as *Tap-Win32
> Adapter V9* and Connectivity as *Access to Local only*, though I have
> also seen *Limited connectivity*.
>
>
>
> This home network is connected through a Trendnet router and cable modem
> to Comcast.
>
>
>
> Everything looks set up pretty much OK but I get no connectivity to the
> servers at the other side of the VPN.
>
>
>
> I have tried this on two Vista-64 systems and one Win Server 2008
> (32-bit) system all with the same problem.
>
>
>
> Thanks,
>
> Gary
>
>
>
> *From:* vpnc-devel-bounces [at] unix-ag
> [mailto:vpnc-devel-bounces [at] unix-ag] *On Behalf Of
> *info [at] arkansassoftball
> *Sent:* Friday, January 02, 2009 9:22 AM
> *To:* 'vpnc list to send bug reports and discussions with developers'
> *Subject:* Re: [vpnc-devel] VPNC connects but no traffice
>
>
>
>
>
> When I do a route print the routes appear correct.
>
> IE
>
> 10.x.x.x mask 255.0.0.0 via 192.168.x.x (tap interface).
>
>
>
> I know traffic is routing through tap because I can do an extended ping
> when I disconnect the interface I get “hardware error” instead of
> request time out on a few packets. The hardware error is when the TAP
>
> interface gets disconnected.
>
>
>
> *From:* vpnc-devel-bounces [at] unix-ag
> [mailto:vpnc-devel-bounces [at] unix-ag] *On Behalf Of *Nick
> *Sent:* Wednesday, December 31, 2008 6:51 PM
> *To:* vpnc-devel [at] unix-ag
> *Subject:* Re: [vpnc-devel] VPNC connects but no traffice
>
>
>
> I am experiencing a similar problem. I'm sure it's just not routes
> being setup correctly. I need all of my traffic to go through TAP
> interface.
>

Heyho,

I did some more testing and I observed this:
After a clean boot, I was *always* able to connect. After the first
connection no new connection was successful.

I compared the routes on my vista-64 machine to the ones vpnc
0.3.3+SVN20051028-3 (debian etch) established on my linux machine. The
difference was that on my linux machine, there was a direct route to the
vpn gateway which was *not* on my vista-64 machine, at least not at the
point where vpnc *always* stopped (S4.5 AM_packet3).

Then I added the following line to my vpnc-script-win-modified.js (which
is executed from vpnc-script, I edited vpnc-script accordingly) at the
"pre-init" stage:

run("route add xxx.xxx.xxx.xxx mask 255.255.255.255 "+gw);

I had to hardcode the vpn gateway ip address here because
env("VPNGATEWAY") returns an empty string at the pre-init stage.

I also did the following modification in order to have a more verbose
script:

function run(cmd)
{
echo(cmd);
var cmd_return=ws.Exec(cmd).StdOut.ReadAll();
echo(cmd_return);
return(cmd_return);

}

Gary, thanks for fixing the regex - Now it works.
Try to add "Debug 2" to your configuration file.

Some suggestions for future releases:

Make VPNGATEWAY available at the pre-init stage.
Make the debug level available to the script - it would be possible to
switch extended messages on and off depending on the debug level.

I attached my vpnc-script-win-modified.js (UTF-8) if somebody is
interested in it.

Have a good sleep,

Tilman Schröder
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJYUFPxWHJ8ml5laIRAptYAKCEI5xXFZkRKFkgGrwgGXB4Wo4K+gCeK/CC
UH+244nWObXM40m4Vq/BNKU=
=LWqM
-----END PGP SIGNATURE-----
Attachments: vpnc-script-win-modified.js (3.78 KB)
  vpnc-script-win-modified.js.sig (65 B)


info at arkansassoftball

Jan 4, 2009, 8:13 PM

Post #6 of 10 (2236 views)
Permalink
Re: VPNC connects but no traffice [In reply to]

I connect routing IS working correctly. I can do ICMP trace and packets are reaching the ASA on the remote network and the server is replying to ping. I am getting encaps and decaps on ASA; however, am not getting the unencrypted data on the client PC.



From ASA
#pkts encaps: 10, #pkts encrypt: 10, #pkts digest: 10
#pkts decaps: 57, #pkts decrypt: 57, #pkts verify: 57
#pkts compressed: 0, #pkts decompressed: 0
#pkts not compressed: 10, #pkts comp failed: 0, #pkts decomp failed: 0
#pre-frag successes: 0, #pre-frag failures: 0, #fragments created: 0
#PMTUs sent: 0, #PMTUs rcvd: 0, #decapsulated frgs needing reassembly: 0
#send errors: 0, #recv errors: 0

-----Original Message-----
From: vpnc-devel-bounces [at] unix-ag [mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of Tilman Schröder
Sent: Sunday, January 04, 2009 5:08 PM
To: vpnc list to send bug reports and discussions with developers
Subject: Re: [vpnc-devel] VPNC connects but no traffice

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gary Davis wrote:
> I have been trying for a couple weeks to get this working without
> success, though I think I am close.
>
>
>
> I have downloaded Cygwin (plus libgcrypt, make, perl and gcc), vpnc
> 0.5.3, openvpn 2.1.rc15 (installing only the Tap selection).
>
>
>
> I compiled vpnc; edited the vpnc-script-win.js file to fix the
> recognition of the default gateway (for Vista and Win Server 2008, see
> below). I created the vpnc.conf file based on my Cisco pcf file and
> ran make install.
>
>
>
> I renamed the network connection from openvpn to be “Tap”.
>
>
>
> I then started the Cygwin terminal by running as admin and typed vpnc
> (some numbers have been altered for security).
>
>
>
> $ vpnc
>
>> route print 0.0.0.0
>
> Default Gateway :192.168.0.1
>
> VPN Gateway: 12.0.173.37
>
> Internal Address: 10.243.56.75
>
> Internal Netmask: 255.255.254.0
>
> Interface: "Tap"
>
> Configuring "Tap" interface...
>
>> netsh interface ip set address "Tap" static 10.243.56.75
>> 255.255.254.0
>
>> route add 12.0.173.37 mask 255.255.255.255 192.168.0.1
>
>> netsh interface ip add wins "Tap" 10.243.32.72 index=1
>
>> netsh interface ip add wins "Tap" 10.243.32.113 index=2
>
>> netsh interface ip add dns "Tap" 10.243.32.25 index=1
>
>> netsh interface ip add dns "Tap" 10.243.32.26 index=2
>
> done.
>
> Configuring networks:
>
> Gateway did not provide network configuration.
>
> Route configuration done.
>
> VPNC started in foreground...
>
>
>
> The lines below starting with “>” are from an echo I added to the run
> function as shown below (also note the replaced line in getDefaultGateway():
>
>
>
>
>
> function run(cmd)
>
> {
>
> *echo("> " + cmd);*
>
> return (ws.Exec(cmd).StdOut.ReadAll());
>
> }
>
>
>
> function getDefaultGateway()
>
> {
>
> if *(run("route print 0.0.0.0").match(/0\.0\.0\.0 *0\.0\.0\.0
> *([^ ]*)/)) {*
>
> return (RegExp.$1);
>
> }
>
> return ("");
>
> }
>
>
>
> This is output from route print after the vpnc was set up:
>
>
>
> ======================================================================
> =====
>
> Active Routes:
>
> Network Destination Netmask Gateway Interface Metric
>
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 10
>
> 10.243.56.0 255.255.254.0 On-link 10.243.56.75 286
>
> 10.243.56.75 255.255.255.255 On-link 10.243.56.75 286
>
> 10.243.57.255 255.255.255.255 On-link 10.243.56.75 286
>
> 12.0.173.37 255.255.255.255 192.168.0.1 192.168.0.2 11
>
> 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
>
> 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
>
> 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
>
> 192.168.0.0 255.255.255.0 On-link 192.168.0.2 266
>
> 192.168.0.2 255.255.255.255 On-link 192.168.0.2 266
>
> 192.168.0.255 255.255.255.255 On-link 192.168.0.2 266
>
> 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
>
> 224.0.0.0 240.0.0.0 On-link 192.168.0.2 266
>
> 224.0.0.0 240.0.0.0 On-link 10.243.56.75 286
>
> 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
>
> 255.255.255.255 255.255.255.255 On-link 192.168.0.2 266
>
> 255.255.255.255 255.255.255.255 On-link 10.243.56.75 286
>
> ======================================================================
> =====
>
> Persistent Routes:
>
> None
>
>
>
> Ipconfig /all (Why no Default Gateway?? Does it need a Primary DNS
> Suffix??):
>
>
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : Server
>
> Primary Dns Suffix . . . . . . . :
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
>
>
> Ethernet adapter Tap:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : TAP-Win32 Adapter V9
>
> Physical Address. . . . . . . . . : 00-FF-68-3C-63-DB
>
> DHCP Enabled. . . . . . . . . . . : No
>
> Autoconfiguration Enabled . . . . : Yes
>
> Link-local IPv6 Address . . . . . :
> fe80::c8a5:b17a:30b4:9b17%25(Preferred)
>
> IPv4 Address. . . . . . . . . . . : 10.243.56.75(Preferred)
>
> Subnet Mask . . . . . . . . . . . : 255.255.254.0
>
> Default Gateway . . . . . . . . . :
>
> DNS Servers . . . . . . . . . . . : 10.243.32.25
>
> 10.243.32.26
>
> Primary WINS Server . . . . . . . : 10.243.32.72
>
> Secondary WINS Server . . . . . . : 10.243.32.113
>
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
>
>
> My vpnc.conf
>
>
>
> ## generated by pcf2vpnc
>
> IPSec ID TunnelGroup
>
> IPSec gateway 12.0.173.37
>
> IPSec secret [decrypted secret]
>
>
>
> Xauth username gary
>
> Domain ABCFL
>
> IKE Authmode psk
>
> Xauth password [password]
>
> Interface name Tap
>
> Interface mode tap
>
> Local Port 0
>
> No detach
>
>
>
> The properties of the network connections for the Tap interface have
> Status showing as *Unidentified network*, Device Name as *Tap-Win32
> Adapter V9* and Connectivity as *Access to Local only*, though I have
> also seen *Limited connectivity*.
>
>
>
> This home network is connected through a Trendnet router and cable
> modem to Comcast.
>
>
>
> Everything looks set up pretty much OK but I get no connectivity to
> the servers at the other side of the VPN.
>
>
>
> I have tried this on two Vista-64 systems and one Win Server 2008
> (32-bit) system all with the same problem.
>
>
>
> Thanks,
>
> Gary
>
>
>
> *From:* vpnc-devel-bounces [at] unix-ag
> [mailto:vpnc-devel-bounces [at] unix-ag] *On Behalf Of
> *info [at] arkansassoftball
> *Sent:* Friday, January 02, 2009 9:22 AM
> *To:* 'vpnc list to send bug reports and discussions with developers'
> *Subject:* Re: [vpnc-devel] VPNC connects but no traffice
>
>
>
>
>
> When I do a route print the routes appear correct.
>
> IE
>
> 10.x.x.x mask 255.0.0.0 via 192.168.x.x (tap interface).
>
>
>
> I know traffic is routing through tap because I can do an extended
> ping when I disconnect the interface I get “hardware error” instead of
> request time out on a few packets. The hardware error is when the TAP
>
> interface gets disconnected.
>
>
>
> *From:* vpnc-devel-bounces [at] unix-ag
> [mailto:vpnc-devel-bounces [at] unix-ag] *On Behalf Of *Nick
> *Sent:* Wednesday, December 31, 2008 6:51 PM
> *To:* vpnc-devel [at] unix-ag
> *Subject:* Re: [vpnc-devel] VPNC connects but no traffice
>
>
>
> I am experiencing a similar problem. I'm sure it's just not routes
> being setup correctly. I need all of my traffic to go through TAP
> interface.
>

Heyho,

I did some more testing and I observed this:
After a clean boot, I was *always* able to connect. After the first connection no new connection was successful.

I compared the routes on my vista-64 machine to the ones vpnc
0.3.3+SVN20051028-3 (debian etch) established on my linux machine. The difference was that on my linux machine, there was a direct route to the vpn gateway which was *not* on my vista-64 machine, at least not at the point where vpnc *always* stopped (S4.5 AM_packet3).

Then I added the following line to my vpnc-script-win-modified.js (which is executed from vpnc-script, I edited vpnc-script accordingly) at the "pre-init" stage:

run("route add xxx.xxx.xxx.xxx mask 255.255.255.255 "+gw);

I had to hardcode the vpn gateway ip address here because
env("VPNGATEWAY") returns an empty string at the pre-init stage.

I also did the following modification in order to have a more verbose
script:

function run(cmd)
{
echo(cmd);
var cmd_return=ws.Exec(cmd).StdOut.ReadAll();
echo(cmd_return);
return(cmd_return);

}

Gary, thanks for fixing the regex - Now it works.
Try to add "Debug 2" to your configuration file.

Some suggestions for future releases:

Make VPNGATEWAY available at the pre-init stage.
Make the debug level available to the script - it would be possible to switch extended messages on and off depending on the debug level.

I attached my vpnc-script-win-modified.js (UTF-8) if somebody is interested in it.

Have a good sleep,

Tilman Schröder
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJYUFPxWHJ8ml5laIRAptYAKCEI5xXFZkRKFkgGrwgGXB4Wo4K+gCeK/CC
UH+244nWObXM40m4Vq/BNKU=
=LWqM
-----END PGP SIGNATURE-----


_______________________________________________
vpnc-devel mailing list
vpnc-devel [at] unix-ag
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/


jmvpnc at loplof

Jan 8, 2009, 9:38 AM

Post #7 of 10 (2206 views)
Permalink
Re: VPNC connects but no traffic [In reply to]

On Sun, Jan 04, 2009 at 10:13:52PM -0600, info [at] arkansassoftball wrote:
> I connect routing IS working correctly. I can do ICMP trace and packets are reaching the ASA on the remote network and the server is replying to ping. I am getting encaps and decaps on ASA; however, am not getting the unencrypted data on the client PC.
...
> From ASA
> #pkts encaps: 10, #pkts encrypt: 10, #pkts digest: 10
> #pkts decaps: 57, #pkts decrypt: 57, #pkts verify: 57
...
> #send errors: 0, #recv errors: 0

As the trace is missing the ISAKMP stuff, I'm not sure whether cisco-udp nat
traversal is being used or native ESP encapsulation is used. Either way:
Somewhere between ASA --> PC someone drops the ESP packets (either in native
form or in cisco-udp encapsulated form).

ciao
Joerg
--
Joerg Mayer <jmayer [at] loplof>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
_______________________________________________
vpnc-devel mailing list
vpnc-devel [at] unix-ag
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/


admin at arkansassoftball

Jan 8, 2009, 10:53 AM

Post #8 of 10 (2236 views)
Permalink
Re: VPNC connects but no traffic [In reply to]

Hmm so any suggestions on how to resolve the issue. We are using NAT UDP

-----Original Message-----
From: vpnc-devel-bounces [at] unix-ag
[mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of Joerg Mayer
Sent: Thursday, January 08, 2009 11:39 AM
To: vpnc-devel [at] unix-ag
Subject: Re: [vpnc-devel] VPNC connects but no traffic

On Sun, Jan 04, 2009 at 10:13:52PM -0600, info [at] arkansassoftball wrote:
> I connect routing IS working correctly. I can do ICMP trace and packets
are reaching the ASA on the remote network and the server is replying to
ping. I am getting encaps and decaps on ASA; however, am not getting the
unencrypted data on the client PC.

...
> From ASA
> #pkts encaps: 10, #pkts encrypt: 10, #pkts digest: 10
> #pkts decaps: 57, #pkts decrypt: 57, #pkts verify: 57
...
> #send errors: 0, #recv errors: 0

As the trace is missing the ISAKMP stuff, I'm not sure whether cisco-udp nat
traversal is being used or native ESP encapsulation is used. Either way:
Somewhere between ASA --> PC someone drops the ESP packets (either in native
form or in cisco-udp encapsulated form).

ciao
Joerg
--
Joerg Mayer <jmayer [at] loplof>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
_______________________________________________
vpnc-devel mailing list
vpnc-devel [at] unix-ag
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/

_______________________________________________
vpnc-devel mailing list
vpnc-devel [at] unix-ag
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/


jmvpnc at loplof

Jan 8, 2009, 4:56 PM

Post #9 of 10 (2196 views)
Permalink
Re: VPNC connects but no traffic [In reply to]

On Thu, Jan 08, 2009 at 12:53:10PM -0600, admin [at] arkansassoftball wrote:
> Hmm so any suggestions on how to resolve the issue. We are using NAT UDP

1) make sure that it is really used - you can enable it, but if the
concentrator doesn't enable it, it won't be used.
2) find out the UDP port used for cisco-udp (either by turning on debugs,
asking the admins or using a network analyzer like Wireshark).
3) try to find out whether there's a firewall blocking that UDP port
somewhere between your pc and the pix.

ciao
Joerg
--
Joerg Mayer <jmayer [at] loplof>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
_______________________________________________
vpnc-devel mailing list
vpnc-devel [at] unix-ag
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/


Gary.Davis at sorc

Jan 18, 2009, 2:40 PM

Post #10 of 10 (2149 views)
Permalink
Re: VPNC connects but no traffic [In reply to]

I finally got this to VPN to work. Look at the route print below. I was
trying to connect to my desktop at work at 10.243.37.56. There is no
route to that IP in the table that goes through the VPN.



I tried to add a route for 10.243.0.0 with mask 255.255.0.0 but it wound
up with the wrong interface selected. So my second option was to force
all 10.*.*.* traffic through the VPN and that worked. To do this, I
changed the Internal Netmask from the value returned from the Cisco VPN
(255.255.254.0) to 255.0.0.0. So now, this statement:



> netsh interface ip set address "Tap" static 10.243.56.75 255.255.254.0



Became this:



> netsh interface ip set address "Tap" static 10.243.56.75 255.0.0.0



The route print now looks like this:



========================================================================
===

Active Routes:

Network Destination Netmask Gateway Interface
Metric

0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.240
40

10.0.0.0 255.0.0.0 On-link 10.243.57.222
286

10.243.57.222 255.255.255.255 On-link 10.243.57.222
286

10.255.255.255 255.255.255.255 On-link 10.243.57.222
286

12.0.173.37 255.255.255.255 192.168.0.1 192.168.0.240
41

127.0.0.0 255.0.0.0 On-link 127.0.0.1
306

127.0.0.1 255.255.255.255 On-link 127.0.0.1
306

127.255.255.255 255.255.255.255 On-link 127.0.0.1
306

192.168.0.0 255.255.255.0 On-link 192.168.0.240
296

192.168.0.240 255.255.255.255 On-link 192.168.0.240
296

192.168.0.255 255.255.255.255 On-link 192.168.0.240
296

224.0.0.0 240.0.0.0 On-link 127.0.0.1
306

224.0.0.0 240.0.0.0 On-link 192.168.0.240
296

224.0.0.0 240.0.0.0 On-link 10.243.57.222
286

255.255.255.255 255.255.255.255 On-link 127.0.0.1
306

255.255.255.255 255.255.255.255 On-link 192.168.0.240
296

255.255.255.255 255.255.255.255 On-link 10.243.57.222
286

========================================================================
===



There are two ways to override the Cisco-supplied mask
("INTERNAL_IP4_NETMASK"). Pick one:



1. Modify vpnc-script-win.js (2nd line below added):

var ip4Mask = env("INTERNAL_IP4_NETMASK");

ip4Mask = "255.0.0.0"; // Override incorrect mask for my use



2. Modify vpnc-script (2nd line below added):

#! /bin/sh

export INTERNAL_IP4_NETMASK=255.0.0.0

cscript `cygpath -w /etc/vpnc/vpnc-script-win.js`



This worked for my environment but yours will probably require some
different tweaking.



I tried removing the no-detach option to allow the vpnc service to run
in the background but that did not work. It would be nice if this
worked.



I do have another question, however. Is there a way to establish the
connection before the Vista logon so the I get the domain login script
to run? The Cisco VPN Client has this option (SBL or Start Before
Logon).



Thanks,

Gary Davis



From: vpnc-devel-bounces [at] unix-ag
[mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of Gary Davis
Sent: Friday, January 02, 2009 4:01 PM
To: 'vpnc list to send bug reports and discussions with developers'
Subject: Re: [vpnc-devel] VPNC connects but no traffice



I have been trying for a couple weeks to get this working without
success, though I think I am close.



I have downloaded Cygwin (plus libgcrypt, make, perl and gcc), vpnc
0.5.3, openvpn 2.1.rc15 (installing only the Tap selection).



I compiled vpnc; edited the vpnc-script-win.js file to fix the
recognition of the default gateway (for Vista and Win Server 2008, see
below). I created the vpnc.conf file based on my Cisco pcf file and ran
make install.



I renamed the network connection from openvpn to be "Tap".



I then started the Cygwin terminal by running as admin and typed vpnc
(some numbers have been altered for security).



$ vpnc

> route print 0.0.0.0

Default Gateway :192.168.0.1

VPN Gateway: 12.0.173.37

Internal Address: 10.243.56.75

Internal Netmask: 255.255.254.0

Interface: "Tap"

Configuring "Tap" interface...

> netsh interface ip set address "Tap" static 10.243.56.75 255.255.254.0

> route add 12.0.173.37 mask 255.255.255.255 192.168.0.1

> netsh interface ip add wins "Tap" 10.243.32.72 index=1

> netsh interface ip add wins "Tap" 10.243.32.113 index=2

> netsh interface ip add dns "Tap" 10.243.32.25 index=1

> netsh interface ip add dns "Tap" 10.243.32.26 index=2

done.

Configuring networks:

Gateway did not provide network configuration.

Route configuration done.

VPNC started in foreground...



The lines below starting with ">" are from an echo I added to the run
function as shown below (also note the replaced line in
getDefaultGateway():





function run(cmd)

{

echo("> " + cmd);

return (ws.Exec(cmd).StdOut.ReadAll());

}



function getDefaultGateway()

{

if (run("route print 0.0.0.0").match(/0\.0\.0\.0 *0\.0\.0\.0 *([^
]*)/)) {

return (RegExp.$1);

}

return ("");

}



This is output from route print after the vpnc was set up:



========================================================================
===

Active Routes:

Network Destination Netmask Gateway Interface
Metric

0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2
10

10.243.56.0 255.255.254.0 On-link 10.243.56.75
286

10.243.56.75 255.255.255.255 On-link 10.243.56.75
286

10.243.57.255 255.255.255.255 On-link 10.243.56.75
286

12.0.173.37 255.255.255.255 192.168.0.1 192.168.0.2
11

127.0.0.0 255.0.0.0 On-link 127.0.0.1
306

127.0.0.1 255.255.255.255 On-link 127.0.0.1
306

127.255.255.255 255.255.255.255 On-link 127.0.0.1
306

192.168.0.0 255.255.255.0 On-link 192.168.0.2
266

192.168.0.2 255.255.255.255 On-link 192.168.0.2
266

192.168.0.255 255.255.255.255 On-link 192.168.0.2
266

224.0.0.0 240.0.0.0 On-link 127.0.0.1
306

224.0.0.0 240.0.0.0 On-link 192.168.0.2
266

224.0.0.0 240.0.0.0 On-link 10.243.56.75
286

255.255.255.255 255.255.255.255 On-link 127.0.0.1
306

255.255.255.255 255.255.255.255 On-link 192.168.0.2
266

255.255.255.255 255.255.255.255 On-link 10.243.56.75
286

========================================================================
===

Persistent Routes:

None



Ipconfig /all (Why no Default Gateway?? Does it need a Primary DNS
Suffix??):



Windows IP Configuration



Host Name . . . . . . . . . . . . : Server

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Tap:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : TAP-Win32 Adapter V9

Physical Address. . . . . . . . . : 00-FF-68-3C-63-DB

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . :
fe80::c8a5:b17a:30b4:9b17%25(Preferred)

IPv4 Address. . . . . . . . . . . : 10.243.56.75(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.254.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 10.243.32.25

10.243.32.26

Primary WINS Server . . . . . . . : 10.243.32.72

Secondary WINS Server . . . . . . : 10.243.32.113

NetBIOS over Tcpip. . . . . . . . : Enabled



My vpnc.conf



## generated by pcf2vpnc

IPSec ID TunnelGroup

IPSec gateway 12.0.173.37

IPSec secret [decrypted secret]



Xauth username gary

Domain ABCFL

IKE Authmode psk

Xauth password [password]

Interface name Tap

Interface mode tap

Local Port 0

No detach



The properties of the network connections for the Tap interface have
Status showing as Unidentified network, Device Name as Tap-Win32 Adapter
V9 and Connectivity as Access to Local only, though I have also seen
Limited connectivity.



This home network is connected through a Trendnet router and cable modem
to Comcast.



Everything looks set up pretty much OK but I get no connectivity to the
servers at the other side of the VPN.



I have tried this on two Vista-64 systems and one Win Server 2008
(32-bit) system all with the same problem.



Thanks,

Gary



From: vpnc-devel-bounces [at] unix-ag
[mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of
info [at] arkansassoftball
Sent: Friday, January 02, 2009 9:22 AM
To: 'vpnc list to send bug reports and discussions with developers'
Subject: Re: [vpnc-devel] VPNC connects but no traffice





When I do a route print the routes appear correct.

IE

10.x.x.x mask 255.0.0.0 via 192.168.x.x (tap interface).



I know traffic is routing through tap because I can do an extended ping
when I disconnect the interface I get "hardware error" instead of
request time out on a few packets. The hardware error is when the TAP

interface gets disconnected.



From: vpnc-devel-bounces [at] unix-ag
[mailto:vpnc-devel-bounces [at] unix-ag] On Behalf Of Nick
Sent: Wednesday, December 31, 2008 6:51 PM
To: vpnc-devel [at] unix-ag
Subject: Re: [vpnc-devel] VPNC connects but no traffice



I am experiencing a similar problem. I'm sure it's just not routes
being setup correctly. I need all of my traffic to go through TAP
interface.

vpnc devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.