In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!
Solved
Use Access lists on mpls network, but now can't access internet
Posted on 2008-06-11
Ok Here it goes....
I found a network on our mpls link that isn't ours in our routing tables. So I am trying to put access lists on the switches at all our locations. However, when I apply the access lists all the internal networks can talk, but nothing can go out to the internet. I thought that I could put a rule to allow any traffic out but the switch will only allow you to apply an access group in. Besides that I don't know if cisco keeps track of sessions. ie. if a packet is allowed out, is it allow to receive the ack if theres no rule to specifically allow that ip?
Ok so heres what I have setup.
access-list 1 permit 10.10.0.0 0.0.255.255
access-list 1 permit 192.168.0.0 0.0.255.255
access-list 1 permit 172.16.0.0 0.0.255.255
I have tried applying the group on all ports of the switches and just the vlans.
It can traverse the mpls but won't allow you to go out to the internet.
I tried making a rule to allow any traffic and apply it to an interface out but there is no out command.
On the 3750s' I'm running 12.2(40)SE and on the 2960s' I'm running 12.2(25)see3.
Is there some kind of command you need to remember sessions or something?
I found a network on our mpls link that isn't ours in our routing tables. So I am trying to put access lists on the switches at all our locations. However, when I apply the access lists all the internal networks can talk, but nothing can go out to the internet. I thought that I could put a rule to allow any traffic out but the switch will only allow you to apply an access group in. Besides that I don't know if cisco keeps track of sessions. ie. if a packet is allowed out, is it allow to receive the ack if theres no rule to specifically allow that ip?
Ok so heres what I have setup.
access-list 1 permit 10.10.0.0 0.0.255.255
access-list 1 permit 192.168.0.0 0.0.255.255
access-list 1 permit 172.16.0.0 0.0.255.255
I have tried applying the group on all ports of the switches and just the vlans.
It can traverse the mpls but won't allow you to go out to the internet.
I tried making a rule to allow any traffic and apply it to an interface out but there is no out command.
On the 3750s' I'm running 12.2(40)SE and on the 2960s' I'm running 12.2(25)see3.
Is there some kind of command you need to remember sessions or something?
2-
2
4 Comments
OK, first you would need to put an allow any statement in as there is an implicit deny at the bottom of every access list.
Second to block the other networks you would need to put the deny at the TOP of the ACL. It would be more efficient to put it like this:
access-list 1 deny ip [unknown network]
access-list 1 permit ip any any
That will let your networks talk to each other and to the internet. The deny statement will be read and processed for the traffic you don't want and will drop it before it gets to the permit stage.
The "in" part of the command means into the interface, not the network. If you were to put that ACL into your edge interfaces you should be fine.
Second to block the other networks you would need to put the deny at the TOP of the ACL. It would be more efficient to put it like this:
access-list 1 deny ip [unknown network]
access-list 1 permit ip any any
That will let your networks talk to each other and to the internet. The deny statement will be read and processed for the traffic you don't want and will drop it before it gets to the permit stage.
The "in" part of the command means into the interface, not the network. If you were to put that ACL into your edge interfaces you should be fine.
I can see that this would work but if I start putting deny statements in then if another new network happens to pop up and I don't know about it the default would be to allow all traffic. Isn't there a way to do this with a default deny rather then default permit?
No. You need a default to allow any as you do not know to which addresses you will be sending internet traffic. The closest you could probably be come would be:
permit YOUR networks
deny 10.x
deny 192.x
deny 172.x (basically put in deny rules for all PRIVATE subnets)
permit any (to allow access to the internet)
permit YOUR networks
deny 10.x
deny 192.x
deny 172.x (basically put in deny rules for all PRIVATE subnets)
permit any (to allow access to the internet)
Featured Post
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 Already a member? Login.
Getting to know the threat landscape in which DDoS has evolved, and making the right choice to get ourselves geared up to defend against DDoS attacks effectively. Get the necessary preparation works done and focus on Doing the First Things Right.
How does someone stay on the right and legal side of the hacking world?
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data.
But that feeling is fleeting. Attacks these days can happen in many w…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…
Suggested Courses
Course of the Month5 days, 11 hours left to enroll
579 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.