August 2025 - NANOG - lists.nanog.org

Correctly dealing with bots and scrapers.
by Andrew Latham 25 Mar '26

25 Mar '26

I just had an issue with a web-server where I had to block a /18 of a large scraper. I have some topics I could use some input on. 1. What tools or setups have people found most successful for dealing with bots/scrapers that do not respect robots.txt for example? 2. What tools for response rate limiting deal with bots/scrapers that cycle over a large variety of IPs with the exact same user agent? 3. Has anyone written or found a tool to concentrate IP addresses into networks for IPTABLES or NFT? (60% of IPs for network X in list so add network X and remove individual IP entries.) -- - Andrew "lathama" Latham -

18 33

New c-nsp, j-nsp, a-nsp, etc mailing lists
by Drew Weaver 20 Jan '26

20 Jan '26

I was a big fan of the *-nsp(a)puck.nether.net<mailto:*-nsp@puck.nether.net> mailing lists that now seem to be completely gone without any indication of whether or when they might return. I've been considering just setting up new ones. Please email me off-list if you think this might be useful. Thanks, -Drew

15 25

Hardware question
by Craig Smith 10 Nov '25

10 Nov '25

Hello, Is anyone out there aware of a fail safe switch/router/1U server where upon power failure or watchdog event 2 ports would fail to pass through data, but could also be assigned an IP address and act as a bridge in "normal" mode? The desire is to have an appliance that could perform monitoring and send telemetry in between a customer device and an Internet connection but not create a single point of failure or require multiple ISP handoffs. Best, Craig

14 18

NEC 2026 changes for data/communication wiring
by Sean Donelan 29 Sep '25

29 Sep '25

The 2026 National Electrical Code is ready for publication. The scope of Chapter 8 is changed from all building communication system installations, to only communications wiring outside or at the cable entrance point. Data/Communication system wiring is now in Chapter 7, which means it will be covered by general NEC requirements. For those designing data centers after 2026, many data/communication installation "best practices" will become code requirements. Probably the biggest change will "working clearances" for communications equipment in wiring closets and cabinet door openings in data centers. No more cramming equipment into shared closets or draping cables across the room. After the 2026 NEC is adopted, building code officials will be able to enforce those requirements.

4 7

2025 State of Network Automation Survey - Requesting Your Participation
by Chris Grundemann 23 Sep '25

23 Sep '25

Hey all! It's that time of year again... Survey time. The 2025 State of Network Automation Survey is open!!! No automation experience required - please share with everyone who has edit access on a production network, regardless of how automated that network might be. https://www.surveymonkey.com/r/StateOfNetworkAutomation_2025 For consistency, and ability to track trends, most of the questions are word-for-word repeats from prior years surveys. This year I deleted a few questions that don't seem relevant anymore, and I made a few questions optional, rather than required, in hopes of MANY more responses -- I also built in some logic, so that *folks who have ZERO network automation experience / deployment can still answer the survey easily*, in hopes of more accurate data collection. There are also some new questions, all suggested by the Network Automation Forum community. Finally, you will notice that we (now with NAF backing) moved off of the free Google form to a much sleeker SurveyMonkey survey. w00t Again - we invite anyone and everyone with enable on a production network to complete the survey, and we hope that everyone here will share the survey in other foraa as well - mailing lists, newsletters, social media, discord, slack, reddit, etc, etc. Survey results have been submitted as a talk for NANOG 95 in October. And will be available publically one way or another before the end of the year. Thanks! ~Chris

4 6

So am I just excitable?
by michael brooks - ESC 09 Sep '25

09 Sep '25

I have been watching the "Weekly Global IPv4 Routing Table Report" for a while now, and have been itching to see the *BGP routing table entries examined line* hit 1M. Now, perhaps I am naive, I am assuming that line correlates to the actual number of routing table entries, true? Am I the only one a bit excited to see this? Is this a non-event? michael brooks Network/Systems Administrator IV Adams 12 Five Star Schools michael.brooks(a)adams12.org :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: "flying is learning how to throw yourself at the ground and miss" -- <http://www.adams12.org> -- This is a staff email account managed by Adams 12 Five Star Schools. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender.

10 14

Re: beware: being old sucks
by Randy Bush 05 Sep '25

05 Sep '25

a fellow nanogger wrote: > I've only *just* gotten to the note from a week or more ago. > >> + tftp-server nvram:startup-config <<<<<<====== >> snmp-server community foo 98 >> snmp-server trap-source Vlan1 >> snmp-server location Ashburn VA US > > I, too, got this from a RANCID setup I built a long time ago. > >> and here is the talos report, thanks joe >> >> https://blog.talosintelligence.com/static-tundra/ >> >> set `no vstack` in config. no, that is not the default. > > I'd told the owner that I didn't think he had control of his gear > anymore, but this helped me to convince him to put a new switch in. moving this to nanog because i did not elaborate on a critical point. when you get this, presume the config of this trivial ancient devic has been snatched. did the device have any burned in users, a la username foo privilege 15 password 7 bar and that uid/pass is used on other, presumably more modern, devices, you need to change the passwords everywhere. same for other credentials, snmp, bgpmd5, ... randy

17 47

Google is not turning up any new peering on IXs?
by Will OBrien 04 Sep '25

04 Sep '25

We recently turned up a new IXP and I’m going through the motions of arranging the usual peers, etc. I’m extremely surprised by this one: Public Peering Google no longer accepts new peering requests at internet exchanges (IXPs). However, Google maintains dedicated connectivity to the internet exchanges (IXPs) listed in our PeeringDB entry<https://www.peeringdb.com/asn/15169>. We also maintain existing BGP sessions across internet exchanges where we are connected. For networks who do not meet our PNI requirements Google will serve those networks via indirect paths. I can only presume that someone who doesn’t pay for cross connect fees came up with this plan. This feels short sighted at the least. Considering the benefits of peering, I have to express some dismay at this disservice to the internet in general. Anyone from Google care to explain what appears to be a willful withdrawal of support for the IXP community?

9 9

Genius or Ridiculous?
by Mike Hammett 31 Aug '25

31 Aug '25

My current project is a voice-related project, but how ridiculous would it be to get a line of service from my competitors at my main office for me to do diagnostics from? Internet from Comcast, Frontier, etc. Voice from Frontier, Comcast, AT&T wireless, VZW, and T-Mobile? I'm currently in a situation where I have to engage customers (or the family of employees) to place test calls for me to collect data on because I can't do it any other way. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP

6 8

APRICOT 2026: Call for Volunteers (Programme Committee)
by Mark Tinka 31 Aug '25

31 Aug '25

Hello all. The APRICOT 2026 Organising Committee would like to welcome everyone to join us in Jakarta, Indonesia, from 5th - 12th February 2026. The APRICOT 2026 PC (Programme Committee) is responsible for the solicitation and selection of suitable presentations and tutorial content for the APRICOT 2026 conference (https://2026.apricot.net/) We are now seeking VOLUNTEERS from the community to join the APRICOT 2026 PC to assist with the development of the programme for APRICOT 2026. Eligible PC candidates must have attended recent APRICOT events, be active members of their local NOG (Network Operators Group) in the Asia Pacific region, have broad technical knowledge of Internet operations, and have good familiarity with the format of APRICOT. Having constructive opinions and ideas about how the programme content might be improved is of high value too. PC members are expected to work very actively to solicit content, follow-through with speaker updates and review submissions for technical merit. The PC meets by conference call, weekly in frequency during the three months prior to APRICOT. While participation in the weekly calls is not obligatory, active participation in content reviews is required at all times to help the PC reach consensus. PC members who are unable to fully participate in the programme development will be excused from the PC. If you are interested in joining the PC and meet the above eligibility criteria, please send a brief note to "pc-chairs at apricot.net". The note must include affiliation (if any) and a brief description about why you would make a good addition to the PC. The PC Chairs will accept nominations received by 17:00hrs UTC+8 on Sunday 7th September 2025, and will announce the new PC shortly thereafter. Many thanks! Mark Tinka, Achie Atienza & Mark Duffell APRICOT 2026 Programme Committee Chairs

1 0