Brought the camera back to homelab A, double checked IP address, still on the correct range.
Put a device onto same subnet, can ping it.
Going to try and set it back to DHCP and take it back to Homelab B and see what happens again.
Brought the camera back to homelab A, double checked IP address, still on the correct range.
Put a device onto same subnet, can ping it.
Going to try and set it back to DHCP and take it back to Homelab B and see what happens again.
It was something I was worried about when I had services exposed to the internet, but now that I'm behind CGNat, I'm not so worried because I have nothing exposed lol.
It whooshed over my head lol.
Hah...you got me. Good one.
This is a software issue anyway with this Realtek NIC.
Not the first time it's happened so I have mitigations in place, unfortunately because I shuffled some VMs around yesterday due to a power outage, the mitigations failed. That has since been sorted.
Sure, but nowhere near as often.
?? That doesn't make sense...
This is a i7-8700 on an Asus Prime H310M-E motherboard.
All I could afford at the time unfortunately.
Onboard NICs in servers are pretty much either going to be Intel or Broadcoms, so it's just something I just don't even need to think about.
Brilliant, i was looking for something like this as well for a project, thanks!
Plenty of enterprise equipment has 48V DC power supplies.
My work setup is Mains -> Rectifier shelf -> DC PSUs/Devices
Batteries are hooked into rectifier //
Last time I did this, i mapped out which plug corresponded to which device that linux saw then wrote a script that told me which hard drive was plugged into where and put it into a csv file.
This was for my disk testing tower, so when it told me "sdb" had finished badblocks, i would know which hdd sdb was.