Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > firewall policy mismatch error

Reply
Thread Tools

firewall policy mismatch error

 
 
David Carson
Guest
Posts: n/a
 
      01-29-2004
I am trying to connect to a VPN using Cisco's VPN client, 4.0.3.B on
Linux. I am getting the error message in the Subject: line.

What does this mean? I have tried running the client with and without
iptables running on my home system. When I have iptables running, I
can poke holes for UDP 500 and 10000, explicitly for my IP and the
Cisco device's IP, both directions, and get the Cisco to respond to my
client. However, it still gives the policy mismatch error.

What kind of information should I be asking of the sysadmins? I can
capture a log and post it here if it would help. What level of
logging would be useful?

Thanks,
David

P.S. Please post your answers here if possible, rather than responding
to me directly.
 
Reply With Quote
 
 
 
 
Walter Roberson
Guest
Posts: n/a
 
      01-29-2004
In article < >,
David Carson <> wrote:
:I am trying to connect to a VPN using Cisco's VPN client, 4.0.3.B on
:Linux. I am getting the error message in the Subject: line.

What's the endpoint?


:What does this mean?

Your VPN client could not agree on a transform set and 'group'
with the remote end.

: I have tried running the client with and without
:iptables running on my home system. When I have iptables running, I
:can poke holes for UDP 500 and 10000, explicitly for my IP and the
:Cisco device's IP, both directions, and get the Cisco to respond to my
:client. However, it still gives the policy mismatch error.

10000 is not that common. UDP 4500 is what you need if you are trying
to do NAT-T to a remote system that knows about NAT-T. IP protocols
(not udp or tcp ports!) 50 (ESP) and 51 (AH) are what are expected
unless NAT-T is in use.
--
Entropy is the logarithm of probability -- Boltzmann
 
Reply With Quote
 
 
 
 
Rik Bain
Guest
Posts: n/a
 
      01-29-2004
On Thu, 29 Jan 2004 08:39:00 -0600, David Carson wrote:

> I am trying to connect to a VPN using Cisco's VPN client, 4.0.3.B on
> Linux. I am getting the error message in the Subject: line.
>
> What does this mean? I have tried running the client with and without
> iptables running on my home system. When I have iptables running, I can
> poke holes for UDP 500 and 10000, explicitly for my IP and the Cisco
> device's IP, both directions, and get the Cisco to respond to my client.
> However, it still gives the policy mismatch error.
>
> What kind of information should I be asking of the sysadmins? I can
> capture a log and post it here if it would help. What level of logging
> would be useful?
>
> Thanks,
> David
>
> P.S. Please post your answers here if possible, rather than responding
> to me directly.


Do your admins support other users with linux client? I have seen this
in the past on VPN Concentrator, when the group policy requires the
integrated firewall. The linux client software does not have this
functionality, so the error is produced and the connection dropped.

Just one scenario.....

Rik Bain
 
Reply With Quote
 
David Carson
Guest
Posts: n/a
 
      01-31-2004
(Walter Roberson) wrote in message news:<bvbs2r$ejj$>...
> In article < >,
> David Carson <> wrote:
> :I am trying to connect to a VPN using Cisco's VPN client, 4.0.3.B on
> :Linux. I am getting the error message in the Subject: line.
>
> What's the endpoint?
>


A Cisco VPN concentrator 3000.

>
> :What does this mean?
>
> Your VPN client could not agree on a transform set and 'group'
> with the remote end.
>
> : I have tried running the client with and without
> :iptables running on my home system. When I have iptables running, I
> :can poke holes for UDP 500 and 10000, explicitly for my IP and the
> :Cisco device's IP, both directions, and get the Cisco to respond to my
> :client. However, it still gives the policy mismatch error.
>
> 10000 is not that common. UDP 4500 is what you need if you are trying
> to do NAT-T to a remote system that knows about NAT-T. IP protocols
> (not udp or tcp ports!) 50 (ESP) and 51 (AH) are what are expected
> unless NAT-T is in use.


I could not figure out how to specify ESP or AH to iptables. The '-m'
option lists these as valid arguments, but I'm not sure what the whole
command should look like. I keep getting "invalid argument" which is
less than revealing.

Also, I tried connecting to the 3000 without iptables running, to
eliminate the possibility that I was filtering a port I should not
have been. The result is the same. It seems that Rik's response
about requiring an integrated firewall may have some validity. Is
this something that can be changed on the 3000?

Thanks,
David
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Policy map using policy map Geoffrey Sinclair Cisco 1 07-27-2009 09:31 AM
PIX 515 Firewall Policy based Routing? myselfimran Hardware 0 07-03-2007 10:17 AM
Default Domain Policy vs Default Domain Controller Policy Tyler Cobb MCSE 6 10-19-2005 09:36 PM
Default Domain Policy vs. Default Domain Controller Policy Tyler Cobb MCSA 1 10-09-2005 03:42 PM
Microsoft new policy, XP to ship with firewall switched on Howard Johnson NZ Computing 34 11-21-2003 09:57 AM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57