Pete's Packet

Limitless

  • Catagories

  • Global visitors

    free counters
  • RSS CCIE Jobs – Metro NY area

    • Sr. Network Engineer
      Task Management Inc Norwalk, CT
    • Sr. Network Engineer Cisco - Somerset NJ or Jersey City
      Confidential Company Somerset, NJJob description: ...industry knowledge* Excellent communication and interpersonal skills* Excellent customer presentation skills** Cisco Certifications preferred (CCNA, CCNP,CCIE).We are committed to a policy of Equal Employment opportunity and will not discriminate on any legally...
    • Wide Area Network Administrator
    • Architect
      Tekmark Global Solutions LLC New York, NYJob description: ...6) Visio drawings 7) Voice/data convergence 8) Data center design 9) Firewalls/security 10) CCIE Written Roles and Responsibilities: -Provide Network Architectural direction to various client outsourced customer accounts-Works with...

Archive for April 13th, 2009

IPV6 stateless autoconfiguration

Posted by Peter Kurdziel on April 13, 2009

The following is a summary of the steps a device takes when using stateless autoconfiguration:

1. Link-Local Address Generation: The device generates a link-local address. Recall that this is one of the two types of local-use IPv6 addresses. Link-local addresses have “1111 1110 10” for the first ten bits. The generated address uses those ten bits followed by 54 zeroes and then the 64 bit interface identifier. Typically this will be derived from the data link layer (MAC) address as explained in the topic on interface identifiers, or it may be a “token” generated in some other manner.
2. Link-Local Address Uniqueness Test: The node tests to ensure that the address it generated isn’t for some reason already in use on the local network. (This is very unlikely to be an issue if the link-local address came from a MAC address but more likely if it was based on a generated token.) It sends a Neighbor Solicitation message using the Neighbor Discovery (ND) protocol. It then listens for a Neighbor Advertisement in response that indicates that another device is already using its link-local address; if so, either a new address must be generated, or autoconfiguration fails and another method must be employed.
3. Link-Local Address Assignment: Assuming the uniqueness test passes, the device assigns the link-local address to its IP interface. This address can be used for communication on the local network, but not on the wider Internet (since link-local addresses are not routed).
4. Router Contact: The node next attempts to contact a local router for more information on continuing the configuration. This is done either by listening for Router Advertisement messages sent periodically by routers, or by sending a specific Router Solicitation to ask a router for information on what to do next. This process is described in the section on the IPv6 Neighbor Discovery protocol.
5. Router Direction: The router provides direction to the node on how to proceed with the autoconfiguration. It may tell the node that on this network “stateful” autoconfiguration is in use, and tell it the address of a DHCP server to use. Alternately, it will tell the host how to determine its global Internet address.
6. Global Address Configuration: Assuming that stateless autoconfiguration is in use on the network, the host will configure itself with its globally-unique Internet address. This address is generally formed from a network prefix provided to the host by the router, combined with the device’s identifier as generated in the first step.

Posted in IPV6, Real World | Leave a Comment »

Notes from a mock lab I took this weekend

Posted by Peter Kurdziel on April 13, 2009

1. PPPoFR =

 

interface Virtual-Template1
 ip address 1.1.1.1 255.255.255.0
 ppp chap hostname ROUTER1
 ppp chap password 0 CISCO
interface Serial0/0
 encapsulation frame-relay
 frame-relay interface-dlci 201 ppp Virtual-Template1
R1#show ip interface brief | include 1.1.1.1
Virtual-Access1 1.1.1.1 YES TFTP up up
Virtual-Template1 1.1.1.1 YES manual down down

Understanding and Configuring PPP CHAP Authentication

http://www.cisco.com/en/US/tech/tk713/tk507/technologies_tech_note09186a00800b4131.shtml

Troubleshooting PPP (CHAP or PAP) Authentication

http://www.cisco.com/en/US/tech/tk713/tk507/technologies_tech_note09186a00800b4130.shtml

2. One interface has no keepalive and the other does not.
The opposite interface would not come up until I entered "no keepalive" on it.

3. One of my RIP routers was not getting any RIP routes from it's neighbor because I fat fingered ver 2 and it was not in the config. Once I added ver 2 under RIP everything was fine.

4.  RIP: ignored v2 update from bad source = no validate update-source

5.

queue-list 1 protocol ip 3 tcp telnet
queue-list 1 protocol ip 5 tcp smtp
queue-list 1 default 4
queue-list 1 queue 3 byte-count 3000 limit 200
queue-list 1 queue 4 byte-count 15000 limit 40

Posted in Routing & Switching Lab | Leave a Comment »

 
Follow

Get every new post delivered to your Inbox.