Lol @ “some 20 years ago … ADSL from 2002”. Thanks for making me feel old!
Just an Aussie tech guy - home automation, ESP gadgets, networking. Also love my camping and 4WDing.
Be a good motherfucker. Peace.
Lol @ “some 20 years ago … ADSL from 2002”. Thanks for making me feel old!
Oh, sure. I get that. Sending yourself reminders is absolutely understandable. Sending yourself documented evidence of your plans to defraud someone is entirely different.
In a 2017 email to himself, Smith calculated that he could stream his songs 661,440 times daily, potentially earning $3,307.20 per day and up to $1.2 million annually.
Great idea, but why would you email yourself about it?
The casting bit is the missing piece for me.
I’ve built a RasPi with Kodi for our caravan, to use Plex and stream our free-to-air TV here in Australia (using Musk’s space innernets). I just miss being able to cast from my phone, for the occasional thing I can’t do with a Kodi add-on.
Forked, and mirrored to my Forgejo server. As someone else pointed out on a different community, this is a great example of the Barbra Streisand effect in action.
People like me, without Haier appliances, are now aware of this fuckwittery, and have actively taken steps to preserve the code, before it gets taken down.
Dickheads.
Hmmm - interesting. I hadn’t bothered to check before now, but I’m seeing something similar on one of the two PBS CTs I run.
Comparing the output of
netstat -lantop
on both CTs, I can see that the one with more outbound traffic has more waiting connections from localhost on port 82, the port Proxmox Backup Servers provides its API over:tcp 0 0 127.0.0.1:51562 127.0.0.1:82 TIME_WAIT - timewait (40.38/0/0) tcp 0 0 127.0.0.1:56342 127.0.0.1:82 TIME_WAIT - timewait (29.92/0/0) tcp 0 0 127.0.0.1:44864 127.0.0.1:82 TIME_WAIT - timewait (58.94/0/0) tcp 0 0 127.0.0.1:45028 127.0.0.1:82 TIME_WAIT - timewait (11.88/0/0) tcp 0 0 127.0.0.1:44026 127.0.0.1:82 TIME_WAIT - timewait (48.66/0/0) tcp 0 0 127.0.0.1:44852 127.0.0.1:82 TIME_WAIT - timewait (58.80/0/0) tcp 0 0 127.0.0.1:59620 127.0.0.1:82 TIME_WAIT - timewait (0.00/0/0) tcp 0 0 127.0.0.1:56374 127.0.0.1:82 TIME_WAIT - timewait (30.98/0/0) tcp 0 0 127.0.0.1:51544 127.0.0.1:82 TIME_WAIT - timewait (39.98/0/0) tcp 0 0 127.0.0.1:59642 127.0.0.1:82 TIME_WAIT - timewait (0.00/0/0) tcp 0 0 127.0.0.1:45008 127.0.0.1:82 TIME_WAIT - timewait (10.92/0/0) tcp 0 0 127.0.0.1:45016 127.0.0.1:82 TIME_WAIT - timewait (11.76/0/0)
I’m wondering if the graph is pulling aggregated network data, including the loopback interface. If so, and it’s all just port 82 stuff on 127.0.0.1, then it’s probably nothing to worry about.
Edit: found this forum post that seems to indicate it’s aggregating all the byte values from
/proc/dev/net
, so this is probably nothing to worry about if yournetstat
output, like mine, only shows API conections to/from 127.0.0.1 on port 82.