See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.
Course Of The Month
6 days, 2 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Block VLan access
Posted on 2013-01-08
Hi,
I want to block access to a 10.x.x.x network from a 172.16.x.x vlan and not sure of the best way to do this. I was thinking of using extended access lists and simply applying those to the vlan but was wondering if there were any better suggestions which might make this more easier.
I want to block access to a 10.x.x.x network from a 172.16.x.x vlan and not sure of the best way to do this. I was thinking of using extended access lists and simply applying those to the vlan but was wondering if there were any better suggestions which might make this more easier.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
I have given some example for this... please understand the same.
===============
ip access-list extended BAN_VLAN_20
permit tcp 10.10.20.0 0.0.0.255 established
deny tcp 10.10.20.0 0.0.0.255 any
permit ip any any
!
interface Vlan100
description SVI_VLAN100
ip address 10.10.100.254 255.255.255.0
ip access-group BAN_VLAN_20 out
!
The above would block the 10.10.20.0 network from initiating access to the 10.10.100.0 network via TCP protocols such as Telnet or SSH. However, if 10.10.100.0 network initiated the connection then with the "permit tcp 10.10.20.0 0.0.0.255 established" added the return traffic from the 10.10.20.0 network would be allowed. This will allow the 10.10.100.0 network, your management Vlan, to access the 10.10.20.0 network hosts via TCP protocols, such as the Telnet and SSH for management.
========================
===============
ip access-list extended BAN_VLAN_20
permit tcp 10.10.20.0 0.0.0.255 established
deny tcp 10.10.20.0 0.0.0.255 any
permit ip any any
!
interface Vlan100
description SVI_VLAN100
ip address 10.10.100.254 255.255.255.0
ip access-group BAN_VLAN_20 out
!
The above would block the 10.10.20.0 network from initiating access to the 10.10.100.0 network via TCP protocols such as Telnet or SSH. However, if 10.10.100.0 network initiated the connection then with the "permit tcp 10.10.20.0 0.0.0.255 established" added the return traffic from the 10.10.20.0 network would be allowed. This will allow the 10.10.100.0 network, your management Vlan, to access the 10.10.20.0 network hosts via TCP protocols, such as the Telnet and SSH for management.
========================
Hi,
Here is one good documnet to learn more on vlan access map, vlan acl..you can go thru it if time permits you.
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/vacl.pdf
Here is one good documnet to learn more on vlan access map, vlan acl..you can go thru it if time permits you.
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/vacl.pdf
For a small number of VLAN's that need to be isolated, ACL's are the best option. For a large number of VLAN's, where managing a lot of ACL's would become difficult, you can use private VLAN's.
These articles from Cisco explain private VLAN's
http://www.cisco.com/en/US/tech/tk389/tk814/tk840/tsd_technology_support_sub-protocol_home.html
http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a008013565f.shtml
These articles from Cisco explain private VLAN's
http://www.cisco.com/en/US/tech/tk389/tk814/tk840/tsd_technology_support_sub-protocol_home.html
http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a008013565f.shtml
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
Use of TCL script on Cisco devices:
- create file and merge it with running configuration to apply configuration changes
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses
Course of the Month6 days, 2 hours left to enroll
707 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.