Question Locked

VPN Tunnel strange issue (aren't they all?)

0 helpful
39 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Have two internet connections at home: a DSL, and cable. Have 2 PIX-501s (one on each end) with a site-2-site IPSEC tunnel. Have both PIX's logging to a Linux machine on the cable end (192.168.1.201) Everything worked great until yesterday, when I started trying to allow outside access to a web server on the Linux box. After agonizing for about 4 hours, I never got that working. But in the process I somewhat broke the VPN connection. It's back up, but now I cannot ping from the DSL-end PIX to anything on the Cable-end. (Even though the tunnel is up). Hosts on that end can ping the cable end just fine; so it has to be in the PIX. But I didn't change anything on that config? The problem with this is that it can't reach the syslog server.

I've checked access-lists on both PIX's - don't see anything being dropped. I don't know how MTU size can suddenly be an issue (especially since pinging between hosts works fine. And the cable-end PIX can ping the other way just fine as well).

Here's what I think are the relevant config entries from each PIX:

DSL:
access-list 101 permit ip 192.168.0.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list NoNat permit IP 192.168.0.0 255.255.255.0 192.168.1.0 255.255.255.0
ip address inside 192.168.0.2 255.255.255.0
global (outside) 1 interface
nat (inside) 0 access-list NoNat
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
sysopt connection permit-ipsec
crypto ipsec transform-set chevelle esp-3des esp-md5-hmac
crypto map transam 1 ipsec-isakmp
crypto map transam 1 match address 101
crypto map transam 1 set peer 70.176.x.x
crypto map transam 1 set transform-set chevelle
crypto map transam interface outside
isakmp enable outside
isakmp key *** address 70.176.x.x netmask 255.255.255.0
isakmp identity address
isakmp policy 1 authenticate pre-share
isakmp policy 1 encryption 3des
isakmp policy 1 hash md5
isakmp policy 1 group 1
isakmp policy 1 lifetime 1000

And for the cable:
access-list outbound deny ip any host 216.163.137.68
access-list outbound permit ip any any
access-list 101 permit ip 192.168.1.0 255.255.255.0 192.168.0.0 255.255.255.0
access-list NoNAT permit ip 192.168.1.0 255.255.255.0 192.168.0.0 255.255.255.0
access-list outside-entry permit tcp any host 192.168.1.201 eq www
access-list outside-entry permit tcp any host 192.168.1.201 eq https
access-list outside-entry permit tcp any host 192.168.1.201 eq ssh
access-list outside-entry permit tcp any host 192.168.1.201 eq ftpaccess-list outbound deny ip any host 216.163.137.68
access-list outbound permit ip any any
access-list 101 permit ip 192.168.1.0 255.255.255.0 192.168.0.0 255.255.255.0
access-list NoNAT permit ip 192.168.1.0 255.255.255.0 192.168.0.0 255.255.255.0
access-list outside-entry permit tcp any host 192.168.1.201 eq www
access-list outside-entry permit tcp any host 192.168.1.201 eq https
access-list outside-entry permit tcp any host 192.168.1.201 eq ssh
access-list outside-entry permit tcp any host 192.168.1.201 eq ftp
ip address inside 192.168.1.199 255.255.255.0
global (outside) 1 interface
nat (inside) 0 access-list NoNAT
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface www 192.168.1.201 www netmask 255.255.255.255 0 0
access-group outside-entry in interface outside
access-group outbound in interface inside
route inside 11.0.0.0 255.0.0.0 192.168.1.200 1
sysopt connection permit-ipsec
crypto ipsec transform-set toyota esp-3des esp-md5-hmac
crypto map bmw 1 ipsec-isakmp
crypto map bmw 1 match address 101
crypto map bmw 1 set peer 75.171.44.40
crypto map bmw 1 set transform-set toyota
crypto map bmw interface outside
isakmp enable outside
isakmp key ******** address 75.171.44.40 netmask 255.255.255.255
isakmp identity address
isakmp policy 1 authentication pre-share
isakmp policy 1 encryption 3des
isakmp policy 1 hash md5
isakmp policy 1 group 1
isakmp policy 1 lifetime 1000

Sorry about the length - hopefully this is enough to provide an idea what is going on. (And if anybody sees why my Linux machine webserver isn't available please let me know what I'm missing there as well!)

Thank you in advance!
-BK

39 replies

by cg it

so what's your first access list that would have a match?

by bk6662

Are you referring to the "Deny" rule on the second (cable) config I posted? But that's for outbound traffic, and it has been there all along. Also if that was the problem wouldn't it affect all hosts trying to ping from the remote LAN? (Followup question since this is a VPN tunnel, is the remote LAN considered inside or outside?)

I will remove that to test, but I didn't think that could be causing this. Of course I may be totally misundersanding your reply!

Thank you,
BK

by bk6662

Removed the "Deny" rule - still can't ping from the PIX to anything on the other end of the tunnel. Please let me know what I am missing.

Thanks!
BK

by cg it

and a sh controllers on the exit interface.

thanks

by bk6662

I'm not sure how to show controllers - here's the show interfacee output of each. Thanks!!

------------------------------------------
PIX2# (Cable):
interface ethernet0 "outside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000b.be94.a529
IP address 70.176.101.4, subnet mask 255.255.248.0
MTU 1500 bytes, BW 10000 Kbit half duplex
525688 packets input, 35271882 bytes, 0 no buffer
Received 505547 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
23093 packets output, 2827768 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 21 deferred
1 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/29)
output queue (curr/max blocks): hardware (0/4) software (0/1)
interface ethernet1 "inside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000b.be94.a52a
IP address 192.168.1.199, subnet mask 255.255.255.0
MTU 1500 bytes, BW 100000 Kbit full duplex
23774 packets input, 3969616 bytes, 0 no buffer
Received 4420 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
17640 packets output, 1684041 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/4)
output queue (curr/max blocks): hardware (1/28) software (0/1)

-----------------------------------------

PIX1# (DSL)

interface ethernet0 "outside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000f.24e9.c57e
IP address 75.171.44.40, subnet mask 255.255.255.255
MTU 1492 bytes, BW 100000 Kbit full duplex
40907 packets input, 13177418 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
47467 packets output, 8125552 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/4)
output queue (curr/max blocks): hardware (0/35) software (0/1)
interface ethernet1 "inside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000f.24e9.c57f
IP address 192.168.0.2, subnet mask 255.255.255.0
MTU 1500 bytes, BW 100000 Kbit full duplex
32419 packets input, 7012923 bytes, 0 no buffer
Received 4294 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
29437 packets output, 11448943 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/65)
output queue (curr/max blocks): hardware (1/4) software (0/1)

by cg it

so you're up on both ends which means the tunnel is established between the 2 PIX firewalls, and you can ping one way but not the other so the interface that you can't ping through is the problem. you mentioned that the cable interface can ping through to the DSL end, but the DSL end can't ping through the cable interface, so that's the interface with the problem, maybe....

and debug info?

Have to ask, did you copy your working running config to a TFTP ? and do a copy run start? if you rebooted and still have the problem, sounds like you did a copy run start without backing up the current run config.

probably not if you asking the question..but had to ask.

by netman1958

If you haven't already done so, reboot both PIXs. After the reboot if the problem persists run the following on both PIXs and post the output:

"sh ipsec sa"

by bk6662

Hi NetMan,

Yes I've rebooted both several times. Below is the output you've requested. Thanks for your assistance!

-Bk
------------------------------------------
PIX1# (DSL PIX)

interface: outside
Crypto map tag: transam, local addr. 75.171.44.40

local ident (addr/mask/prot/port): (192.168.0.0/255.255.255.0/0/0)
remote ident (addr/mask/prot/port): (192.168.1.0/255.255.255.0/0/0)
current_peer: 70.176.101.4:500
PERMIT, flags={origin_is_acl,}
#pkts encaps: 14658, #pkts encrypt: 14658, #pkts digest 14658
#pkts decaps: 14648, #pkts decrypt: 14648, #pkts verify 14648
#pkts compressed: 0, #pkts decompressed: 0
#pkts not compressed: 0, #pkts compr. failed: 0, #pkts decompress failed: 0
#send errors 259, #recv errors 0

local crypto endpt.: 75.171.44.40, remote crypto endpt.: 70.176.101.4
path mtu 1492, ipsec overhead 56, media mtu 1492
current outbound spi: 45b590e9

inbound esp sas:
spi: 0x77a6b304(2007413508)
transform: esp-3des esp-md5-hmac ,
in use settings ={Tunnel, }
slot: 0, conn id: 2, crypto map: transam
sa timing: remaining key lifetime (k/sec): (4607999/24472)
IV size: 8 bytes
replay detection support: Y

inbound ah sas:

inbound pcp sas:

outbound esp sas:
spi: 0x45b590e9(1169527017)
transform: esp-3des esp-md5-hmac ,
in use settings ={Tunnel, }
slot: 0, conn id: 1, crypto map: transam
sa timing: remaining key lifetime (k/sec): (4607999/24409)
IV size: 8 bytes
replay detection support: Y

outbound ah sas:
outbound pcp sas:
-------------------------------------------
Pix2# (Cable PIX)

interface: outside
Crypto map tag: bmw, local addr. 70.176.101.4

local ident (addr/mask/prot/port): (192.168.1.0/255.255.255.0/0/0)
remote ident (addr/mask/prot/port): (192.168.0.0/255.255.255.0/0/0)
current_peer: 75.171.44.40:500
PERMIT, flags={origin_is_acl,}
#pkts encaps: 14648, #pkts encrypt: 14648, #pkts digest 14648
#pkts decaps: 14658, #pkts decrypt: 14658, #pkts verify 14658
#pkts compressed: 0, #pkts decompressed: 0
#pkts not compressed: 0, #pkts compr. failed: 0, #pkts decompress failed: 0
#send errors 0, #recv errors 0

local crypto endpt.: 70.176.101.4, remote crypto endpt.: 75.171.44.40
path mtu 1500, ipsec overhead 56, media mtu 1500
current outbound spi: 77a6b304

inbound esp sas:
spi: 0x45b590e9(1169527017)
transform: esp-3des esp-md5-hmac ,
in use settings ={Tunnel, }
slot: 0, conn id: 2, crypto map: bmw
sa timing: remaining key lifetime (k/sec): (4607999/24266)
IV size: 8 bytes
replay detection support: Y

inbound ah sas:

inbound pcp sas:

outbound esp sas:
spi: 0x77a6b304(2007413508)
transform: esp-3des esp-md5-hmac ,
in use settings ={Tunnel, }
slot: 0, conn id: 1, crypto map: bmw
sa timing: remaining key lifetime (k/sec): (4607999/24239)
IV size: 8 bytes
replay detection support: Y

outbound ah sas:
outbound pcp sas:

by netman1958

Well you do have send errors on the DSL PIX:
#send errors 259, #recv errors 0

Can you post or PM me the complete configs for both PIXs?

by bk6662

Here goes!

PIX1:

: Saved
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password UhOh encrypted
passwd UhOh encrypted
hostname PIX1
domain-name ecc.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list 101 permit ip 192.168.0.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list NoNAT permit ip 192.168.0.0 255.255.255.0 192.168.1.0 255.255.255.0
pager lines 24
logging on
logging timestamp
logging trap informational
logging facility 22
logging host outside 192.168.1.201
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside 192.168.0.2 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.1.12 255.255.255.255 inside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list NoNAT
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
ntp server 198.60.22.240 source outside
http server enable
http 192.168.1.12 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set chevelle esp-3des esp-md5-hmac
crypto map transam 1 ipsec-isakmp
crypto map transam 1 match address 101
crypto map transam 1 set peer 70.176.101.4
crypto map transam 1 set transform-set chevelle
crypto map transam interface outside
isakmp enable outside
isakmp key ******** address 70.176.101.4 netmask 255.255.248.0
isakmp identity address
isakmp policy 1 authentication pre-share
isakmp policy 1 encryption 3des
isakmp policy 1 hash md5
isakmp policy 1 group 1
isakmp policy 1 lifetime 1000
telnet 70.176.101.4 255.255.255.255 outside
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 inside
ssh timeout 5
management-access inside
console timeout 0
vpdn group ISP request dialout pppoe
vpdn group ISP localname krbrian1012@qwest.net
vpdn group ISP ppp authentication pap
vpdn username XYZ@qwest.net password *********
dhcpd address 192.168.0.11-192.168.0.50 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:
: end

--------------------------------------------------------------------

PIX2:

: Saved
:
PIX Version 6.3(5)
interface ethernet0 10baset
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password OhBoy encrypted
passwd OhBoy encrypted
hostname PIX2
domain-name epx.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list outbound permit ip any any
access-list 101 permit ip 192.168.1.0 255.255.255.0 192.168.0.0 255.255.255.0
access-list NoNAT permit ip 192.168.1.0 255.255.255.0 192.168.0.0 255.255.255.0
access-list outside-entry permit tcp any host 192.168.1.201 eq www
access-list outside-entry permit tcp any host 192.168.1.201 eq https
access-list outside-entry permit tcp any host 192.168.1.201 eq ssh
access-list outside-entry permit tcp any host 192.168.1.201 eq ftp
pager lines 24
logging on
logging timestamp
logging trap notifications
logging host inside 192.168.1.201
mtu outside 1500
mtu inside 1500
ip address outside dhcp setroute
ip address inside 192.168.1.199 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.1.16 255.255.255.255 inside
pdm location 216.163.137.68 255.255.255.255 outside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list NoNAT
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface www 192.168.1.201 www netmask 255.255.255.255 0 0
access-group outside-entry in interface outside
access-group outbound in interface inside
route inside 11.0.0.0 255.0.0.0 192.168.1.200 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
ntp server 198.60.22.240 source outside
http server enable
http 192.168.1.26 255.255.255.255 inside
http 192.168.1.201 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set toyota esp-3des esp-md5-hmac
crypto map bmw 1 ipsec-isakmp
crypto map bmw 1 match address 101
crypto map bmw 1 set peer 75.171.44.40
crypto map bmw 1 set transform-set toyota
crypto map bmw interface outside
isakmp enable outside
isakmp key ******** address 75.171.44.40 netmask 255.255.255.255
isakmp identity address
isakmp policy 1 authentication pre-share
isakmp policy 1 encryption 3des
isakmp policy 1 hash md5
isakmp policy 1 group 1
isakmp policy 1 lifetime 1000
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 15
ssh 192.168.1.0 255.255.255.0 inside
ssh timeout 15
management-access inside
console timeout 0
dhcpd address 192.168.1.10-192.168.1.50 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:
: end

by cg it

static (inside,outside) tcp interface www 192.168.1.201 www netmask 255.255.255.255 0 0

netmask 255.255.255.255 is all 1s

by bk6662

I agree with you that it seems a standard subnet mask should go here. But the system won't allow it (I just tried to change it to 255.255.255.0, to test. It wouldn't take it). But it allowed me to go back and put 255.255.255.255. So I'm assuming the PIX must be seeing that as an "exact match"?

by netman1958

I've looked over those configs several times and nothing jumps out at me. Just for the heck of it let's try a debug and see if that leads us anywhere. Try this on both PIXs:
PIX1#term mon
PIX1#debug icmp trace

PIX2#term mon
PIX2#debug icmp trace

Then try your pings and post the output.

by bk6662

Here goes!

PIX1# term1: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40
2: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40
3: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40
4: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40
5: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40
6: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40
7: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40
8: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40

Type help or '?' for a list of available commands.
PIX1# ping 192.168.1.199
9: ICMP echo request (len 32 id 9233 seq 0) 75.171.44.40 > 192.168.1.199
192.168.1.199 NO response received -- 1000ms
10: ICMP echo request (len 32 id 9233 seq 1) 75.171.44.40 > 192.168.1.199
192.168.1.199 NO response received -- 1000ms
11: ICMP echo request (len 32 id 9233 seq 2) 75.171.44.40 > 192.168.1.199
192.168.1.199 NO response received -- 1000ms
PIX1# 12: ICMP unreachable (code 0) 216.160.199.209 > 75.171.44.40

PIX2# ping 192.168.0.2
1: ICMP echo request (len 32 id 9233 seq 0) 70.176.101.4 > 192.168.0.2
2: ICMP echo reply (len 32 id 9233 seq 0) 192.168.0.2 > 70.176.101.4
192.168.0.2 response received -- 70ms
3: ICMP echo request (len 32 id 9233 seq 1) 70.176.101.4 > 192.168.0.2
4: ICMP echo reply (len 32 id 9233 seq 1) 192.168.0.2 > 70.176.101.4
192.168.0.2 response received -- 10ms
5: ICMP echo request (len 32 id 9233 seq 2) 70.176.101.4 > 192.168.0.2
6: ICMP echo reply (len 32 id 9233 seq 2) 192.168.0.2 > 70.176.101.4
192.168.0.2 response received -- 20ms
PIX2#

by netman1958

I see what is happening. The pings are sourcing from the outside interface's IP address. Since the outside interface's IP is not included in access-list 101 or 104, it's not sending the pings through the tunnel.

Are computers on the LAN side of the DSL PIX able to ping hosts on the LAN side of the cable PIX? If so, your tunnels are functioning.

As for the cable PIX being able to ping 192.168.0.2, I wonder if that's the IP address of a device on your ISP's internal network that is replying to the pings?

by bk6662

CG / Netman,

I was looking at the configs I've already posted at your request. I am noticing a discrepancy in the MTU Size on the DSL device. Even though the outside interface is set to 1500, it looks like it is somehow set to 1492. Do you think this could be causing my issues? (NetMan I also sent you a pm responding to your findings - please let me know if it didn't come through).

Please note the following -
From "show interface":
PIX2#
MTU 1500 bytes, BW 10000 Kbit half duplex
PIX1:
MTU 1492 bytes, BW 100000 Kbit full duplex

And from "show crypto sa"
PIX1:
path mtu 1492, ipsec overhead 56, media mtu 1492
PIX2:
path mtu 1500, ipsec overhead 56, media mtu 1500

Please let me know what you think. Thank you!

-BK

by netman1958

I replied to your PM and addressed your issues. I'll summarize that reply here. I don't think the MTU issue is the cause of not being able to ping from the PIX, but they are a performance(speed) consideration as DSL using PPPoE usually requires a smaller MTU and TCP MSS.

by cg it

I'm with netman, the MTU isn't going to cause problems with ping packets. default MTU ethernet v2 spec is 1500 where 1492 is ethernet 802.3 spec. virtually the same and simply means data units.

I'm also with netman that it seems as though the 192.168.1.X subnet isn't allowing return ping packets..so access list problem

side note: no reply means the route to the subnet is known but the host doesn't return the packet. destination unreachable usually means an unknown route to the destination.

by bk6662

I shut down the PIX and tried pinging from an internal host - no go. It doesn't look like there's another device at that address. CG you think it's an access list on the 1.199 PIX? Shouldn't that be obvious if I do a "show access-list" command and look for denied packets? Or are implicit denies not logged?

I do have another observation to throw into the mix. On the DSL end, the PIX is connected to a DSL modem (router). I know that IP address was set to 0.1, which is why I configured the PIX to 0.2. Now I cannot ping or connect to 0.1 (the DSL modem). I KNOW I've connected to that box in the past, when I was setting it up. I'm almost wondering if somebody hacked in and changed the IP on me. If they changed it to 0.2, it would be consistent with NetMan's thoery.

Please let me know if you guys have any other odeas or comments. I greatly appreciate your suggestions!

by cg it

from the PIX and then from the WAN interface, but not from hosts behind the PIX, could be access lists.

I'd copy your running config somewhere but to the startup config, then remove all your access-lists from the running config and start testing the links from both ends. That at least eliminates or confirms that it's the access lists that are causing the problem.

Wiping the startup/running config seems a bit drastic.

you can add the access-lists one at a time and test to find out which one is the culprit.

Also, and can't remember and didn't look, do you have NAT on either end?

by netman1958

This really isn't making any sense. I want you to try another test. Run the following on PIX number 2 (the one that is getting ping replies):
PIX2#traceroute 192.168.0.2
Post the output from that traceroute.

by bk6662

Is there a comparable PIX command I'm not aware of?

Thanks!
BK

by bk6662

Ok I see now. I am running PIX version 6.3. Traceroute was incorporated in version 7.2; I'm not even sure the 501 will run that version. I will check and see, as this would be a very helpful test.

by netman1958

I could have sworn PIX 6.3 supported the traceroute command. Oh well, don't bother about trying to upgrade unless you just want to, we'll try something else. See my reply to your last message.

by bk6662

Ok so I told you I cannot connect to 192.168.0.1 from the local segment, through the DSL PIX. Well get this - I'm connected to the cable PIX now. From that device I AM able to ping 192.168.0.1. Sorry for all these random messages - I'm just hoping one turns out to be an important clue!

by netman1958

Disconnect the DSL cable on the DSL PIX and then from the cable modem try to ping 192.168.0.1 and let me know if the pings still reply.

by bk6662

Sorry NetMan - no go. I've also noticed that the ONLY device I can ping that address from is from the Cable PIX (192.168.1.199). I cannot ping it from other host on the 1.0 network, nor from anything (including the PIX) on the 0.0 network. I'm seriously thinking about doing a write erase and starting from scratch, on the Cable end. Please let me know if you have any other ideas!!

by netman1958

Does that mean the pings from the cable PIX to 192.168.0.1 failed with the DSL cable disconnected but you receive replies with the DSL cable connected?

by bk6662

Sorry reached the max depth on the previous message. You are correct - once I removed the DSL cable I could no longer ping from the Cable PIX. But then I realised "Of course that won't work". By removing that cable I was isolating the DSL LAN from the rest of the world.

As another test on the DSL side I completely bypassed the PIX, and plugged a host directly into the DSL modem. I was then able to ping and connect to 192.168.0.1.

by cg it

you said"

As another test on the DSL side I completely bypassed the PIX, and plugged a host directly into the DSL modem. I was then able to ping and connect to 192.168.0.1"

So, that means that the host directly connected to the DSL line, gets the public address???

I'd say again, take your PIX config for the DSL side and remove the access lists see if it works. If it does, it's access lists.

I'd then add in the access lists, as configured previously one at a time, each time running the ping test.

by netman1958

once and for all. If you don't mind doing this, reconfigure the DSL PIX so that it isn't using the same IP range on the LAN as the DSL modem is using. Maybe use 192.168.2.0 255.255.255.0 for the subnet.
Like this on the DSL PIX:
access-list 101 permit ip 192.168.2.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list NoNAT permit ip 192.168.2.0 255.255.255.0 192.168.1.0 255.255.255.0
ip address inside 192.168.2.2 255.255.255.0
dhcpd address 192.168.2.11-192.168.2.50 inside

And on the Cable PIX:
access-list 101 permit ip 192.168.1.0 255.255.255.0 192.168.2.0 255.255.255.0
access-list NoNAT permit ip 192.168.1.0 255.255.255.0 192.168.2.0 255.255.255.0

by bk6662

Ok - fair enough. I keep thinking it's on the cable end, since that's the one I was playing around with when this whole mess began. But I understand where you are coming from, and I agree that starting there is the best idea. (Unless -dumb question just occurred to me - - what if I instead changed the dsl-modem IP address?)

If I go through all of this and nothing changes, I will look back at the cable-end.

CG concerning access-lists....wouldn't I get some sort of log-entry if packets were being dropped b/c of acc-list issues? Or are implicit denies not logged? Sorry still have a lot to learn!!

Thanks!
BK

by netman1958

" (Unless -dumb question just occurred to me - - what if I instead changed the dsl-modem IP address?)"

That would work also if you can change it and might save time. Good call!

by cg it

to answer your question, yes you ought to get some info on dropped packets if in fact the Pix is filtering.

What gets me is the "what if I changed the address" ... did you or didn't you? ought to know the config and your WAN addressing...

So, hey can't find the problem, then maybe your idea of erasing the config and starting over is the way to go. I dunno, its your rig.

by bk6662

CG,

I realize these questions / suggestions are scattered all over the place. No I haven't changed the IP address yet. NetMan suggested this morning, and I sent the "What if" question as a followup (I won't be able to try it out until this evening). But I haven't done either yet. I appreciate all of the advice you've offered - will be sure to let you guys know what I find.

-Bk

by bk6662

I just turned everything off except for the Cable PIX, and a single host. DSL network, modem, DSL PIX, and all other devices are powered down. I can still ping 0.1 and 0.2, only from the Cable PIX. (not from any hosts). Sorry I missed this yesterday. But what does it mean? There is no possibility that there are devices out there with those addresses. I think it's something in the PIX config? But I don't see anything. Please let me know if you guys have any ideas. Otherwise I will be rebuilding this config from scratch.

Thanks!

by netman1958

Actually there is a possibility that there is a device with a 192.168.0.x address out there. Possibly your cable modem or something on your cable ISP's network. I have a Cisco 831 at home connected to a cable modem. My internal network is a 172.16.1.0 255.255.255.0 subnet and the public IP on the Cisco is 68.185.x.x. There is nothing on my local network in the 192.168.x.x subnet. Here is the output from a ping on my Cisco:
Cisco-831#ping 192.168.100.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/8/24 ms

If I open a web browser on a computer on the LAN and put 192.168.100.1 in the address bar, it opens a configuration page on my cable modem.

I wouldn't rebuild your configs at all. It looks to me like your PIXs and VPNs are working like they are supposed to. I'm going to post a follow-up to this showing some pings and their results from my Cisco 831 across a VPN to my work network that may help clear it up for you.

by bk6662

Thanks again NetMan and CG for all the assistance you've provided. It turns out that this issue started when my cable ISP somehow added ip addresses 0.1 and 0.2 to the internal cable (192.168.1.0) network. NetMan thanks for that tip. I don't know exactly how it works or how it is able to find a route to those devices, but I do know that after I blew away the cable config and started from scratch, I was able to ping those addresses as soon as I made the PIX a DHCP client of the cable router. So all along before when I thought I was pinging the DSL PIX, I was actually pinging those internal devices.

With that being the case, I changed the DSL network to 2.0 instead of 0.0. Then after another hour of still not being able to ping from that PIX I remembered to ping from the inside interface - not the outside interface. I could finally ping my syslog server from the PIX!

Last problem was that my syslog *still* wasn't getting alerts from the DSL PIX. Took me a while to figure out that the new PIX IP address needed to be added as an "Allowable host" on the Linux Syslog.

Finally all is well again. Thanks again for your patience and assistance - I've learned a lot.

-bk

This discussion is closed to new replies.