Cisco VPN connection gets disconnected immediately after established.

Question

Level 1

0 points

Cisco VPN connection gets disconnected immediately after established.

I think SL's Cisco VPN connection is even not as good as iPhone. Since iPhone 2.0 added Cisco VPN capability, I've been using it. But in SL, the connection gets disconnected after it gets the IP from the VPN.

Anyone saw the same issue?

Below are the messages saw in Console.app:

8/29/09 3:38:18 PM configd[13] event_callback: Address added. previous interface setting (name: en1, address: 192.168.0.138), current interface setting (name: utun0, family: 1001, address: 10.13.32.20, subnet: 255.0.0.0, destination: 10.13.32.20).
8/29/09 3:38:18 PM kernel utun ctlconnect: creating interface utun0
8/29/09 3:38:18 PM configd[13] network configuration changed.
8/29/09 3:38:18 PM racoon[5918] IKE Packet: receive success. (Information message).
8/29/09 3:38:18 PM configd[13] SCNC Controller: service ending_verifyprimaryservice, waiting for PrimaryService. status = 1
8/29/09 3:38:18 PM configd[13]
8/29/09 3:38:18 PM kernel SIOCPROTODETACH_IN6: utun0 error=6
8/29/09 3:38:18 PM configd[13] network configuration changed.
8/29/09 3:38:18 PM configd[13] SCNC Controller: ipv4 statechanged, done waiting for ServiceID.

Message was edited by: oldhu

MBP, Mac OS X (10.6)

Posted on Aug 29, 2009 12:43 AM

Reply

Answer 1

gilcelli

Level 1

10 points

Aug 29, 2009 3:04 AM in response to oldhu

Could it be that your CISCO VPN Transport mode is in UDP ?
I think Snow Leopard only works with TCP Transport mode.

Please see here:
http://discussions.apple.com/thread.jspa?threadID=2131308&tstart=15

We shoud send feedback to Apple:
http://www.apple.com/feedback/macosx.html

Reply

Answer 2

oldhu Author

Level 1

0 points

Aug 29, 2009 5:47 AM in response to gilcelli

No, my VPN supports TCP and UDP both. You can see that the connection has been established and the IP has been assigned before it got disconnected.

Reply

Answer 3

Aug 29, 2009 8:11 PM in response to oldhu

The same thing happens to me since I upgraded. I use Cisco SERA 4.0 and I make the connection and it immediately drops.

Reply

Answer 4

Sep 3, 2009 5:24 PM in response to Ira Parker

Add me to the "me too" list.

09-09-03 8:20:19 PM racoon[779] Connecting.
09-09-03 8:20:19 PM racoon[779] IKE Packet: transmit success. (Initiator, Aggressive-Mode message 1).
09-09-03 8:20:20 PM racoon[779] IKEv1 Phase1 AUTH: success. (Initiator, Aggressive-Mode Message 2).
09-09-03 8:20:20 PM racoon[779] IKE Packet: receive success. (Initiator, Aggressive-Mode message 2).
09-09-03 8:20:20 PM racoon[779] IKEv1 Phase1 Initiator: success. (Initiator, Aggressive-Mode).
09-09-03 8:20:20 PM racoon[779] IKE Packet: transmit success. (Initiator, Aggressive-Mode message 3).
09-09-03 8:20:24 PM racoon[779] IKE Packet: transmit success. (Mode-Config message).
09-09-03 8:20:24 PM racoon[779] IKEv1 XAUTH: success. (XAUTH Status is OK).
09-09-03 8:20:24 PM racoon[779] IKE Packet: transmit success. (Mode-Config message).
09-09-03 8:20:24 PM racoon[779] IKEv1 Config: retransmited. (Mode-Config retransmit).
09-09-03 8:20:24 PM racoon[779] IKE Packet: receive success. (MODE-Config).
09-09-03 8:20:24 PM racoon[779] IKE Packet: transmit success. (Initiator, Quick-Mode message 1).
09-09-03 8:20:24 PM configd[13] event_callback: Address added. previous interface setting (name: en1, address: 192.168.1.199), current interface setting (name: utun0, family: 1001, address: 192.168.15.45, subnet: 255.255.255.0, destination: 192.168.15.45).
09-09-03 8:20:24 PM kernel utun ctlconnect: creating interface utun0
09-09-03 8:20:24 PM configd[13] network configuration changed.
09-09-03 8:20:24 PM racoon[779] IKE Packet: receive success. (Information message).
09-09-03 8:20:24 PM racoon[779] IKE Packet: receive success. (Information message).
09-09-03 8:20:25 PM kernel SIOCPROTODETACH_IN6: utun0 error=6
09-09-03 8:20:25 PM configd[13] network configuration changed.

Oh well, hopefully the cisco software itself still works.

Reply

Answer 5

Zoc06

Level 1

5 points

Sep 5, 2009 5:05 AM in response to oldhu

Same problem for me...

But in my case, we DO use UDP encapsulation. It's a pity the SL Cisco VPN client does not support UDP encapsulation, because it will prevent using Cisco VPN when using your computer behind a NAT device, which is often the case nowadays...

Reply