A late follow-up, just in case this helps anyone else while searching the
archives of this list etc., this turned out to be a pix configuration
issue...
Since we also have an easy vpn on the same pix (for Cisco's software VPN
client), we had to add two extra attributes at the end of the line on
NAT is not in use, the two peers are in direct contact
with each other.
OS version: Cisco PIX Firewall Version 6.3(4)120
PIX model: Hardware: PIX-515E
Regards
Richard
--- Petr Ruzicka <[EMAIL PROTECTED]> wrote:
> two more questions
> - pix version ?
> - is nat in use ?
>
> Petr R.
>
> --- Ri
two more questions
- pix version ?
- is nat in use ?
Petr R.
Hi
Thanks, for your replies. I have some additional information now -
the cisco config (below) - though it still looks quite sensibly configured
(to someone who doent know any cisco commands ;)), and
the errors remain :(
Regards, Richard
--- Erik Carlseen <[EMAIL PROTECTED]> wrote:
> It would
Thanks for the replies here on this list. Using the
debug parameters suggested usefully reduced the
amount of information in the log files.
I've requested the Cisco PIX config information -
hopefully I'll get that from the techs at the other
end of the tunnel I am creating this week.
In my isakmp
Hi, could you get configuration of PIX. Not all of it required, just
isakmp and crypto map stuff.
Do they use xauth ?
Petr R.
On 5/6/05, Richard Green <[EMAIL PROTECTED]> wrote:
> Hi
>
> I've been struggling with this one for a while, and
> would appeciate some advice from someone with more
> ex
Hi
I've been struggling with this one for a while, and
would appeciate some advice from someone with more
experiece that I on creating VPN tunnel between an
OpenBSD (mine) and Cisco PIX (not mine..). Previously
I /did/ test this using OpenBSD to OpenBSD in a test
environment without problems.
Pha
7 matches
Mail list logo
