Skip to main content

TTL-Security and EBGP Multihop difference

TTL-Security

  External BGP neighbor may be up to 2 hops away.
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Connection is ECN Disabled, Mininum incoming TTL 253, Outgoing TTL 255

EBGP Multihop

  External BGP neighbor may be up to 2 hops away.
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Connection is ECN Disabled, Mininum incoming TTL 0, Outgoing TTL 2

One of the good explain can read about TTL-Security at www.packetlife.net.

http://packetlife.net/blog/2009/nov/23/understanding-bgp-ttl-security/

If you want more explain pls go this website.
http://www.cisco.com/c/en/us/td/docs/ios/12_2s/feature/guide/fs_btsh.html#wp1054580

Comments

Popular posts from this blog

Nested Route Reflection Cluster

Figure 1.1 R1 router bgp 65000  bgp cluster-id 10  neighbor 2.2.2.2 remote-as 65000  neighbor 2.2.2.2 update-source Loopback0  neighbor 2.2.2.2 route-reflector-client  neighbor 3.3.3.3 remote-as 65000  neighbor 3.3.3.3 update-source Loopback0  neighbor 3.3.3.3 route-reflector-client R2 router bgp 65000  bgp cluster-id 20  net 22.22.22.0 mask 255.255.255.0  neighbor 1.1.1.1 remote-as 65000  neighbor 1.1.1.1 update-source Loopback0  neighbor 4.4.4.4 remote-as 65000  neighbor 4.4.4.4 update-source Loopback0  neighbor 4.4.4.4 route-reflector-client R3 router bgp 65000  bgp cluster-id 30  net 33.33.33.0 mask 255.255.255.0  neighbor 1.1.1.1 remote-as 65000  neighbor 1.1.1.1 update-source Loopback0  neighbor 5.5.5.5 remote-as 65000  neighbor 5.5.5.5 update-source Loopback0  neighbor 5.5.5.5 route-reflector-client R4 router bgp 65000 ...

OSPF Traffic Types

Three types of traffic may be defined in relation to areas: Intra-area traffic consists of packets that are passed between routers within a single area. Inter-area traffic consists of packets that are passed between routers in different areas. External traffic consists of packets that are passed between a router within the OSPF domain and a router within another routing domain. Area ID 0 (or 0.0.0.0) is reserved for the backbone. The backbone is responsible for summarizing the topologies of each area to every other area. For this reason, all inter-area traffic must pass through the backbone; non-backbone areas cannot exchange packets directly. Ref: Routing TCP/IP volume 1