Showing posts with label ACL. Show all posts
Showing posts with label ACL. Show all posts

Tuesday, August 13, 2013

Today's stumbling blocks in my memory

These are just a few points I want to reconsider today.  It is best to be clear and particular about them.

One practice exam question I was incorrect in answering was the "host mask" vs. "inverse host mask."  I had incorrectly marked the answer for a host mask in an ACL as 255.255.255.255.  The reality is that a host mask in an ACL is 0.0.0.0 -which means that all bits must match.

From the Cisco website, I summarize:

In an inverse mask, a 0 must be an exact match to be considered for the traffic routing, and a 1 is a "don't care."  ACL equivalents:

  • The source/source-wildcard of 0.0.0.0/255.255.255.255 means "any". (although the source could be any IP address whatsoever - all will still apply)
  • The source/wildcard of 10.1.1.2/0.0.0.0 is the same as "host 10.1.1.2".  

DHCP configuration cheat-sheet
  1. prepare your excluded addresses
  2. Create your pool
  3. Add the network
  4. Add the domain name
  5. Add the default router
  6. Add the DNS servers
As an example:
R1(config)#ip dhcp excluded-address 10.1.1.1
R1(config)#ip dhcp pool MYPOOL
R1(dhcp-config)#network 10.1.1.0 /24

R1(dhcp-config)#domain-name madhouse.local
R1(dhcp-config)#default-router 10.1.1.1
R1(dhcp-config)#dns-server 8.8.8.8 8.8.4.4

Dynamic NAT


I configured a dynamic NAT lab tonight, also.  One of the things I wanted to remind myself was that the NAT statement when configuring dynamic NAT does not require the overload keyword, as this is doing IP-to-IP translation and not port translation (or PAT).

I also looked up what exactly a RIP flash update is.  A flash update is an update that is sent to neighbor routers when a route change takes place.  This occurs in both RIPv1 and RIPv2 - however that is a "triggered update" which is a characteristic of Link-State routing protocols, not distance-vector.  This leaves grey area in my understanding of RIP, but at least I understand it now.

Friday, July 19, 2013

Random items of review regarding Access Control Lists

Just a few things I picked up yesterday that I wanted to jot down before I forget again:

  1. Fast path switching in NAT/PAT is indicated by an asterisk when running a show ip nat translations command.  This has nothing to do with NAT, but indicates that the switching was done based on the initial packet asks for a port and subsequent packets use that same port.
  2. access-group is used in applying ACLs to an interface, access-class is used in applying ACLs to lines
  3. Dynamic Access lists allow a router to create an ACL based on user credentials.
  4. Limit the number of telnet sessions in the line command, such as line vty 1 to limit to a single session
  5. Static NAT allows connections from the outside and are always in the NAT table
  6. Always pay attention to the source and destination in an ACL, especially where ports are concerned - do not limit based on source port, but rather on destination.
  7. Extended ACLs should be placed on the interface nearest the source, whereas standard ACLs should be placed nearest the destination.

More thoughts as they arrive...

Thursday, July 18, 2013

Random ACL thoughts and things I want to remember

Some thoughts on ACLs, as well as some commands to review:

distribute-list <#> [ in | out] - permit or deny routing protocols from adding a network into the routes propagated

Standard ACLs:  1-99, 1300-1999
Extended ACLs:  100-199, 2000-2699

A Cisco router removes the host inverse mask (0.0.0.0) from an ACL when doing a show running-config, because anything without a mask is assumed to be a host.

Apply standard ACLs on the interface closest to the destination.

An empty ACL allows all traffic.

When working on a router or firewall remotely, start with the reload in command to reload the device  autmatically in case an error is made and everyone is locked out.  Then cancel the reload to remove the reload command before the timer is up if everything is working correctly:

reload in 5
reload cancel


When configuring extended ACLs, be cautious about the source port and its placement.  Entering port numbers after the source IP, you only filter that source port.  Leaving source port information off the ACL means to assume all source ports

Best practice is to apply extended ACLs on the interface closest to the source.  This is directly contrary to the best practice for standard ACLs.

(Standard near destination, Extended near source)

Use the established keyword to allow any packets with an ACK or RST through.  This is commonly applied on the Internet interface inbound to allow any sessions initiated from the LAN back through the router.

A named ACL can have a single line deleted without removing the entire ACL.  One major difference is that the named list must be prepended with the ip keyword.

A Cisco router creates entries in a named ACL starting at line number 10 and incrementing by 10.

resequence allows you to move an ACL line from one number to another.

More thoughts as they come to me...