nanog mailing list archives
Re: Winstar says there is no TCP/BGP vulnerability
From: Deepak Jain <deepak () ai net>
Date: Thu, 22 Apr 2004 16:34:34 -0400
You can add a RPF-flavored filter like:Make core-facing network interfaces drop or not route the /30 or /24 your peering interface is on. Many NAP fabrics IPs are blackholed at borders like they should be.
Or you could move your peers to 10.x.x.x addresses and NOT route them inside your network, or have them destined to your blackhole community..
Better still. Just have all of your border routers announce the specpfic address blocks you have peers or directly connected interfaces on with your blackhole community. The routers with directly connected interfaces shouldn't mind the exported route and the routers that receive it shouldn't be routing it anyway.
Deepak Jain AiNET James wrote:
anti spoofing filtering won't help you with your ebgp peer if the packet is spoofed to your peer's address and hits the peering interface. try adding GTSM with anti-spoofing. makes it far harder.. -J On Thu, Apr 22, 2004 at 12:14:55AM -0700, Alexei Roudnev wrote:If they make proper anty-spoofiing filtering, no need in MD5.Perhaps we are all making too much of this... It appears that Winstar feels that there is no need for MD5 authentication of peering sessions. One of our customers has just had the following response from Winstar following a request to implement MD5 on their OC3 connection to Winstar. My first suggestion is to locate another upstream provider (they have 3 already). However, perhaps someone from Winstar would care to help us all understand what the alternative solution is to securing the session via MD5? I would *love* an alternative to the 5 days of work we've just gone through.-----Original Message----- From: Justin Crawford - NMCW Engineer [mailto:jcrawford () winstar net] Sent: Tuesday, April 20, 2004 11:13 AM To: xxxxxx Subject: Re: *****SPAM***** MD5 implimentation on BGP xxxxx, Winstar does not currently run MD5 authentication with our peers. Thanks Justin Thank you for your time and business Justin Crawford Winstar NMCW Ph: 206-xxx.xxxxHas anyone else run in to this with Winstar? -- Rodney Joffe CenterGate Research Group, LLC. http://www.centergate.com "Technology so advanced, even we don't understand it!"(SM)
Current thread:
- Re: Winstar says there is no TCP/BGP vulnerability, (continued)
- Re: Winstar says there is no TCP/BGP vulnerability E.B. Dreger (Apr 21)
- Re: Winstar says there is no TCP/BGP vulnerability Pekka Savola (Apr 21)
- Re: Winstar says there is no TCP/BGP vulnerability E.B. Dreger (Apr 21)
- Re: Winstar says there is no TCP/BGP vulnerability Joe Rhett (Apr 28)
- Re: Winstar says there is no TCP/BGP vulnerability Rodney Joffe (Apr 28)
- Re: Winstar says there is no TCP/BGP vulnerability Kevin Oberman (Apr 28)
- Re: Winstar says there is no TCP/BGP vulnerability Rodney Joffe (Apr 28)
- Re: Winstar says there is no TCP/BGP vulnerability James (Apr 22)
- Re: Winstar says there is no TCP/BGP vulnerability Deepak Jain (Apr 22)
- Re: Winstar says there is no TCP/BGP vulnerability James (Apr 22)
- Re: Winstar says there is no TCP/BGP vulnerability Dan Hollis (Apr 22)
- Re: Winstar says there is no TCP/BGP vulnerability Daniel Senie (Apr 22)
- Re: Winstar says there is no TCP/BGP vulnerability Christopher L. Morrow (Apr 22)
- Re: Winstar says there is no TCP/BGP vulnerability Patrick W . Gilmore (Apr 22)
- Re: Winstar says there is no TCP/BGP vulnerability Patrick W . Gilmore (Apr 20)
- Re: Winstar says there is no TCP/BGP vulnerability Rob Thomas (Apr 20)
- Re: Winstar says there is no TCP/BGP vulnerability Patrick W . Gilmore (Apr 20)