- Test - lists.nanog.org

pd table vs 6296
by Randy Bush 22 Sep '17

22 Sep '17

say i want to use pd to a fairly large aggregation. the router has to hold the pd table. it sees some routers have limited table size, e.g. 1k. so what's a poor boy to do? the classic ipv4 solution would be 6296 <the horror!>. are folk doing pd scaling? how? randy

2 1

Vodafone Global Carrier Services: Contact to Abuse/Fraud Department?
by Benoit Panizzon 22 Sep '17

22 Sep '17

Hello I'm trying to reach somebody from Vodafone Global Carrier Services, regarding abusive calls originating from their network (probably transit from some other TSP). Their IC team do not consider them self in charge of abuse cases. The Vodafone UK fraud teams declares itself only responsible if I am a Vodafone end customer. If somebody has a contact or works @ Vodafone Global Carrier Services, could you please contact me off list? Kind regards -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Puerto Rico just lost internet?
by Javier J 22 Sep '17

22 Sep '17

Any info would help.

7 13

Hughesnet IPv6
by Patrick Shoemaker 21 Sep '17

21 Sep '17

Are there any HughesNet network engineers on here who could either contact me off list to answer some questions about the IPv6 implementation on the Gen5 platform? Standard support mechanisms are not very useful here. Thanks, Patrick Shoemaker

1 0

Bell Canada (AS 577) and NTT (AS 2914) routing
by Scott Larson 21 Sep '17

21 Sep '17

I'm looking for a contact at Bell to look at a routing/traffic issue we've been seeing since at least 5pm PDT yesterday. One of our uplinks is via NTT and after correlating with their NOC, it appears traffic passing through that link ends up dying inside the Bell network. -- *[image: userimage]Scott Larson[image: los angeles] <https://www.google.com/maps/place/4216+Glencoe+Ave,+Marina+Del+Rey,+CA+9029…>Lead Systems Administrator[image: wdlogo] <https://www.wiredrive.com/> [image: linkedin] <https://www.linkedin.com/company/wiredrive> [image: facebook] <https://www.twitter.com/wiredrive> [image: twitter] <https://www.facebook.com/wiredrive> [image: instagram] <https://www.instagram.com/wiredrive>T 310 823 8238 <310%20823%208238%20x1106> | M 310 904 8818 <310%20904%208818>*

2 1

RE: AS PATH limits
by Jakob Heitz (jheitz) 21 Sep '17

21 Sep '17

The consequence of keeping a route with a long AS_PATH is that it uses a little more memory. Also, if you send it on, you will add one ASN and may exceed the maximum BGP message size and not be able to send it. Even that is no reason to drop the incoming route. The consequence of dropping the route is that someone loses connectivity because you dropped it. The need for limiting AS_PATH length stemmed from this incident: https://dyn.com/blog/the-flap-heard-around-the-world/ This bug has long been fixed, so it should not happen again. However, if you want to be extra cautious, because unpatched routers may still be out there, then 200 should not drop any normal route. Just keep an eye on what you are dropping Thanks, Jakob Date: Tue, 19 Sep 2017 13:33:03 +0000 From: craig washington <craigwashington01(a)hotmail.com> To: "nanog(a)nanog.org" <nanog(a)nanog.org> Subject: AS PATH limits Message-ID: <SN1PR0701MB206268455259CC64FC0D8ED7A8600(a)SN1PR0701MB2062.namprd07.prod.outlook.com> Content-Type: text/plain; charset="iso-8859-1" Hello world. I was wondering and forgive me if this discussions has already taken place. How many AS PATHS are too many? Meaning how do we determine how many to filter on transit links or public peering links? Thanks in advance

1 0

Has Level3 done away with traceroute??
by Van Dyk, Donovan 21 Sep '17

21 Sep '17

Hello All, Recently I was troubleshooting a network event for a client of our who resides on the Level3 network. While trying to verify the path, I noticed I am no longer able to traceroute through the Level3 network. The funny thing is this is not just isolated to the /32. It appears to be that the entire 4.0.0.0/9 network is no longer able to traceroute through. Everything dies on their edge network. This appears to be isolated to traceroute. I have check this in NA and EU. My carrier contacted Level3 who pretty much stated that they can’t provide anything. I have checked multiple looking glasses and other online tools and none of them make it. Even Level3 looking glass drops the packets. Does anyone know anything about this? I’m pretty sure this is the first time we are seeing this. Random 4.0.0.0/9 address. NTT looking glass Tracing the route to 4.35.230.7 1 * ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 3 msec 1 msec 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * TATA looking glass traceroute to 4.7.6.4 (4.7.6.4), 30 hops max, 52 byte packets 1 if-ae-14-3.tcore2.FNM-Frankfurt.as6453.net (195.219.87.89) 2.056 ms if-ae-6-2.tcore1.FR0-Frankfurt.as6453.net (195.219.50.173) 1.253 ms 1.177 ms MPLS Label=616998 CoS=0 TTL=1 S=1 2 195.219.50.50 (195.219.50.50) 1.214 ms 1.247 ms 1.535 ms 3 195.219.50.50 (195.219.50.50) 1.144 ms * 2.246 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * Telia looking glass traceroute to 4.7.6.4 (4.7.6.4), 30 hops max, 52 byte packets 1 if-ae-14-3.tcore2.FNM-Frankfurt.as6453.net (195.219.87.89) 2.056 ms if-ae-6-2.tcore1.FR0-Frankfurt.as6453.net (195.219.50.173) 1.253 ms 1.177 ms MPLS Label=616998 CoS=0 TTL=1 S=1 2 195.219.50.50 (195.219.50.50) 1.214 ms 1.247 ms 1.535 ms 3 195.219.50.50 (195.219.50.50) 1.144 ms * 2.246 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * Level3 looking glass Traceroute results from Atlanta, GA to 4.200.65.42(dialup-4.200.65.42.Dial1.LosAngeles1) 1 0.0.0.0 * * * 2 0.0.0.0 * * * 3 0.0.0.0 * * * 4 0.0.0.0 * * * 5 0.0.0.0 * * * 6 0.0.0.0 * * * 7 0.0.0.0 * * * 8 0.0.0.0 * * * 9 0.0.0.0 * * * 10 0.0.0.0 * * * 11 0.0.0.0 * * * -- Donovan Van Dyk SOC Network Engineer Fort Lauderdale, FL USA [cid:image001.png@01D332DA.F4DD00A0] The information contained in this electronic mail transmission and its attachments may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient (or an individual responsible for delivery of the message to such person), you are strictly prohibited from copying, disseminating or distributing this communication. If you have received this communication in error, please notify the sender immediately and destroy all electronic, paper or other versions.

5 4

Re: IOS new versions and network load
by Jean-Francois Mezei 21 Sep '17

21 Sep '17

On 2017-09-17 19:37, Eduardo Schoedler wrote: > Server is an app now, any MacOS can have it running. But do carriers/ISPs really want to deal with a rack unfriendly Mac Mini or iMac at a carrier hotel? If the Server App could run on Linux, or if OS-X could boot on standard servers, perhaps, it it seems to be a very bad fit in carrier/enterprise environments. > Implementation will be a little tricky, because you need your > customers to look a record in your domain. I've tried reading some about it. The cache server app registers with Apple its existence and the IP address ranges it serves When a client wants to download new IOS version, Apple checked and finds that the client's IP is served by the caching server whose "local" IP is a.b.c.d (akaL the inside NAT IP address). Tells client to get version of software from that IP address. The DNS TXT records are used by the Caching Server to get the list of IP blocks it can serve. (not needed in the target small office environments where everyone is on same subnet and the caching server can tell the apple serves the one subnet it seves).

18 31

Drop cable
by ahmed.dalaali＠hrins.net 21 Sep '17

21 Sep '17

Hello, I would like to buy drop cable 6 core, I am already buying from China, but the quality sometimes is bad so anyone who deals with good companies there can share their contact with me? Regards,

3 2

Hurricane Maria: Dominica complete communication outage 12 hours
by Sean Donelan 21 Sep '17

21 Sep '17

Its very unusual to loose all communications with a country for almost 12 hours in 2017. During Hurricane Maria, essentially all communications were cut with the Commonwealth of Dominica at about September 19, 2017 at 4:00am local time. It took nearly 12 hours to re-establish any communications with officials on the island via radio. There has been some unofficial communications with ham radio operators, assumed to be on the island. All power, wireline, internet and cell service appears to still be out. Its unclear how much is due to general damage which will take a while to repair or specific points which could be repaired quickly. There are some VSAT links in Dominica, but I didn't get responses from the ones I tried. Initial aerial fly-overs by CDEMA/RSS, a joint disaster agency by 6 participating countries in the Eastern Caribbean, saw 70%-80% damage to buildings, the hospital and other infrastructure. The Barbados Coast Guard is sailing tonight towards Dominica trying to re-establish better communications for relief efforts. Additional relief personnel are due to be sent in the morning, during daylight hours.

2 2