Data link layer

And the network caveat from that same project is the asterisk I mentioned earlier.

Multicast paging only works within the same Layer 2 broadcast domain or across routed segments with IGMP and multicast routing explicitly enabled.

The multicast TTL is set to 1, meaning the packet dies at the first router.

Across VLANs, you need multicast routing or per VLAN paging groups at the switch or router layer.

That's the mechanism to connect packets across the network that Daniel mentioned.

It's not a proprietary box.

It's understanding Layer 2 versus Layer 3 IGMP, snooping, multicast routing, TTL.

The network is the product.

However, personally, I'm not perfectly happy with this construct.

It's the best that you can really do in a classic Layer 2 environment.

Why am I not happy? Because CFMs are being sent out once every 10 minutes or so.

And the fracture of a broadcast domain, let's say by somebody has not configured the VLAN on a switch-to-switch link.

Is there performance enhancements that come with this as well? Are we able to leverage more ports with a single IP address, or is that strictly just one-to-one?

With BGP, absolutely.

With the classical layer 2, the best that you can hope for is LACP.

And LACP has a certain number of caveats, so all of the ports have to be the same link speed.

So Halloween, which is also Bitcoin's 18th birthday, is going to be very eventful.

This episode is sponsored by Orange Rock Layer 2 Labs, Cake Wallet, Sideshift and Brains Hashpower.

And in the chat, you can already start typing numbers for the contest.

Bob has written.

It's a lot more than just the TANC.

Yeah, I remember when that happened, and it was sort of a joke, but the joke became something that people took seriously.

I think that Tether even built their own Layer 2, which was called Polygon, I think, for the purpose of trading Tron on it.

Right.

2026-76658 describes vulnerability in the SSH daemon that likewise allows an unauthenticated remote attacker to take over the host.

Both affect Fabric Composer through version 7.3.3. Workaround, Motherhood, and Apple Pie only expose the CLI, API, and web interfaces on a dedicated Layer 2 segment or VLAN, protect them with firewall policies, and track and log user activities and resource use.

The fix, oh wait, what a surprise, upgrade to 7.3.4 or 7.4.0 or above.

Note, we're only detailing these two CVEs, but there are 50 more for the same product suite this week.

The flaw, discovered during a customer support investigation, affects 10 silicon-1 based switches and could let an attacker gain root privileges remotely.

The vulnerability is exposed through default Layer 2 ports, making it particularly dangerous for improperly configured network infrastructure.

Cisco urges administrators to apply the patches immediately to prevent unauthorized access to their networks.

Serbian activists were targeted with sophisticated spyware, including zero-click Pegasus and Novispy infections, ahead of upcoming elections.

There's also initial support for the Qualcomm Snapdragon X Elite or Snapdragon 10 Elite platform, depending on how you pronounce that.

There's also, and this is cool for me, improvements to NPF, the NetBSD packet firewall, including Layer 2 and user group filtering.

There's also a new microVM kernel for x86, which supports i386 and AMD64.

NetBSD 11 introduces a dedicated micro VM kernel designed for extremely fast virtual machine boot, leveraging PVH, VirtIO, MMIO, and multiple kernel optimizations.

Using terms the wrong way and describing devices with them, I think, tend to create more confusion.

So we, especially in my courses, say that a switch is a device that operates at OSI Layer 2 that communicates by forwarding devices based on a destination MAC address.

A router is a Layer 3 device, and that is a device that forwards traffic based on the destination IP address.

So there's where the difference is.