[126322] in North American Network Operators' Group
eBGP TTL matching requirement
daemon@ATHENA.MIT.EDU (Vitto Capabianco)
Tue May 11 13:55:36 2010
Date: Tue, 11 May 2010 13:55:02 -0400
From: Vitto Capabianco <donvittony@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Folks,
Is there a TTL value enforcment on EBGP session establishment? For some
reason I thought that both peers have to have the SAMe value? Is that
true? For example:
default EBGP = TTL = 1 (if one end sends something other than 1 in its OPEN
message, we won't bring up the adjecancy)
multihop EBGP = TTL = 255 (by default) - likewise, if one end sends
something else, adjecancy won't come up
multihop EBGP = TTL = modified hop value - ex. 15 (both ends have to have
it)
I understand that ttl-security and its implications.
Thanks,
Vitto
