Notes

It wouldn't be a Wiki without hyperlinks...

Vultr finally resolved the problem this morning, 49 hours after I initially reported it.

"We found and issue on one of the upstream switches that had a failing process. We have corrected the issue and now I see no more errors accumulating."

Seconds_Behind_Master: 94658

🥴

Going on 27 hours of downtime now. @Vultr@twitter.com support staff have only updated my ticket to tell me to stop opening new tickets. No update on the actual packet loss problem or when it will be resolved.

The only way I can get them to respond at all is to open a new ticket each time (I now have 3 open). Their only response beyond "we are currently working on your ticket" is this gem, telling me I'm SOL because it's the weekend (!)

Two of Pushover's @Vultr@twitter.com bare metal servers in their Seattle POP have been essentially down for going on 16 hours now due to ~60% packet loss on their network. They haven't provided any updates to my ticket or updated their network status page to reflect any outage. \

How about a live search box...

Well, it's a start...

I got an Asante Micro EN/SC SCSI Ethernet device for my PowerBook that is powered by just the SCSI and ADB ports, so I had the dumb idea to get a small Ethernet->WiFi converter to make it wireless but the ADB port doesn't put out enough 5V amperage to power up the USB adapter :(

Hmm this guy makes a lot of sense

This is about 1 month's worth of IPs that attempted telnet logins to my BBS with suspicious usernames like "root" and "admin" that the BBS then sent to my firewall for blocking:

jcs@pf:~> doas pfctl -T show -t bbs_idiots | wc -l
4684

Keep on smilin'

Brrr