- Test - lists.nanog.org

CIDR cleanup
by John Von Essen 02 Oct '20

02 Oct '20

Sorry if this is slightly off-topic, but I am writing some code for a custom GeoDNS routemap. My starting data set is a raw list of /24 subnets, no prefix aggregation has been done. In other words, its the entire BGP routing table in /24 prefixes - tagged by Geo region. Each region is its own txt file with a dump of /24’s. As a result, these lists are HUGE. I want to aggregate the prefixes as much as possible to create a smaller routemap. So right now it looks like: ... 105.170.72.0/24 brs 105.170.73.0/24 brs 105.170.74.0/24 brs 105.170.75.0/24 brs 105.170.76.0/24 brs 105.170.77.0/24 brs 105.170.78.0/24 brs 105.170.79.0/24 brs 105.170.80.0/24 brs 105.170.81.0/24 brs 105.170.82.0/24 brs 105.170.83.0/24 brs 105.170.84.0/24 brs … and so on. Obviously, 105.170.72.0/24 thru 105.170.79.0/24 can be aggregated to 105.170.72.0/21 and so on. I normally use Perl, does anyone now if there is a perl module that will automatically do this prefix aggregation? I tried to write my code to do this, and its not trivial, just lookinh for a shortcurt. I did a breif glance at some CIDR related Perl cpan modules, and nothing has jumped out. Thanks John

7 8

CIDR string replacement
by Royce Williams 02 Oct '20

02 Oct '20

The recent thread on CIDR aggregation cleanup scripts reminds me that I'm looking for a similarly efficient implementation of a related tool. (I'm gearing up to write my own in Perl, but don't want to reinvent the wheel.) I'd like a fast, Unix-pipeline-ready tool that *replaces* all IPs within that range with a supplied string, using a simple config file as input, and ideally with autodetection of IP-address "word" boundaries, as in: $ cat cidr-replace.cfg 105.170.75.0/24|[Unitel] 209.112.128.0/18|[ACS] 209.165.128.0/18|[GCI] 192.0.2.0/24|[TEST-NET-1] 198.51.100.0/24|[TEST-NET-2] 203.0.113.0/24|[TEST-NET-3] $ echo "source,data1,data2,209.112.130.2,data3" | cidr-replace cidr-replace.cfg source,data1,data2,[ACS],data3 And I know this is kludgy, but it would also be useful for quick-and-dirty work if it had a flag to "append" the string using a known delimiter, as in: $ echo "source,data1,data2,209.112.130.2,data3" | cidr-replace --append ',' cidr-replace.cfg source,data1,data2,209.112.130.2,[ACS],data3 (But I'm happy to hack that last functionality into an existing script.) -- Royce

2 1

Telstra Hijack
by Ross Tajvar 02 Oct '20

02 Oct '20

I'm surprised no one else has mentioned this yet, but Telstra is hijacking a lot of prefixes: https://rpki.cloudflare.com/?view=bgp&prefix=&asn=1221&validState=Invalid Since we don't have RPKI filtering in our network (yet), we are currently filtering everything with the path ".* 4637 1221$". This is of course taking a while...

3 5

Re: CIDR cleanup
by John Kristoff 01 Oct '20

01 Oct '20

On Thu, 1 Oct 2020 13:32:53 +0000 John Von Essen <john(a)essenz.com> wrote: > I tried to write my code to do this, and its not trivial, just > lookinh for a shortcurt. I did a breif glance at some CIDR related > Perl cpan modules, and nothing has jumped out. I wrote the code below some time ago. I've not used it in awhile, but presumably it does what I think it does. I called it compactaddrs.pl. Feed it a list of CIDR blocks via stdin. John #!/usr/bin/perl -T use strict; use warnings; # compactaddrs - aggregate addr blocks use NetAddr::IP qw( Compact ); my @v4blocks; my @v6blocks; while( defined(my $line=<>) ) { chomp $line; if ( $line =~ /:/ ) { push @v6blocks, NetAddr::IP->new($line); } else { push @v4blocks, NetAddr::IP->new($line); } } if ( scalar @v4blocks > 0 ) { print "# IPv4 aggregate prefixes\n"; my @aggregates = Compact(@v4blocks); print 'WHERE'; for my $prefix (@aggregates) { print ' saddr <<= '; print "'$prefix' OR"; # print "$prefix\n"; } } if ( scalar @v6blocks > 0 ) { print " #IPv6 aggregate prefixes\n"; my @aggregates = Compact(@v6blocks); for my $prefix (@aggregates) { print "$prefix\n"; } } print "\n";

1 0

Re: Hand held copper Ethernet testers
by Rich Greenwood 01 Oct '20

01 Oct '20

On Thu, Oct 1, 2020 at 5:00 AM <nanog-request(a)nanog.org> wrote: > My old Test-Um Lanscaper died, and I was curious what people liked these > days. Don’t need throughput testing or anything like that, just basic wire > map testing, cable ID, cable length, PoE voltage, and DHCP client. > We've been happy with the Platinum Tools Net Prowler: https://www.platinumtools.com/products/testers/network-testers/net-prowler-… It does physical cable testing and ID, DHCP and basic IP testing, PoE testing, and LLDP. --Rich -- Rich Greenwood Network Engineer Shasta County Office of Education Office: 530-225-0161 Hotline: 530-225-0279

1 0

Gaming Consoles and IPv4
by Matt Hoppes 01 Oct '20

01 Oct '20

I know the solution is always “IPv6”, but I’m curious if anyone here knows why gaming consoles are so stupid when it comes to IPv4? We have VoIP and video systems that work fine through multiple layers of PAT and NAT. Why do we still have gaming consoles, in 2020, that can’t find their way through a PAT system with STUN or other methods? It seems like this should be a simple solution, why are we still opening ports or having systems that don’t work?

22 45

Re: CIDR cleanup
by Charles Cloughly 01 Oct '20

01 Oct '20

Not Perl, though this may be useful depending on your environment: https://github.com/rus-cert/compress-cidr The examples are for IPv6, though I use it to consolidate lists of IPv4 in a variety of jobs/scripts without issue. YMMV. From: NANOG on behalf of John Von Essen Sent: Thursday, October 1, 2020 6:32 AM To: NANOG Subject: CIDR cleanup Sorry if this is slightly off-topic, but I am writing some code for a custom GeoDNS routemap. My starting data set is a raw list of /24 subnets, no prefix aggregation has been done. In other words, its the entire BGP routing table in /24 prefixes - tagged by Geo region. Each region is its own txt file with a dump of /24’s. As a result, these lists are HUGE. I want to aggregate the prefixes as much as possible to create a smaller routemap. So right now it looks like: ... 105.170.72.0/24 brs 105.170.73.0/24 brs 105.170.74.0/24 brs 105.170.75.0/24 brs 105.170.76.0/24 brs 105.170.77.0/24 brs 105.170.78.0/24 brs 105.170.79.0/24 brs 105.170.80.0/24 brs 105.170.81.0/24 brs 105.170.82.0/24 brs 105.170.83.0/24 brs 105.170.84.0/24 brs … and so on. Obviously, 105.170.72.0/24 thru 105.170.79.0/24 can be aggregated to 105.170.72.0/21 and so on. I normally use Perl, does anyone now if there is a perl module that will automatically do this prefix aggregation? I tried to write my code to do this, and its not trivial, just lookinh for a shortcurt. I did a breif glance at some CIDR related Perl cpan modules, and nothing has jumped out. Thanks John

1 0

Hand held copper Ethernet testers
by Chris Boyd 01 Oct '20

01 Oct '20

My old Test-Um Lanscaper died, and I was curious what people liked these days. Don’t need throughput testing or anything like that, just basic wire map testing, cable ID, cable length, PoE voltage, and DHCP client. What do y’all like? —Chris

6 6

Hulu Contact
by rob-lists＠bpsnetworks.com 30 Sep '20

30 Sep '20

Can someone from Hulu reach out to me? We are getting several customers complaining about receiving proxy/vpn errors from one of our subnets. Thanks! Robert Haas BPS Networks 573-293-2638

2 1

STIR/SHAKEN: New Rules Promote Caller ID Authentication Across America's Phone Networks
by Sean Donelan 29 Sep '20

29 Sep '20

https://www.fcc.gov/document/fcc-adopts-new-rules-combat-spoofed-robocalls The Federal Communications Commission today adopted new rules to further promote implementation of the STIR/SHAKEN caller ID authentication framework to protect consumers against malicious caller ID spoofing. The new rules make clear the obligations and deadlines for voice service providers regarding caller ID authentication, advance the use of caller ID authentication across the nation’s phone networks, and prohibit voice service providers from adding any line item charges to the bills of consumer or small business customer subscribers for caller ID authentication technology.

1 0