On Mon, 17 Jan 2011 20:23:17 -0500 Jeffrey Lyon <jeffrey.l...@blacklotus.net> wrote:
> On Mon, Jan 17, 2011 at 8:21 PM, William Pitcock > <neno...@systeminplace.net> wrote: > > Hi, > > > > On Mon, 17 Jan 2011 19:46:55 -0500 > > Jeffrey Lyon <jeffrey.l...@blacklotus.net> wrote: > > > >> Raymond, > >> > >> I do not take you for a fool, the assignment is legitimately null > >> routed. My traceroutes are dropping at my home ISP. > > > > I call bollocks. It's alive and kicking via BGP here. > > > > edge1.lax01# show ip bgp 208.64.120.197/32 > > BGP routing table entry for 208.64.120.0/24, version 2014041464 > > Paths: (6 available, best #3, table default) > > [...] > > > > And I can reach it from my house. > > > > William > > > > So it's dead on Cox Cable and the L3 Looking Glass but not at your > house? How is that possible? > Because you haven't nullrouted shit. You're just tagging the IP with a specific BGP community and not all networks will respect your tagging. The ones that don't allow the traffic to pass right on through to your network, and due to BGP convergence that there will always be a working route this way. Again, I ask: how hard is it to type "ip route 208.64.120.197 255.255.255.255 Null0"? For someone who is "first and leading in DDoS Protection Solutions" you sure seem to not be able to effectively nullroute, no offense. William
