SirLagz

joined 10 months ago
[–] [email protected] 1 points 9 months ago

About 300W, ~7kWh a day, costs me about $80 AUD a month.

[–] [email protected] 1 points 9 months ago

Thunderbolt has nothing to do with an integrated GPU.

[–] [email protected] 2 points 9 months ago (1 children)

Proxmox with Proxmox Backup Server will do most of that if you were willing to move of CentOS Stream and onto Proxmox.

[–] [email protected] 1 points 9 months ago (1 children)

I've never heard of them but I've bought a lot of random RAM before. If they use proper RAM chips like micron, Kingston, hynix, Samsung, etc then I wouldn't be too worried.

[–] [email protected] 1 points 9 months ago

Excalidraw's sketchy style can also be done in draw.io for anyone who is torn between the two lol.

[–] [email protected] 1 points 9 months ago (1 children)

I don't think I've come across a NIC in the last 15 years that hasn't been VLAN capable.

[–] [email protected] 1 points 9 months ago (1 children)

Micron, and Intel would be the ones I would use if you wanted reliability.

If you can find some Samsung enterprise spec drives then that would be ok too.

[–] [email protected] 1 points 9 months ago (1 children)

What 2 drive case with hardware RAID do you have?

[–] [email protected] 1 points 9 months ago

The newest version of Proxmox supports some SDN (Software Defined Networking) so that might be of use to you here.

I haven't played with it yet, so can't help too much, but might be worth a read of the documentation

[–] [email protected] 1 points 9 months ago (1 children)

As an alternative to the other suggestions, map out your network in Netbox and let Netbox draw your diagram for you!

[–] [email protected] 1 points 9 months ago

Are all nodes dedicated to labbing or do you have some HomeProd services running as well?

 

Netbox Drawing Diagrams

Has anyone else used the Netbox Topology Views to do your network diagrams for you?

I'm testing one of the plugins out as my work is starting to use Netbox to do the diagrams for us rather than us having to manually update diagrams.

Just looking for feedback or if anyone has any tips / gotchas when doing it this way.

 

So I have a device, it's an IP Camera - yes I'm aware of the security implications and will be making sure it is firewalled off but for now, lets assume there's no restrictions in place for the purposes of troubleshooting.

I plug it in to Homelab A - it works fine, gets an IP address, can view the stream, no issues.

I set a static IP address when at Homelab A to the same range as Homelab B, and I can ping it while located at Homelab A with a device that has the same IP address range as Homelab B

I take it to Homelab B, and plug it in, and it doesn't get an IP address if it's set to DHCP. It has worked once before, but not since then. I've tried the following -

  • Set a Static ip address when it was plugged in at Site A, then taken it to Site B - nada.
  • When the camera was set to DHCP, could see layer 2 traffic from the camera occasionally.
  • Factory reset the IP Camera
  • Factory reset the main switch at Homelab B
  • Tried different cables
  • Tried putting a switch between IP Camera and main switch
  • Tried plugging it straight into the hypervisor server and pinging it from there
  • Tried Setting the switch port to half duplex,100mbit, full duplex, gigabit, all sorts of combinations

The switch at Homelab A is a TP-Link Jetstream 24 port.

The switch at Homelab B is a Cisco SG300

Both homelabs run Proxmox.

Is there anything else I can try to see if I can get this IP Camera working before I throw in the towel?

view more: next ›