ACLs for switches

CISCO 3750 12.2(25) SEE2
Cisco 2950  12.1.(22) EA2

We codevelop software with teams from other companies and they come to our site to do this. With these companies we have setup Lan to Lan tunnels. So when they come we allow them to connect to our Guest network. Then they VPN into their companies and connect to a particular host on our end. It does not seem the best way to me for them to loop around like that because of our security restrictions.

I was thinking about letting them connect to our company LAN then configure ACLs in a switch, apply them  to specific ports  and allow them access only to an specific host on port 80 and 443.

If it makes any difference I will throw these 2 scenarios in:

1- destination host and guest users connected physically to ports in the same switch

2- destination host  and guest users connected in different switches uplinked  with switches in between . I wonder it if is needed one set of ACLs on both switches or does it matter?

Is this possible, please provide an example of how it would like in the configuration

Thanks for your help

JAR
JohnRamzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don JohnstonInstructorCommented:
Will the source and destination devices be on the same VLAN?

If not, then a routed ACL will be what you need.

If they are on the same VLAN, you will need to use a VLAN ACL (VACL).

0
JohnRamzAuthor Commented:
donjohnston

They are on the same VLAN (native VLAN 1). How do I do it? Would you provide sort of a template?

Thanks

0
Don JohnstonInstructorCommented:
The following VACL will allow devices 192.168.1.16-31 to access the server at 192.168.1.8 for web, smtp and pop3. Those 15 devices can also ping everything. No other traffic from those devices is permitted.

However, all traffic from other addresses is permitted.


ip access-list extended guest-allowed
 permit tcp 192.168.1.16 0.0.0.15 host 192.168.1.8 eq 80
 permit tcp 192.168.1.16 0.0.0.15 host 192.168.1.8 eq 25
 permit tcp 192.168.1.16 0.0.0.15 host 192.168.1.8 eq 110
 permit icmp 192.168.1.16 0.0.0.15 any
ip access-list extended guest-denied
 permit ip 192.168.1.16 0.0.0.15 any
!
vlan access-map outsiders 10
 match ip address guest-allowed
 action forward
vlan access-map outsiders 20
 match ip address guest-denied
 action drop
vlan access-map outsiders 30
 action permit
!
vlan filter outsiders vlan-list 99

Open in new window

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Become a Certified Penetration Testing Engineer

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

JohnRamzAuthor Commented:
donjohnston

Thanks for your reply.very insightful

 I am thinking that creating a separate VLAN would work better for this and I would not have to assign them IP addresses manually. I already have a a separate VLAN with a DHCP server that hands out IP addresses on that subnet.  I know very little about ACLs, so I appreciate if you post another config with the scenario I just suggested, You mentioned in your first post routed ACLs, those might come into play here I guess.

Also would this work on the 3750?

Thanks

0
Don JohnstonInstructorCommented:
Yes. If the devices are on different VLAN's, you would create traditional ACLs and apply them to the VLAN interface.

And yes, you can do this on a 3750.
0
JohnRamzAuthor Commented:
donjohnston:

I was waiting for you config template for the last scenario but I got to it and solved the issue doing it this way:

! Created a VLAn

interface Vlan700
ip address 192.168.1.254 255.255.255.0

! Created the access list to allow them access to a host and the Internet

ip access-list extended GUEST_ACCESS
permit tcp 192.168.1.0 0.0.0.255 host 10.10.6.1 eq www
permit udp 192.168.5.0 0.0.0.255 any eq 53
deny ip 192.168.1.0 0.0.0.255 10.0.0.0 0.255.255.255
permit tcp 192.168.1.0 0.0.0.255 any eq 443
permit tcp 192.168.1.0 0.0.0.255 any eq 80

!Applied it to the VLAN 700 interface

ip access-group GUEST_ACCESS in

Thanks for your guidance anyway
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.