Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 342
  • Last Modified:

I need help building ACLs to control traffic between VLANs ...

Hello all,

I'm completely new to building ACLs on a Catalyst switch.  That said, I have experience doing so on the PIX platform so I have some understanding of concepts, etc.

Here is what I'm trying to do:
There are two VLANs in questions -
the first can be considered the "main" vlan (id = 2, subnet 192.168.50.x) where all the clients and some servers live.
the second can be considered the "web" vlan (id = 3, subnet 192.168.51.x) where all our web servers live.

Right now, since IP Routing is enabled on the switch, these two VLANs can talk to each other.  I need to be able to limit this like so:

No one from the Main vlan should be able to talk to anyone in the Web vlan unless it's FTP or RDP.
No one from the Web vlan should be able to talk to anyone in Main vlan except our DB server on port 1433 only.

Does that make sense?  Many thanks for any help you folks can provide ...
0
ustda
Asked:
ustda
  • 2
  • 2
1 Solution
 
mabutterfieldCommented:
Something similar to this should work.  (check for typo's, and apply access-list numbers as you like)

access list 100 permit tcp 192.168.50.0 0.0.0.255 192.168.51.0 0.0.0.255 eq 20
access list 100 permit tcp 192.168.50.0 0.0.0.255 192.168.51.0 0.0.0.255 eq 21
access list 100 permit tcp 192.168.50.0 0.0.0.255 192.168.51.0 0.0.0.255 eq 3389
access list 100 deny ip 192.168.50.0 0.0.0.255 192.168.51.0 0.0.0.255
access list 100 permit ip any any



access list 101 permit tcp 192.168.51.0 0.0.0.255 192.168.50.0 0.0.0.255 eq 1433
access list 101 deny ip 192.168.51.0 0.0.0.255 192.168.50.0 0.0.0.255
access list 101 permit ip any any



int vlan1
access-group 100 in

int vlan 2
access-group 101 in

0
 
ustdaAuthor Commented:
This is great, thanks mabutterfield!  One question though - how come you end each list with the permit ip any any statment?

Given that it's below the deny statement, nothing would ever get that far, right?
0
 
mabutterfieldCommented:
access list 100 line:

1 permit internal to web ftp
2 permit internal to web ftp
3 permit internal to web rdp
4 prevents all other traffic to web network FROM internal
5 allow all other traffic (outbound to internet, etc)

access list 101 line:

1 allow web to access SQL
2 prevent web from accessing internal
3 allow web outbound to internet / rest of world

you could also add (before the deny lines)
access list 100 permit icmp 192.168.50.0 0.0.0.255 192.168.51.0 0.0.0.255
which would allow icmp (ping) traffic.

You could also tighten down the acls more by restricting them to hosts.  I would recommend changing access list 101 line 1 to:

access list 101 permit tcp 192.168.51.0 0.0.0.255 host <ip of SQL server> eq 1433

This would prevent the web server from accessing database servers that it's not authorized for.




0
 
ustdaAuthor Commented:
This is perfect - thank's a million mabutterfield, it all makes sense.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now