This story is slightly munged due to my own faulty memory and to obfuscate the guilty parties...
The company I work for develops network appliances for large backbone and provider networks. One of the things these appliances do is maintain a "hearbeat" with each other so that if one disappears, the others know about it and can send an alert to the NOC.
The heartbeat packets themselves needed some kind of payload, even though the payload was not important. At that time, the company was still a small and scrappy startup so humor was generally encouraged. So naturally the engineer decided the payload should be a random line from a list of pirate quotes. Ship-its all around and the feature made it into the next major product release.
A couple months later, a very angry call comes into the helpdesk from someone _very_ high up in the food chain of a major U.S. telecom. It turns out they had noticed the pirate quotes in a random packet dump they were looking at and the network team spent a whole weekend thinking their network was very deeply compromised because our appliances were one of the tools they were using to inspect the network and kept seeing the "Yarr, Matey!" and such everywhere they looked.
Needless to say, the pirate quotes went away in a few days as part of an emergency patch and the heartbeat message was changed to something more mundane but less likely to trigger heart attacks in our customers.
> Needless to say, the pirate quotes went away in a few days as part of an emergency patch and the heartbeat message was changed to something more mundane but less likely to trigger heart attacks in our customers.
It's like the engineer picked the literal worst possible thing to send over the wire. Like making an alarm clock for people who have wartime PTSD that fires off a 9mm round to wake you up.
More startups need to be cognizant of this. Humor is important but there is a balance between fun and idiotic.
At work we have a test for these things: "If you would be uncomfortable explaining something to an auditor or judge, don't include it in the product." I think it is a good test because there are many in-jokes and engineering terms that don't sound good to laypeople.
Something I found myself saying recently: "When the parent process is about to die it's tries to kill its children, otherwise the orphans stick around holding onto their ports which is super annoying."
See also: any time a "subversion repo" is discussed in the mainstream media (see for example the breathless coverage of how Levandowski used one to steal the chauffeur project files from Google).
I'm the owner of the modem. I've found about this a couple of months back when I moved the modem to its own vlan and noticed the broadcast frames. I did some research into the author of the poem on Twitter (https://twitter.com/riojot/status/1268821579724541954), but nothing fruitful.
If anyone knows how the poem ended up in my modem, or even just what's ethertype 0x8300 all about, please comment!
The type 8300 is not a registered standard and the patent includes a payload description: "mac, port-info, vlan-info" (yes some is redundant to the headers, that is explicitly mentioned) and that doesn't fit the data. Maybe "Huawei compatible" in the meaning of "can be understood by their devices, but not exactly as patented by them". If a ring with a second such device is formed, it might respond with a different poem.
Algorhyme
I think that I shall never see
A graph more lovely than a tree.
A tree whose crucial property
Is loop-free connectivity.
A tree that must be sure to span
So packets can reach every LAN.
First, the root must be selected.
By ID, it is elected.
Least-cost paths from root are traced.
In the tree, these paths are placed.
A mesh is made by folks like me,
Then bridges find a spanning tree.
-Radia Perlman
It could be using Huawei software and hardware. Serbian ISP "Telekom Srbija" which uses mostly Huawei HG8245Q2 ONTs and has standardized on Huawei OLT and Core network, also uses these Nokia branded devices. AFAIK the Huawei GPON network is incompatible with other vendors which is why there's a small part of the capital city Belgrade stuck on old ZTE CPEs as that was a part of a pilot FTTH project with ZTE before China financed this rollout.
So, my point being, given they also use this exact Nokia ONT, it could very well mean that it's compatible with Huawei because it IS, in part, Huawei.
A shortish poem like this seems like a nice match. Ethernet has a minimum packet size, which is around the length of a line. The whole poem is short enough that you can remember it, but long enough that seeing a duplicate line would give you a good idea of having a network loop (possibly with delay) or having a second sender that started at an offset (although, maybe there's some ID information in the packet before the text begins).
This poem seems cute and memorable, and unlikely to offend any censors, and may have been available under a permissive license?
Could it be for trademark / copyright protection? There was an anti-spam mechanism in the past that worked this way. If you abused the system, they could sue you for millions. No idea if that is still around.
> Could it be for trademark / copyright protection?
Oracle uses this to connect SQL*Plus client to the database. This way, if you make a client without signing one their draconian contracts, they can sue you for infringing the copyrights on the poem.
> My ISP-provided optical modem broadcasts a poem line every 10 seconds to my local network from address 00:00:00:00:00:12 using ethertype 0x8300 frames. Anyone knows why? It's simultaneously amusing and scary.
Likewise, albeit not quite so recently (~5 months ago).
What's strange is how the poem relates to me somewhat differently being as that "gap" has already started to slowly fill. Honestly, it put a smile on my face. I love how little things like a simple poem can become so relatable to all of us.
Regardless, I'm sorry to hear of your loss. Please do give yourself time to heal--I know it sounds cliché but it's absolutely of the utmost importance. Without knowing the context, it's almost certainly for the better. It took me a while to realize that toxic people can--and WILL--drag you down no matter how much you might love them or try to work things out. Plus side is that in my case, the problem solved itself once I stopped responding to her patterns of behavior that were causing us issues!
If you need to let off some steam or just want someone anonymous to talk at, feel free to email me at my HN username at gmail.com. Having been down that road not all that long ago, I know how you feel.
Thank you very much for your reply, I really appreciate it and it resonates with me. It wasn’t so recent, but as you said things take some time to heal.
Relationships sometimes end in a sunk cost fallacy: you’ve spent so much time with someone, you think you have to fix the broken relationship at any cost, even if you’re the only one who’s still invested. And that leads to toxicity and being taken advantage of.
> It wasn’t so recent, but as you said things take some time to heal.
It does. Even last month (this ended in May--just 4 days after my birthday) I had a regression catching myself thinking about things. Usually little things. Stupid little things. Maybe I'd across something funny and thought briefly about sharing it with her only to realize that cutting off all communication is a one-way street. You can't go back. If you do, you risk opening those old wounds.
I know this isn't a popular place to say this, so I won't dwell on it, but what helped me immensely was getting back into church. Networking with other people whose compassion gave me an outlet was a tremendous relief.
I think that's the real key though: Having a support network is the most important keystone in paving a road to success after personal hurt. It's not easy, and you're right--it takes a lot of time. A dear friend whom I made through this told me, using his own experiences (he lost his son just 2 years ago) as a guide: You can get bitter or you can get better. It's a choice.
> you think you have to fix the broken relationship at any cost
This really hit home. Mine wasn't bad (or abusive), but even in spite of it, I felt exactly that way. If things went south for whatever reason, I wanted nothing more than to recover it back to the prior state. Love is hard, but the fear of losing that love is even harder.
Honestly, if I were smart, there were a number of red flags that should've been an indication I needed escape the situation. But, I wasn't. I fully accept that my choices were entirely stupid and motivated by the fact that I didn't want to hurt her. (It sounds ridiculous typing this out since I feel I'm just trying to rationalize it ex post facto, but it's how I felt at the time.)
> And that leads to toxicity and being taken advantage of.
...even if sometimes that "being taken advantage of" is strictly emotional!
I think what made it worse for me was that we were very close friends before the relationship started, and during it. Losing a romantic interest is one thing; losing someone who was your best friend for so long? That's much harder. The only way I could mentally rationalize it in the beginning was to pretend she passed away. In a strange series of mental gymnastics, I guess she did. She transformed into someone I didn't recognize (fancy title in front of her name; justified treating me differently), and that friend I had for so long honestly did die--at her own hands.
I know that as this post ages, there'll be others who stumble on it and wonder why the heck I typed all this out. Then there'll be those few who read our conversation here and realize that, yes!, things really do get better. It hurts. It sucks. You'll dwell on it for a while. But you can't dwell on it forever! For my part, a new gal has taken my interest from church, and I'm hoping to grow a new friendship just to see where the path leads. I was worried I wouldn't keep my heart open to such things; but, I realized that if I closed it off, I was letting that other person inflict harm on my future relationships. That's not fair to anyone, and it's giving a person who's no longer in my life far too much control that they don't deserve.
I'm going to cherish that poem. Ironically, I hadn't intended to browse HN tonight, then came across this headline.
Sorry about the lengthy post. Your comment really impacted me and made me take a moment to reflect on everything.
I always thought it would be a unique method of prayer (for an existing or new religion) that used part of the IPv6 packet header or an ICMP packet. We would be sending prayers at random with a ttyl to be broadcast across existing networks, and routers/endpoints could choose to listen.
More importantly, it might cause some devices to wake their network hardware or even CPU's up every 10 seconds, and significantly shorten battery life.
A device that wakes on broadcast packets of an unknown type would be very poorly designed and wouldn't get much sleep on any network. Wake-on-LAN usually only wakes up when it receives a magic packet, or possibly if it it receives a packet addressed specifically to that device (not broadcast).
My 'home' network (with 10 people, 70 unique devices last month), there are currently only about 15 broadcast packets per minute, and they're all things that could be filtered/handled in wifi firmware (DHCP requests, multicast management traffic, STP stuff, ARP discovers, etc.).
If other networks are like mine, then it would be reasonable for firmware to wake up for any unhandled thing, since the application processor might need to handle that unknown message, and to not wake up would leave the application developer sad...
Maybe it is some _copyrighted_ beacon? I've read somewhere that Oracle have made some verse a part of some network API of theirs to be able to copyright it.
The original LEGO Mindstorms had a handshaking mechanism like this. The firmware for the RCX brick was stored in battery-backed RAM, so you had to re-upload it via infrared whenever you changed the batteries. But the ROM bootloader would only accept a firmware image if it contained the string:
> "Do you byte, when I knock?"
After uploading, the host computer would send an "unlock request" with the string "LEGO®", at which point the RCX would return the other half of the rhyme:
> "Just a bit off the block!"
I assume the only reason for jumping through these hoops was to have a legal excuse to discourage other companies from making interoperable products. I have no idea whether this strategy would have actually held up in court; in any case, there were plenty of homebrew tools that just embedded the magic strings anyway.
Something in nature like "DontstealOSX" or whatever that SMBIOS string in Mac machines is called?
In any case, doing this to an API is just plain nasty... but I believe at least under European law it's still getting trumped by the right to interoperability and reverse engineering.
Reminds me of the folklore.org[1] story about the Steve Jobs-requested, Susan Kare-designed bitmap embedded in the original Macintosh ROM to catch cloners.
That strategy doesn't work in my country as the law clearly stated mere protocol is not copyrightable.
Another interesting case was, Nintendo released a floppy disk with their logo relief and use its presence for DRM purpose. When third party released a compatible floppy disk, Nintendo sued them for trademark violation. Nintendo lost.
A lot of residential modems are also providing networking for IPTV set top boxes. This could be a keep alive for them (even if this particular provider doesn't offer that service).
The company I work for develops network appliances for large backbone and provider networks. One of the things these appliances do is maintain a "hearbeat" with each other so that if one disappears, the others know about it and can send an alert to the NOC.
The heartbeat packets themselves needed some kind of payload, even though the payload was not important. At that time, the company was still a small and scrappy startup so humor was generally encouraged. So naturally the engineer decided the payload should be a random line from a list of pirate quotes. Ship-its all around and the feature made it into the next major product release.
A couple months later, a very angry call comes into the helpdesk from someone _very_ high up in the food chain of a major U.S. telecom. It turns out they had noticed the pirate quotes in a random packet dump they were looking at and the network team spent a whole weekend thinking their network was very deeply compromised because our appliances were one of the tools they were using to inspect the network and kept seeing the "Yarr, Matey!" and such everywhere they looked.
Needless to say, the pirate quotes went away in a few days as part of an emergency patch and the heartbeat message was changed to something more mundane but less likely to trigger heart attacks in our customers.