02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

To create an ingress ACLs, use <strong>the</strong> ip access-group command (Figure 233) in <strong>the</strong> EXEC privilege mode.<br />

This example also shows applying <strong>the</strong> ACL, applying rules to <strong>the</strong> newly created access group, and viewing<br />

<strong>the</strong> access list:<br />

Figure 233 Creating an Ingress ACL<br />

<strong>Force10</strong>(conf)#interface gige 0/0<br />

<strong>Force10</strong>(conf-if-gige0/0)#ip access-group abcd in<br />

<strong>Force10</strong>(conf-if-gige0/0)#show config<br />

!<br />

gige<strong>the</strong>rnet 0/0<br />

no ip address<br />

ip access-group abcd in<br />

no shutdown<br />

<strong>Force10</strong>(conf-if-gige0/0)#end<br />

<strong>Force10</strong>#configure terminal<br />

<strong>Force10</strong>(conf)#ip access-list extended abcd<br />

<strong>Force10</strong>(config-ext-nacl)#permit tcp any any<br />

<strong>Force10</strong>(config-ext-nacl)#deny icmp any any<br />

<strong>Force10</strong>(config-ext-nacl)#permit 1.1.1.2<br />

<strong>Force10</strong>(config-ext-nacl)#end<br />

<strong>Force10</strong>#show ip accounting access-list<br />

!<br />

Extended Ingress IP access list abcd on gige<strong>the</strong>rnet 0/0<br />

seq 5 permit tcp any any<br />

seq 10 deny icmp any any<br />

permit 1.1.1.2<br />

Configuring Egress ACLs<br />

Layer 2 and Layer 3 ACLs are supported on plat<strong>for</strong>m e<br />

Use <strong>the</strong> “in” keyword<br />

to specify ingress.<br />

Begin applying rules<br />

to <strong>the</strong> ACL named<br />

“abcd.”<br />

View <strong>the</strong> access-list.<br />

Egress ACLs are applied to line cards and affect <strong>the</strong> traffic leaving <strong>the</strong> system. Configuring egress ACLs<br />

onto physical interfaces protects <strong>the</strong> system infrustructure from attack—malicious and incidental—by<br />

explictly allowing only authorized traffic.These system-wide ACLs eliminate <strong>the</strong> need to apply ACLs onto<br />

each interface and achieves <strong>the</strong> same results. By localizing target traffic, it is a simpler implementation.<br />

Packets originated from <strong>the</strong> system, are not filtered by egress ACLs. This means if you initiate a ping<br />

session from <strong>the</strong> system, and apply an egress ACL to block this type of traffic on <strong>the</strong> interface, <strong>the</strong> ACL<br />

does not affect that ping traffic.<br />

An egress ACL is used when users would like to restrict egress traffic. For example, when a DOS attack<br />

traffic is isolated to one particular interface, you can apply an egress ACL to block that particular flow<br />

from exiting <strong>the</strong> box, <strong>the</strong>reby protecting downstream devices.<br />

346 IP Access Control Lists, Prefix Lists, and Route-maps

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!