[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
eBGP TTL matching requirement
- Subject: eBGP TTL matching requirement
- From: patrick at ianai.net (Patrick W. Gilmore)
- Date: Tue, 11 May 2010 14:10:57 -0400
- In-reply-to: <[email protected]>
- References: <[email protected]>
On May 11, 2010, at 1:55 PM, Vitto Capabianco wrote:
> Is there a TTL value enforcment on EBGP session establishment
No.
--
TTFN,
patrick
> 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
>