cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6400
Views
31
Helpful
29
Replies

Firewall blocking traffic between VLANS/subnets

KingPrawns
Beginner
Beginner

Here's the problem we've encountered, was hoping you guys could help me debug what the heck is going on:


In the below diagram, computers on 10.20.1.x cannot ping anything on the 10.20.3.x subnet (Including Firewall B).
However, Firewall A can ping Firewall B and the .3.x server so it's not a VLAN routing problem.

The strange thing is that according to the ASDM Packet trace on Firewall A (Screenshot), packets are allowed to travel freely between the internal pc's and the .3.x subnet servers.

I'm positive the fault lies with Firewall A, but the running config file is way too big to post here so I'll try dig out what looks relevant.

We have the following NAT rule which I would have though was the solution but that doesn't seem to help:

     static (inside,bt_dmz) 10.20.1.0 10.20.1.0 netmask 255.255.255.0

(bt_dmz is the interface on Firewall A that runs through to the 10.20.3.x subnet)

We also have icmp permitted:

     icmp permit 10.20.1.0 255.255.255.0 inside

     icmp permit 10.20.2.0 255.255.255.0 dmz

     icmp permit 10.20.3.0 255.255.255.0 bt_dmz

Access list rule:

     access-list outside_access_in_dmz extended permit icmp any any

If Firewall A can ping Firewall B and the server, it feels like routing between VLANS is ok but why then can I not ping the server on that VLAN from my internal PC? Could there be a conflicting rule?

1 Accepted Solution

Accepted Solutions

Could you please add this:

access-list vlan1_bt_dmz_access_in extended permit icmp any any

this should resolve the icmp issue and check packet-tracer again.

Thanks,

Varun

Thanks,
Varun Rao

View solution in original post

29 Replies 29

varrao
Advocate
Advocate

Hi Wez,

I was answering to your thread but I guess you moved it by then

Well I woudl say take captures and analyse, thats the best thing. Check where the packets are getting dropped. Also you woudl need a nat statement for translating the source traffic On firewall 1, something like this:

nat (inside) 10 10.20.1.0 255.255.255.0

global (dmz) 10 interface

On the firewall 2, you shoudl have the following:

static (inside,dmz) 10.20.1.0 10.20.1.0

I would request you to kindly try it and take captures. On firewall 2 as well you need the access-list going from dmz to inside, so plz make sure.

For captures:

https://supportforums.cisco.com/docs/DOC-17814

Hope this helps.

Thanks,

Varun

Thanks,
Varun Rao