@litchralee_v6@ipv6.social

Litchralee_v6 @litchralee_v6@ipv6.social

· 1w ago

Today I saw a post on Hackaday about "UDP broadcasting" and #IPv6. Only that it barely touched upon UDP or broadcasting, and mostly served to reinforce long-dead or never-true assumptions that devs tend to have #IPv6.

One citation is to a "2020 rant" that can be summarized as: addr6 too long, DNS broken, bad software. All of which are v4 faults projected onto v6.

But my chief complaint is the idea that v6 subnetting has gone away? What?? How can that idea withstand a moment's thought? (1/n)

ipv6.social

4

0

2

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 1w ago

RE: @arstechnica@mastodon.social

As with all days, today is an excellent time to move (or make a plan to move) from RSA digital signatures to anything else, whether PQC or not. EdDSA or ML-DSA are good candidates.

mastodon.social

2

0

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 2mo ago

Replying to

@nuintari@mastodon.bsd.cafe Does it count if it was in writing rather than said aloud? I once came across a document where someone ruled out using SSH as a secure transport from a guest VM to the host. But rather than citing a colorable rationale, they blamed the VM vendor for "undocumented behavior" that prevents routing packets in the 127.0.0.0/8 subnet... Nevermind whether other address ranges were available, I'm stunned that someone: 1) thought to try this, 2) didn't try anything else, 3) blamed the vendor.

6

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Replying to

@intransitivelie @sluttymayo The classic "double diamond" shape for bicycles does genuinely have a material advantage, in that the frame uses less steel/aluminum for the same strength. That said, the difference is small and in the context of today's e-bikes, it's entirely overshadowed by the battery weight. Hence, the practical downside is reduced, and now everybody can ride without having to throw a leg over. I'm a fan of more people on two wheels, whatever shapes they may choose.

8

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 2mo ago

Replying to

@azonenberg@ioc.exchange Only tangentially related, I learned the other day that mountain bikers in muddy terrain have "tear offs", which are transparent stickers that go over their goggles. So if the goggles need clearing, they can just reach for the tab and pull the tear-off away. Some riders will apply multiple tear-offs, with offset tabs, so they can repeatedly clear their vision. I'm enthused at how simple the solution is.

2

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Replying to

@tschaefer At the current rate, the proposal -- which I will not even dignify with a name -- will become a litmus test, to detect people who genuinely do not understand one iota of network complexity, or history for that matter. Such people must never be put in charge of anything more complicated than plugging in an Ethernet cord.

4

2

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 4mo ago

Replying to

Ref: https://datatracker.ietf.org/doc/html/rfc3986#section-5.1

IETF Datatracker

RFC 3986: Uniform Resource Identifier (URI): Generic Syntax

A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing th

2

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 4mo ago

Replying to

@sash@hachyderm.io Excellent write-up! While reading, I had the thought of possible mitigation in the #meshcore firmware, such as dropping adverts that contain node names with "http://". But TIL, relative URIs allow omitting the scheme. So ultimately, sanitizing the node names before presentation is the most robust solution, exactly as your write-up concludes.

2

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Replying to

@jima @tschaefer @ghostinthenet The thing is, I'd prefer to never have to see that dismal document ever again. Its very existence exudes categorical error.

2

15

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

@jana@social.jsteuernagel.de @Bluewall@infosec.exchange @loos@aleph.land The proposal is entirely unserious. In only two minutes, I came across grossly incompatible statements like:

> The suite is 100% backward compatible.

And:

> Organisations assign internal zone prefixes (127.1.0.0, 127.2.0.0 etc) to network zones and regions.

More than once in my career, I have had to point to the 1993 RFC that reserves the entire 127.0.0.0/8 subnet for solely loopback. And this nonsense is still happening in 2026??

2

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Replying to

@jima @tschaefer @ghostinthenet Do IETF proposals get their TTL extended when there's a revision? I would support additional meowing in the only proposal that's worth talking about, just to make sure it sticks around. 🐱

1

17

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Replying to

@jima @tschaefer @ghostinthenet In some ways, I think it's perfect that LinkedIn content stays wholly contained within that platform lol

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

@nuintari@mastodon.bsd.cafe Honestly, it's somewhat surprising they didn't reintroduce classful networking. Considering the trainwreck before us, they might as well have defined Class D, Class E, and Class F networks to be /96, /84, and /72, for no obvious reason whatsoever and in stark contravention to anything learned in the last 30 years.

Probably the worst part is that people who don't know better will think that 8 > 6 and therefore ask their network admins to implement this. God help these admins.

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Some while ago -- I think it was an @azonenberg@ioc.exchange post -- I learned of a company that sells a fast-drying, mil-spec hand lotion for use in cleanrooms, that comes in an ESD-safe bottle and sold in gallon (3.78 L) amounts.

Would this be overkill for my work-from-home desk job? Yes.

Did I find a good deal online? Yes.

And I can say that so far, I like it.

https://rrlotion.com/product/ic-lotion-fragrance-free/

R&R Lotion®

IC Lotion Fragrance Free (Cleanroom)

IC Fragrance-Free Pre-gloving Lotion is non-contaminating, static dissipative, and moisturizing. No silicones, lanolin’s, glycerin, or mineral oils.

1

3

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 6mo ago

Replying to

@lw I think, but I'm not certain, this might be due to how WG attaches itself to the iptables/nftables chain, stealing packets before they get to the routing decision. Perhaps "iptables -vL" will show something along those lines? It's been a while since I've dealt with iptables, and I now mostly prefer to do WG in a separate namespace so that my application containers don't have to be dual-stack.

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 6mo ago

Replying to

@hugo A colleague of mine had the unusual circumstance of his #meshcore gear arriving earlier than expected, so much so that the courier forgot to collect the duties owed and had to request it after delivery was already made.

1

7

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 6mo ago

Replying to

@lw What does "ip -4 route" look like? There might be a default route that it's trying to connect through, one which dead-ends but it won't know that until it tries. For WG, if you remove the default route and replace it with a static route for precisely the WG endpoint, I think that should result in all Legacy IP traffic being unroutable except for WG.

0

6

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 6mo ago

Replying to

@lw Firstly, I want to apologize for missing the part in your original post where you already said there was no default route. I now see how strange the situation is. It's perplexing as to what would be holding up the v4 connection. Is tcpdump or Wireshark available to examine the traffic? The primary DNS server is on v6?

0

4

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Replying to

@jima @tschaefer @ghostinthenet For different reasons, I no longer use archive\.is links or visit them

0

3

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

Replying to

@azonenberg I'm poised to agree! That said, it took some searching to find where to buy this stuff. All the local suppliers from their website didn't have it. Grainger did, but at quite a markup. And I didn't want to buy this from Amazon. Somehow eBay had it for near MSRP though.

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 5mo ago

@nuintari@mastodon.bsd.cafe I couldn't make it through more than two minutes of reading the sheer contradictions.

I wish to give it no further consideration, except as an excellent example of how an onslaught of truly insane, possibly LLM generated slop is sufficient to tire out the BS-meters from anyone that still has a working one.

I wonder if anyone has ever done fondue cheese with popcorn.

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 2mo ago

Replying to

@azonenberg@ioc.exchange Is this an oddball because U.FL is normally for RF signals that require careful impedance matching, which generally precludes through-hole because of the difficulty with impedance matching and reflections? Maybe there are people using U.FL as a power or low-speed digital bus connector?

0

2

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 3w ago

Replying to

@nuintari@mastodon.bsd.cafe At the risk of showing my youth and naivete, Packard Bell is a name I've only heard of but never experienced. The Wikipedia page tells me they were in the same boat as eMachines and Gateway in the early 21st Century, so I imagine they were particularly low-quality consumer machines?

0

1

0

Litchralee_v6 @litchralee_v6@ipv6.social

· 3w ago

Replying to

@nuintari@mastodon.bsd.cafe That's a subset of softmodems, right? I have only a preview of their horrors from the intro blurb for the talk that @philpem@digipres.club is giving next month. https://digipres.club/@philpem/117242377663791348 I take it then that they're an abomination unto software and hardware engineering.

digipres.club

Phil M0OFX: "I'm happy to announce I'll be speaking at @jawnco…" - digipres.club

0

1

0