Just an Aussie tech guy - home automation, ESP gadgets, networking. Also love my camping and 4WDing.
Be a good motherfucker. Peace.
Just an Aussie tech guy - home automation, ESP gadgets, networking. Also love my camping and 4WDing.
Be a good motherfucker. Peace.
Entity control from iOS widget
Smart locks and remote Z-wave
Preventing auto-login as Home Admin profile
Fossify Music Player 1.0.0 released
Fossify Music Player 1.0.0 released
What are your homelab stats?
Looking for/to create a sectional garage door position sensor
How are you keeping on top of fleet updates?
NAS for Proxmox HA
OPNsense on Proxmox WAN speeds
Aside from blocking instances, what other controls do admins have to keep unwanted content off their instances?
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 -lantopon 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 yournetstatoutput, like mine, only shows API conections to/from 127.0.0.1 on port 82.