John W Kerns

Multi-disciplined IT engineer. Blogger\Dev at and Insert some disclaimer here

[John W Kerns @packetsar]

@DaryllSwer @Marbell28 @stubarea51 @artofneteng @ehorley I agree with both of you. Memorization of IP addresses should not be as big a thing as it is. Also, the biggest hurdle most operators have to implementing IPv6 is the fear that they cannot read and memorize them.

[John W Kerns @packetsar]

@artofneteng Promises made, promises kept 😄

[The Art of Network Engineering @artofneteng]

🚨 IPv6 Is No Longer Optional 🚨

Still relying on IPv4 and NAT? You’re not alone—but it’s time for a reality check.

In this episode @ehorley @stubarea51 @bgp_mane and @andylapteff tackle the real reasons IPv6 is essential for modern networking:
🔹 Scaling networks without breaking them
🔹 Avoiding the pitfalls of NAT reliance
🔹 Future-proofing your infrastructure

If you’ve been avoiding IPv6, this episode is your wake-up call. Don’t get left behind.

🎧 Listen here
https://t.co/ZndLMLZESQ

#IPv6 #Networking #FutureTech

[John W Kerns @packetsar]

@layer8packet Anybody studying for the CCIE Licensing cert yet?

[John W Kerns @packetsar]

@TracketPacer I’m a network engineer and have been a pollworker for the last several election cycles.

Speaking for my county, our electronic “Ballot Marking Devices” are not connected to the internet.

[John W Kerns @packetsar]

@FrontierCorp when will you begin supporting IPv6 in Southern California? Almost 50% of internet traffic now uses a protocol for which you have no support #IPv6

[John W Kerns @packetsar]

@ccieby30 Networking is about making things **work**.

Cybersecurity is about making things **not work**.

I like making things work

[John W Kerns @packetsar]

@danieldibswe Forwarded. I'd expect an unmanaged switch to ignore the frame data following the source/dest MACs (starting with the Ethertype).

[Daniel Dib @danieldibswe]

I was looking for some information on bonding interfaces in Linux and ran into this fantastic post by @packetsar that both summarizes the options, and introduces us to an interesting troubleshooting scenario with LLDP.

Fantastic work!

https://t.co/IR60LXI9xu

[John W Kerns @packetsar]

@danieldibswe OSPFv2 will require individual IPs to be configured on each interface for option 3, so option 2 would be simpler.

OSPFv3 requires no IPs to be configured at all (used LLA), so option 3 would be simpler

[John W Kerns @packetsar]

@OpentoDebateOrg @ApplePodcasts @YouTube @WNYC @nprdistribution @oren_cass @DavidMMcintosh @nayeema The question is phrased wrong. It should ask: "Is the uniparty's refusal to cut spending fiscally irresponsible?"

[John W Kerns @packetsar]

@danieldibswe Give the host two NICs and point it's default gateway towards an IP on the NIC not being tested. Use only specific routes towards the NIC you are testing.

[John W Kerns @packetsar]

@IPv6_mannen @mikrotik_com Does it include an old disgruntled coworker who keeps trying to turn IPv6 off everywhere?

[John W Kerns @packetsar]

Want to determine the maturity/stability of a networking product? Find out how much of its feature-set has #IPv6 parity with legacy IP.

If it has limited IPv6 support, then it likely has major bugs you will encounter, even if you aren't using IPv6 at all.

[John W Kerns @packetsar]

@danieldibswe Use IPv6 LLA. Then you don’t have to set an address at all.

[John W Kerns @packetsar]

@danieldibswe Should work if you put both of the interfaces in a bridge together

[John W Kerns @packetsar]

@beatmastermatt I honestly haven’t heard an argument against it. I’d be interested to hear a good-faith argument against so I can understand any downsides.

[John W Kerns @packetsar]

@HerrNilsson2 @packetpushers If you can, sanitize the neighbor data and submit it in a Github issue or DM it to me