January 2018 - Test - lists.nanog.org

IPv4 smaller than /24 leasing?
by Filip Hruska 18 Mar '18

18 Mar '18

Hi, I have stumbled upon this site [1] which seems to offer /27 IPv4 leasing. They also claim "All of our IPv4 address space can be used on any network in any location." I thought that the smallest prefix size one could get routed globally is /24? So how does this work? [1] http://www.forked.net/ip-address-leasing/ Thanks -- Filip Hruska Linux System Administrator

16 42

TWC/Charter/Spectrum contact off-list ? (Reverse DNS issue)
by Brandon Applegate 17 Mar '18

17 Mar '18

Hello, I had success with this issue about 2 years ago when some TWC folks contacted me. I don’t know if those folks are still with TWC/Charter here in the end of 2017 - hence posting on NANOG. The tl;dr is IPv6 reverse DNS issues. It was broken, got fixed, and seems to have broken again recently. Thanks in advance. -- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 0641 D285 A36F 533A 73E5 2541 4920 533C C616 703A "For thousands of years men dreamed of pacts with demons. Only now are such things possible."

2 2

Reminer: FCC seeks comments on 2017 hurricane season respons
by Sean Donelan 20 Feb '18

20 Feb '18

Just a reminder, the Federal Communications Committee is still collecting comments on the 2017 hurricane season. https://apps.fcc.gov/edocs_public/attachmatch/DA-17-1180A1.pdf PUBLIC SAFETY AND HOMELAND SECURITY BUREAU SEEKS COMMENT ON RESPONSE EFFORTS UNDERTAKEN DURING 2017 HURRICANE SEASON PS Docket No. 17-344 Comments Due: January 22, 2018 Reply Comments Due: February 21, 2018 The Public Safety and Homeland Security Bureau (PSHSB or Bureau) of the Federal Communications Commission (FCC or Commission) seeks comment on the resiliency of the communications infrastructure, the effectiveness of emergency communications, and government and industry responses to the 2017 hurricane season. [...]

1 1

1/2u 100g Metro-E Aggregation Switch
by Lewis,Mitchell T. 16 Feb '18

16 Feb '18

Anyone know of any alternatives to the Ciena 5170 Service Aggregation Switch? I am looking for something that has 4 100g ports for metro ethernet in a 1/2u form factor. Regards, Mitchell T. Lewis [ mailto:MLewis@TechCompute.Net | MLewis(a)TechCompute.Net ] [ http://linkedin.com/in/mlewiscc ] |203-816-0371 PGP Fingerprint: 79F2A12BAC77827581C734212AFA805732A1394E [ https://pgp.mit.edu/pks/lookup?op=get&search=0x2AFA805732A1394E | Public PGP Key ]

6 11

ticketmaster.com 403 Forbidden
by Manser, Charles J 08 Feb '18

08 Feb '18

List, It seems that browsing to ticketmaster.com or any of the associated IP addresses results in a 403 Forbidden for our customers today. Is anyone else having this issue? If anyone from Ticketmaster could reach out to me off-list, it would be helpful. Charles Manser | Principal Engineer I, Network Security Charles.Manser(a)charter.com E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

15 18

improving signal to noise ratio from centralized network syslogs
by Joe Maimon 31 Jan '18

31 Jan '18

Hey All, Centralized logging is a good thing. However, what happens is that every repetitive, annoying but not (usually) important thing fills up the log with reams of what you are not looking for. Networks are a noisy place and silencing every logged condition is impractical and sometimes undesirable. What I am interested in is an automated zoom-in zoom-out tool to mask the repetition of "normal" events and allow the unusual to stand out. Add to that an ability to identify gaps in the background noise. (The dog that didnt bark) What I am not interested in are solutions based upon preconfigured filters and definitions and built in analysis for supported (prepopulated definitions) platforms, this is all about pattern mining/masking and should be self discoverable. Ideally a command tool to generate static versions of the analysis coupled with a web platform (with zoom +- buttons) for realtime. I made a crude run of it with SLCT, using its generated patterns to grep -v, and that in and of itself was useful, but needs a bit of work. Also, its not quite real time. Any ideas would be greatly appreciated. Joe

8 7

list blockchain
by Randy Bush 29 Jan '18

29 Jan '18

why is no one exploring converting this mailing list to a blockchain? major missed opportunity. </dripping sarcasm> randy

8 8

Leasing /22
by Ryan Gard 27 Jan '18

27 Jan '18

We're on the hunt yet again for an additional /22 to lease, and are wondering what the best options are out there? Our usual suspects that we've reached out to in the past seem to be plum out... Any recommendations? Thanks! -- Ryan Gard

13 20

Anyone using Cogent Ethernet
by Mike Hammett 27 Jan '18

27 Jan '18

I much prefer using WDM transport as opposed to Ethernet\VPLS transport due to it being significantly harder (I try not to say impossible) to oversubscribe. That said, it isn't always available at a decent rate at a given location. Cogent has a reputation (right or wrong) for running things a little hot. Have any of you used Cogent Ethernet\VPLS services? What are you experiences? Offlist is fine if you don't want it public. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

13 20

evil ipv6 bit?
by Baldur Norddahl 26 Jan '18

26 Jan '18

Hello After some apparently unrelated changes, one of my routers stopped routing traffic to a few IPv6 destinations. After a lot of experimentation, including rebooting (did not help), I found this: archive.ubuntu.com: 2001:67c:1360:8001::17 "ping6 vrf internet 2001:67c:1360:8001::17" from the router shell works. ping6/traceroute from a customer connection has the packet dropped by the router. Traceroute gets nothing back at all. 2001:67c:1360:7fff:: is ok. Does not reply to ping because I just made up that address. But I get a valid traceroute all the way to the destination. Anything between 2001:67c:1360:8000:: and 2001:67c:1360:ffff:ffff:ffff:ffff:ffff is dropped. My route table looks like this: albertslund-edge1#show ipv6 forwarding route vrf internet 2001:67c:1360:8001::17 IPv6 Routing Table: Headers: Dest: Destination, Gw: Gateway, Pri: Priority; Codes : K: kernel, I1: isis-l1, SFN: sf-nat64, R: ripng, AF: aftr, B: bgp, D: direct, I2: isis-l2, SLN: sl-nat64, O: ospfv3, D6: dhcp, P: ppp, S: static, N: nd, V: vrrp, A: address, M: multicast, UI: user-ipaddr, GW-FWD: PS-BUSI,GW-UE: PS-USER,LDP-A: LDP-AREA, UN: user-network, US: user-special; Dest Owner Metric Interface Pri Gw 2001:67c:1360::/48 B 0 xgei-0/0/0/6 200 ::ffff:185.24.168.254 ::/0 B 0 xgei-0/0/0/6 200 ::ffff:185.24.168.254 Notice how this is a /48 route and one bit at the /49 level changes how it is routed. That is not right. I tried adding a /128 static route but that does not do anything. The packet is still dropped. I just now discovered this: google.com: 2a00:1450:400e:807::200e That address works fine. But then I changed that one bit in the address: 2a00:1450:400e:8807::200e and voila, the router drops the packet. Now I am stumbled. What could the 49th bit in the destination IPv6 address field in a packet mean to the router, that would make it drop the packet? Some extra information about the network: We are using MPLS with l3vpn (vrf) and l2vpn (vpls). The traffic is qinq tagged before being transported in a l2vpn towards the router in question. The l2vpn does not transport the outer vlan tag. The l2vpn is then terminated on a loopback cable. On the other end of that loopback cable we receive the traffic as ordinary qinq tagged without MPLS tagging. It is on this interface the router apparently drops the packet. It might conceivably also drop the packet on the way out of the l2vpn. I have a similar setup, but instead of a loopback cable, the l2vpn is terminated on another MPLS switch, which then connects to a router of the same model. This setup does not have the problem. The change I introduced was changing from an internal interface called "bvi" to the loopback cable. The bvi interface is a simulated loopback cable construct. We are dropping the bvi interface because it is very buggy. We did not have this problem with the bvi interface however. The hardware is ZTE M6000-S V3.00.20(3.40.1). Thanks, Baldur

4 3