May 2020 - Test - lists.nanog.org

Re: Contact at Ubiquiti Networks?
by Mike Hammett 01 Jun '20

01 Jun '20

That is a big problem. In terms of their UniFi product line, there are no reasonable alternatives. Upper management is the biggest problem. They have severe ADD. A ton of companies have these kinds of issues. They just plain don't hire enough people in the right areas to really excel. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP ----- Original Message ----- From: "Ben P" <bp(a)list-subs.com> To: "Mike Hammett" <nanog(a)ics-il.net> Cc: "j k" <jsklein(a)gmail.com>, "NANOG list" <nanog(a)nanog.org> Sent: Tuesday, May 26, 2020 5:01:36 AM Subject: Re: Contact at Ubiquiti Networks? Agree 1000% with the sentiments expressed by Mike. Unfortunately despite much research I’ve been unable to find a suitable replacement vendor. All the other vendors seem to want to ram cloud-management down your throat which I absolutely do not want. My network, my control, not under the auspices of someone else’s magic cloud. On 25 May 2020, at 21:21, Mike Hammett < nanog(a)ics-il.net > wrote: The company has mostly fallen apart. Their sales are going up, but their responsiveness and customer support have been declining over the last five years. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP ----- Original Message ----- From: "j k" < jsklein(a)gmail.com > To: "NANOG list" < nanog(a)nanog.org > Sent: Monday, May 25, 2020 3:16:36 PM Subject: Contact at Ubiquiti Networks? Does anyone have a good contact at Ubiquity Networks? Finding a pattern I don't like. Joe Klein "inveniet viam, aut faciet" --- Seneca's Hercules Furens (Act II, Scene 1) "I never lose. I either win or learn" - Nelson Mandela

16 24

AS hijacking (Philosophy, rants, GeoMind)
by Justin Wilson (Lists) 01 Jun '20

01 Jun '20

One of the companies I work for recently had an issue with AS 2 (University of Delaware) hijacking a prefix. Due to Origin AS, good upstreams, and the like this has not really affected the traffic to the legit blocks. However, GeoMind picked this up almost immediately it seems. The IP blocks when you go to speedtest.net come back to the university of Delaware. This seems to be the only issue at the moment so we are working through contacting the peers of AS2 and asking them to look into this. We had also contacted University of Delaware. Here is where the philosophy comes into play. The very terse e-mail we received back was basically “As2 gets hijacked a lot and it’s not our problem”. So my question for the NANOG folks. At what point do you say “it’s not your problem” when it involves your ASN? Rant I almost always have issues with GeoMind and others when it comes to IP space. Several of my folks have received allocations from Arin in March. A few are still fighting with geolocation stuff with a few of the providers. So why does GeoMind atomically accept a hijacked prefix as correct? All the right boxes have been ticked. Origin Validiation, registry sets, etc. Happy Friday! Justin Wilson j2sw(a)mtin.net — https://j2sw.com - All things jsw (AS209109) https://blog.j2sw.com - Podcast and Blog

7 7

Curious Cloudflare DNS behavior
by John Sage 31 May '20

31 May '20

FULL DISCLOSURE: this is an end-user issue, but one that might have some operational relevance, particularly if anyone from Cloudflare DNS is on the list EXECUTIVE SUMMARY: twice in six weeks Cloudflare DNS on my new Netgear Orbi cable modem/mesh WiFi hotspot has completely lost track of one (and only one that I know of) prominent US domain: usbank dot com Internet provider: Comcast/Xfinity "Extreme Pro+" Dynamic IP address via Comcast that hasn't changed in six-seven years New Netgear Orbi cable modem, configured with DNS through Cloudflare (1.1.1.1 and 1.0.0.1) Again, twice in 6 weeks Cloudflare DNS seems to loose complete track of usbank dot com as a domain Symptoms: Firefox on Ubuntu Linux returns that little puzzled dinosaur cartoon thing and "We can't seem to find this website right now" BUT ALSO: Each one of ping, traceroute, dig and host returns Host usbank . com not found: 2(SERVFAIL) or some variant thereof Everything else works "just fine" as the saying goes And the Cloudflare DNS drop lasted for days the first time around I can switch over to Google DNS (8.8.8.8 and 8.4.4.8) in the Orbi and immediately fix the problem So. Seems odd that Cloudflare DNS would apparently loose complete track of a major US domain name like usbank dot com Or am I missing something? - John -- John Sage FinchHaven Digital Photography Email: jsage(a)finchhaven.com Web: https://finchhaven.smugmug.com/ Old web: http://www.finchhaven.com/

9 10

Rate-limiting BCOP?
by Bryan Holloway 31 May '20

31 May '20

I'm curious if the community would be willing to share their best-practices and/or recommendations and thoughts on how they handle situations where a customer buys X amount of bandwidth, but the physical link is capable of Y, where Y > X. (Yes, I speak of policy-maps, tx/rx-queues, etc.) For example, it might be arguably common to aggregate customer links Layer 2, and then push them upstream to where they anchor Layer 3. That Layer 2 <-> Layer 3 could be a couple of meters or several kilometers. So, as I see it, my options are: * Rate-limit at the Layer 2 switch for both customer ingress/egress, * Rate-limit at the Layer 3 router upstream, i/e, or * Some combination thereof? E.g.: Rate-limit my traffic towards the customer closer to the core, and rate-limit ingress closer to the edge? I've done all three on some level in my travels, but in the past it's also been oftentimes vendor-centric which hindered a scalable or "templateable" solution. (Some things police in only one direction, or only well in one direction, etc.) In case someone is interested in a tangible example, imagine an Arista switch and an ASR9k router. :) Thoughts?

5 8

Re: RFC6550 (RPL) and RFC6775 (IPv6 Neighbor Discovery for 6LoWPANs)
by Etienne-Victor Depasquale 31 May '20

31 May '20

Pascal, thank you, the draft at https://datatracker.ietf.org/doc/draft-thubert-6man-ipv6-over-wireless/ is very informative. You hit the nail on the head with your suggestion of confusion between the congruence of link and subnet. However, I followed one of the references (RFC4903) in your draft and it does not help that it (RFC4903) points to RFC4291's assertion that: "Currently IPv6 continues the IPv4 model that a subnet prefix is associated with one link" RFC4903 further states that: "clearly, the notion of a multi-link subnet would be a change to the existing IP model.". I confess: your assertion in the draft that: "In Route-Over Multi-link subnets (MLSN) [RFC4903], routers federate the links between nodes that belong to the subnet, the subnet is not on-link and it extends beyond any of the federated links" is news to me. Best regards, Etienne On Sat, May 30, 2020 at 1:39 PM Pascal Thubert (pthubert) < pthubert(a)cisco.com> wrote: > Hello Etienne Victor > > Maybe you’re confusing link and a subnet? > > This is discussed at length here: > > https://datatracker.ietf.org/doc/draft-thubert-6man-ipv6-over-wireless/ > > RPL can route inside a subnet using host routes. This is how a multi link > subnet can be made to work... > > Please let me know if the draft above helped and whether it is clear > enough. The best way for that discussion would be to cc 6MAN. > > Keep safe, > > Pascal > > Le 30 mai 2020 à 10:03, Etienne-Victor Depasquale <edepa(a)ieee.org> a > écrit : > > > Thank you Carsten, and thank you Pacal. Your replies are valuable and > packed with insight. > > I'll wrap up with how I interpret RPL's behaviour in terms of IP hops. > > On one hand, RFC6775 defines a route-over topology as follows: > "A topology where hosts are connected to the 6LBR through the use of > intermediate layer-3 (IP) routing. > Here, hosts are typically multiple IP hops away from a 6LBR. > The route-over topology typically consists of a 6LBR, a set of 6LRs, and > hosts." > If RPL is route-over by definition, then RFC6775 would imply that there > are typically multiple IP hops between a leaf and the border router. > > On the other hand, there at least two contradictions (which I justify > after stating them): > (a) RFC6550 states that "RPL also introduces the capability to bind a > subnet together with a common prefix and to route within that subnet." > (b) Reduction of a DODAG to a single subnet prefix, albeit only only one > parent-child relationship deep, is clearly shown at Contiki-NG's Github > page (deep dive section). > > The hinge on which my understanding revolves is that an IP hop traverses a > router and ***results in a change of prefix of the link on which the packet > travels*** : > > --------<incoming packet; link prefix = p1>------><router> > --------<outgoing packet; link prefix = p2>------> > > With RPL, the "hop" would look like as shown below: > > --------<incoming packet; link prefix = p1>------<router> > --------<outgoing packet; link prefix = p1>------ > > There seems to be a change in the meaning associated with "IP hop". > I guess that I can reconcile both cases through the observation that RPL > actually does apply to a single, NBMA link and therefore the IP prefix > ***is*** the same. > Then again, calling the RPL device involved in the packet forwarding by > the name "router" feels like an uncomfortable stretch. > Don't routers sit at the meeting point of different layer 2 links? > > > Cheers, > > Etienne > > On Fri, May 29, 2020 at 10:39 PM Pascal Thubert (pthubert) < > pthubert(a)cisco.com> wrote: > >> Hello Etienne >> >> You may see ND as the host to * interface for any network and RPL as the >> router to router interface when the network is NBMA. >> >> Some of us cared about the interworking. >> >> Look at the RPL Unaware leaf I-draft and you’ll see that I’m sure. >> >> Keep safe, >> >> Pascal >> >> > Le 29 mai 2020 à 20:28, Carsten Bormann <cabo(a)tzi.org> a écrit : >> > >> > Hi Etienne, >> > >> > I’m also not sure many of the classical network operators assembled in >> NANOG work with 6LoWPANs today, but I still can answer your question. >> > >> >> While trying to build a holistic view of LoWPANs, I'm consulting the >> IETF's informational and standards documents. >> >> >> >> I'm struck by the impression that, despite the significance of >> RFC6775's extension of Neighbor Discovery(ND) to low-power and lossy >> networks (LLNs), >> >> it is largely ignored by RFC6550 (RPL), with little to no reference to >> the ontological plane created in RFC6775's terminology section. >> > >> > Yes, you could say that. >> > >> > ND (Neighbor discovery) describes interfaces between hosts and between >> hosts and routers. >> > 6LoWPAN-ND does not use host-to-host interfaces (different from >> Ethernet, all traffic goes over routers, which RFC 4861 already forsaw in >> the L — on-link — bit, which isn’t set in 6LoWPAN-ND). >> > >> > RFC 6550 was completed at a time when many people who came in from the >> WSN (wireless sensor network) world thought they could get away with a >> network that is wholly composed of routers. >> > Even the “leaf” nodes in the RPL world were participating in the >> routing protocol and therefore didn’t really need a host-router interface. >> There was no separate host-router interface in that world, because there >> were no non-router hosts. >> > >> >> (a) router advertisements and router solicitations are substituted by >> DAG information objects (DIO) and DAG information solicitations (DIS) >> > >> > Right, DIO and DAO are router-to-router messages. If there are no >> hosts (and routers don’t bootstrap themselves as hosts), you don’t need ND. >> > >> >> (b) the terms "mesh-under" and "route-over" (widely cited), defined in >> RFC6775, are absent from RFC6550 >> > >> > RFC6550 is route over by definition. Actually, the term was coined by >> the people working closely with the RPL development; RFC 6775 does >> appropriate it as 6LoWPAN-ND is applicable in either case. >> > >> >> (c) jarringly: RFC6775 describes the route-over topologies as >> multi-IP-hop, while RFC6550 gathers DODAG nodes within the confines of the >> same IPv6 prefix as their border router - no multiple IP hops. >> > >> > I’m not sure where you get this interpretation: RFC 6550 (RPL) is very >> much about IP hops. >> > Maybe you mean the address architecture that was defined explicitly in >> RFC 6775; RFC 6550 does not really say much about addresses. >> > >> > Note that the RPL people have since proceeded to (at least partially) >> embrace the host-router concept from the IP architecture; RFC 8505 is an >> update to RFC 6775 that makes 6LoWPAN-ND more palatable to RPL people. >> > >> > I have CCed Pascal Thubert who, as a co-author to all three RFCs, >> certainly will have another perspective on this. >> > >> > Grüße, Carsten >> > >> > > > -- > Ing. Etienne-Victor Depasquale > Assistant Lecturer > Department of Communications & Computer Engineering > Faculty of Information & Communication Technology > University of Malta > Web. https://www.um.edu.mt/profile/etiennedepasquale > > -- Ing. Etienne-Victor Depasquale Assistant Lecturer Department of Communications & Computer Engineering Faculty of Information & Communication Technology University of Malta Web. https://www.um.edu.mt/profile/etiennedepasquale

1 0

Clueful Domain Name Expert from Network Solutions Needed
by james jones 30 May '20

30 May '20

Greetings, Hope everyone is staying healthy and safe. I am really looking for help from someone clueful at Network Solutions. I am having major issues with transferring a domain away from them. Turns out the primary contact on the account has been the same for over a 15+ years. That person has not been involved with the organization for decade and was never updated. I have been getting the run around from customer service to for 4 months trying to update the primary contact. I have provided all the information that has been requested multiple times . Is there anyone on the list that might be able to help. P.S. Sorry for have to do this here. -James

1 0

Re: RFC6550 (RPL) and RFC6775 (IPv6 Neighbor Discovery for 6LoWPANs)
by Etienne-Victor Depasquale 30 May '20

30 May '20

Thank you Carsten, and thank you Pacal. Your replies are valuable and packed with insight. I'll wrap up with how I interpret RPL's behaviour in terms of IP hops. On one hand, RFC6775 defines a route-over topology as follows: "A topology where hosts are connected to the 6LBR through the use of intermediate layer-3 (IP) routing. Here, hosts are typically multiple IP hops away from a 6LBR. The route-over topology typically consists of a 6LBR, a set of 6LRs, and hosts." If RPL is route-over by definition, then RFC6775 would imply that there are typically multiple IP hops between a leaf and the border router. On the other hand, there at least two contradictions (which I justify after stating them): (a) RFC6550 states that "RPL also introduces the capability to bind a subnet together with a common prefix and to route within that subnet." (b) Reduction of a DODAG to a single subnet prefix, albeit only only one parent-child relationship deep, is clearly shown at Contiki-NG's Github page (deep dive section). The hinge on which my understanding revolves is that an IP hop traverses a router and ***results in a change of prefix of the link on which the packet travels*** : --------<incoming packet; link prefix = p1>------><router> --------<outgoing packet; link prefix = p2>------> With RPL, the "hop" would look like as shown below: --------<incoming packet; link prefix = p1>------<router> --------<outgoing packet; link prefix = p1>------ There seems to be a change in the meaning associated with "IP hop". I guess that I can reconcile both cases through the observation that RPL actually does apply to a single, NBMA link and therefore the IP prefix ***is*** the same. Then again, calling the RPL device involved in the packet forwarding by the name "router" feels like an uncomfortable stretch. Don't routers sit at the meeting point of different layer 2 links? Cheers, Etienne On Fri, May 29, 2020 at 10:39 PM Pascal Thubert (pthubert) < pthubert(a)cisco.com> wrote: > Hello Etienne > > You may see ND as the host to * interface for any network and RPL as the > router to router interface when the network is NBMA. > > Some of us cared about the interworking. > > Look at the RPL Unaware leaf I-draft and you’ll see that I’m sure. > > Keep safe, > > Pascal > > > Le 29 mai 2020 à 20:28, Carsten Bormann <cabo(a)tzi.org> a écrit : > > > > Hi Etienne, > > > > I’m also not sure many of the classical network operators assembled in > NANOG work with 6LoWPANs today, but I still can answer your question. > > > >> While trying to build a holistic view of LoWPANs, I'm consulting the > IETF's informational and standards documents. > >> > >> I'm struck by the impression that, despite the significance of > RFC6775's extension of Neighbor Discovery(ND) to low-power and lossy > networks (LLNs), > >> it is largely ignored by RFC6550 (RPL), with little to no reference to > the ontological plane created in RFC6775's terminology section. > > > > Yes, you could say that. > > > > ND (Neighbor discovery) describes interfaces between hosts and between > hosts and routers. > > 6LoWPAN-ND does not use host-to-host interfaces (different from > Ethernet, all traffic goes over routers, which RFC 4861 already forsaw in > the L — on-link — bit, which isn’t set in 6LoWPAN-ND). > > > > RFC 6550 was completed at a time when many people who came in from the > WSN (wireless sensor network) world thought they could get away with a > network that is wholly composed of routers. > > Even the “leaf” nodes in the RPL world were participating in the routing > protocol and therefore didn’t really need a host-router interface. There > was no separate host-router interface in that world, because there were no > non-router hosts. > > > >> (a) router advertisements and router solicitations are substituted by > DAG information objects (DIO) and DAG information solicitations (DIS) > > > > Right, DIO and DAO are router-to-router messages. If there are no hosts > (and routers don’t bootstrap themselves as hosts), you don’t need ND. > > > >> (b) the terms "mesh-under" and "route-over" (widely cited), defined in > RFC6775, are absent from RFC6550 > > > > RFC6550 is route over by definition. Actually, the term was coined by > the people working closely with the RPL development; RFC 6775 does > appropriate it as 6LoWPAN-ND is applicable in either case. > > > >> (c) jarringly: RFC6775 describes the route-over topologies as > multi-IP-hop, while RFC6550 gathers DODAG nodes within the confines of the > same IPv6 prefix as their border router - no multiple IP hops. > > > > I’m not sure where you get this interpretation: RFC 6550 (RPL) is very > much about IP hops. > > Maybe you mean the address architecture that was defined explicitly in > RFC 6775; RFC 6550 does not really say much about addresses. > > > > Note that the RPL people have since proceeded to (at least partially) > embrace the host-router concept from the IP architecture; RFC 8505 is an > update to RFC 6775 that makes 6LoWPAN-ND more palatable to RPL people. > > > > I have CCed Pascal Thubert who, as a co-author to all three RFCs, > certainly will have another perspective on this. > > > > Grüße, Carsten > > > -- Ing. Etienne-Victor Depasquale Assistant Lecturer Department of Communications & Computer Engineering Faculty of Information & Communication Technology University of Malta Web. https://www.um.edu.mt/profile/etiennedepasquale

1 0

Charter AS20115 Contact
by Jeff Waddell 29 May '20

29 May '20

Could a Charter network engineer reach out off list for an issue we are seeing when trying to reach any Charter customers under the AS20115 We don't peer with (or get transit) directly from AS20115 and traffic seems to be blocked at the border with our transit providers and AS20115 We have tried opening tickets with our transit providers - but that is going no where Thanks Jeff

1 0

Equinix Chicago Traffic Drop 5/29/2020
by Kevin McCormick 29 May '20

29 May '20

Last night between 5:20 am and 6:50 am UTC we noticed a large drop in traffic. Looking at flow data, Google had dropped traffic in same time period. We were wondering if anyone had noticed similar drop in traffic. Thank you, Kevin McCormick

1 0

RFC6550 (RPL) and RFC6775 (IPv6 Neighbor Discovery for 6LoWPANs)
by Etienne-Victor Depasquale 29 May '20

29 May '20

Hello folks, I'm not sure whether this is within scope as it regards LoWPANs ... please chastise freely and ignore if LoWPANs are out of scope. While trying to build a holistic view of LoWPANs, I'm consulting the IETF's informational and standards documents. I'm struck by the impression that, despite the significance of RFC6775's extension of Neighbor Discovery(ND) to low-power and lossy networks (LLNs), it is largely ignored by RFC6550 (RPL), with little to no reference to the ontological plane created in RFC6775's terminology section. For example: (a) router advertisements and router solicitations are substituted by DAG information objects (DIO) and DAG information solicitations (DIS) (b) the terms "mesh-under" and "route-over" (widely cited), defined in RFC6775, are absent from RFC6550 (c) jarringly: RFC6775 describes the route-over topologies as multi-IP-hop, while RFC6550 gathers DODAG nodes within the confines of the same IPv6 prefix as their border router - no multiple IP hops. Can anyone confirm or contradict this impression? Cheers, Etienne -- Ing. Etienne-Victor Depasquale Assistant Lecturer Department of Communications & Computer Engineering Faculty of Information & Communication Technology University of Malta Web. https://www.um.edu.mt/profile/etiennedepasquale

2 1