Well, think about RST attacks, in which someone bombards a TCP connection with TCP RESET in the hopes of threading a needle and taking it down. It's not the end of the world - BGP restarts - but there is an outage. The simplest way to protect against that (and against having someone with a hijacked IP address connect to your router) is to put mutual authentication on the TCP connection. Having it also at the BGP layer, and having ACLs to be sure you know what's going on, are good things, but TCP MD5, TCP-AO, or IPsec are an awful lot safer.
> On Aug 14, 2018, at 4:28 PM, Grant Taylor via NANOG <nanog@nanog.org> wrote: > > On 08/14/2018 03:38 PM, Randy Bush wrote: >> so we started to wonder if, since we started protecting our bgp >> sessions with md5 (in the 1990s), are there still folk trying to >> attack? > > n00b response here > > I thought using ACLs or otherwise protecting the BGP endpoint was best > practice. Thus it's really hard to even try break an MD5 protected BGP > session if you can't even establish the TCP connection. > > Everything that I've seen or set up had an ACL to only allow the peer(s) to > be able to connect to (from memory) TCP port 179. > > Is there something that I've missed the boat on? > > #learningOpportunity > > > > -- > Grant. . . . > unix || die > -------------------------------------------------------------------------------- The fact that there is a highway to hell and a stairway to heaven is an interesting comment on projected traffic volume...
signature.asc
Description: Message signed with OpenPGP
