The arguments against 0.0.0.0/8

The arguments against using 0.0.0.0/0 have been pretty much quashed by the following:

Allow 0.0.0.0/8 as a valid address rangeThe longstanding prohibition against using 0.0.0.0/8 dates back to two issues with the early internet.

There was an interoperability problem with BSD 4.2 in 1984, fixed in BSD 4.3 in 1986. BSD 4.2 has long since been retired.

Secondly, addresses of the form 0.x.y.z were initially defined only as a source address in an ICMP datagram, indicating “node number x.y.z on this IPv4 network”, by nodes that know their address on their local network, but do not yet know their network prefix, in RFC0792 (page 19). This usage of 0.x.y.z was later repealed in RFC1122 (section 3.2.2.7), because the original ICMP-based mechanism for learning the network prefix was unworkable on many networks such as Ethernet (which have longer addresses that would not fit into the 24 “node number” bits). Modern networks use reverse ARP (RFC0903) or BOOTP (RFC0951) or DHCP (RFC2131) to find their full 32-bit address and CIDR netmask (and other parameters such as default gateways). 0.x.y.z has had 16,777,215 addresses in 0.0.0.0/8 space left unused and reserved for future use, since 1989.

This patch allows for these 16m new IPv4 addresses to appear within a box or on the wire. Layer 2 switches don’t care. 0.0.0.0/32 is still prohibited, of course.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=96125bf9985a&fbclid=IwAR2W03PZN8b7ZzAL1jsvxe0wuI9qOWKpeWdAnMMjvgLGE7x5f48RIaCtYUw

Cambium QOE traffic screenshots

Recently I have been using the QoE solution from Cambium Networks on some networks. This software allows for the prioritization and shaping of traffic on a service provider’s network. We will go into the workings of this in some later posts. Here are some screenshots.

Yes, it is IPv6 aware

Musings of an ISP Engineer part 2

Part 1 can be viewed here

-Always check layer1 first. Your momma told you it’s the simplest things in life.  Most times it is that simple.

-After that check layer 2. If a backhaul or fiber link can’t push data due to no connectivity then the fanciest written config in the world won’t mean a thing.

-Use a password manager. 16 character passwords should be the norm with two-factor authentication to the password manager.

-Make a decision and act on it.  Too many times I see network by committee.  By the time it’s actually implemented the parameters have changed. Do the best you can, with the information you have, in the time you have.

-Have a second and third way into your network

yo dawg i heard you like redundancy so i put redundancy in your redundancy  so you can be redundant while you're redundant! - xzibit-yo-dawg | Meme  Generator

-Get used to reading release notes and scanning forums/mailing lists for bug reports

-Your network probably is not hacked

-Quit spending time trying to navigate your network on your phone’s small screen.  Break down and buy a tablet or break out your laptop. Your phone is for quick assessments using the data you are fed.  It’s too inefficient to make config changes.

32,619 Phone Frustration Stock Photos, Pictures & Royalty-Free Images -  iStock

-This Dilbert comic strip cracks my ass up

Dilbert had it right back in 1995 : r/linuxmasterrace

-Just emphasizing how it’s the simplest things at times

-It’s fine if you know how to program in binary but you don’t need to know the inner workings of hardware for 95% of the job. A racecar driver probably knows about engines but spends 99% of his or her time just driving the car.

-Get to know your sales reps for your hardware. They are the unsung heroes in this industry. a good salesperson picks up tidbits of knowledge and lets their customers know. Things like bad hardware runs, bugs other customers have come across, and the like.

A successful maintenance window is 75% labor and 25% documentation. An unsuccessful one is 75% labor and 25% rolling into backups.

-You only know what you know and that’s okay

-The big companies are just as clueless as you. Sometimes they are worse. They just have more people who know just enough to get by.

-There are work gadgets and fun gadgets. Keep the two separate.

Hilarious Comics With Unexpected Endings By “Wtframecomics” (47 Pics) –  Global Circulate

-That optic you should have replaced when you were cleaning the fiber cable will probably haunt you tomorrow.

Part 3? Maybe…..

Auto mapping your Cisco Network

This content is for Patreon subscribers of the j2 blog. Please consider becoming a Patreon subscriber for as little as $1 a month. This helps to provide higher quality content, more podcasts, and other goodies on this blog.
To view this content, you must be a member of Justin Wilson's Patreon
Already a qualifying Patreon member? Refresh to access this content.

The state of Iowa announces “Dig Once” program

OFFICIAL NOTICE. December 30, 2021. The Office of the Chief Information Officer (“OCIO”) has released the first version of the State of Iowa’s Fiber Optic Network Conduit Installation (“Dig Once”) program. More information regarding this program can be found on the website at https://ocio.iowa.gov/dig-once

The OCIO is leading and coordinating a program to provide for the installation of fiber optic network conduit where such conduit does not exist. To further the program, the OCIO has developed a website to help identify where opportunities may exist to lay or install fiber optic network conduit alongside state-funded construction projects involving trenching, boring, a bridge, a roadway, or opening of the ground, or alongside any state-owned infrastructure.

The Dig Once website provides access to information concerning the Iowa Department of Transportation (“DOT”) five-year state-funded infrastructure projects. The website provides a map of locations where anticipated projects will occur and a form to sign up to receive updates when new projects are identified within locations of interest. Please visit https://ocio.iowa.gov/dig-once to view this information. Questions may be submitted by e-mail to ociogrants@iowa.gov.