On Tue, Oct 25, 2016 at 9:03 PM, Hank Nussbacher
wrote:
> and if that doesn't work try:
> http://bgp.he.net/AS3356#_graph4
> [replace the ASN with the ASN of your choice to see the interconnections.]
>
​Doesn't always work--as it will only show upstream ASNs.
For example, Comcast's backbone AS
According to telnet://route-server.twtelecom.net and
http://lookingglass.level3.net/bgp/lg_bgp_main.php BGP is working as
designed. Your single prepend on one prefix with TWTC causes a slight
preference for LVL3. Add another prepend if you want to further balance
your ingress load away from TWTC.
On Wed, Apr 2, 2014 at 1:24 PM, Blake Dunlap wrote:
> Is this malicious or did someone redistribute all of bgp with bad upstream
> filtering?
>
They perfectly re-advertized all mine. Loos like a huge mistake. And still
ongoing.
Although this was nice to see:
==
On Thu, Jan 16, 2014 at 11:04 AM, John Levine wrote:
> If you're a tiny little network, you can
> use the public DNS servers for the BL lookups, and you can
> FTP the text version of DROP and turn in into firewall
> rules or whatever. That's what I do (hack perl scripts
> available on request.)
1:54pm wingying said:
A quick question, what is the common bandwidth for out-of-band access?
If you administer the metro MPLS for a large city, apparently about
"1,100...modems hidden away in locked filing cabinets in public buildings
around the city." http://weblog.infoworld.com/venezia/ar
5 matches
Mail list logo
