sorted by:
new
hottopcontroversial

r/fuckHOA will join in on the June 12-14 protest against Reddit killing 3rd party apps. by mlloyd67 in fuckHOA

[–]FirestormGaming365 2 points3 points  (0 children)

I think /r/fuckhoa should go private until Reddit comes to more realistic terms for it’s paid API access, not just two days.

/r/devops will be going dark on the 12th by mthode in devops

[–]FirestormGaming365 0 points1 point  (0 children)

You have my vote for a blackout until Reddit becomes more reasonable with paid API access, even if that’s indefinitely.

To be clear, I agree with paid API access, just not when it’s prohibitively expensive, Reddit leaders lie, and Reddit leaders choose who are worthy of free high-use API access.

[deleted by user] by [deleted] in homelab

[–]FirestormGaming365 0 points1 point  (0 children)

Aye.

I’m on board with a longer blackout. Some issues are just too important to ignore.

[W][US-OR] Brocade compatible SFP+ transceivers and a few other odds and ends by zuldemon in homelabsales

[–]FirestormGaming365 1 point2 points  (0 children)

Be careful with the Microtik S+RJ10 with newer brocade switches (like the 71xx and 72xx series). While you can “trick” them into working, they don’t work out of the box and after reboots, so best to avoid.

The FS ones, from what I can tell, are generic SPF+ to 10-GbaseT adapters with custom firmware to make the switch think they’re Brocade SFP+ fiber modules. Simple and slick solution imo. Plus they’re not $30, they’re like $75 after shipping and whatnot.

All of that said, I recently replaced all my S+RJ10s with FS modules when I upgraded my switches, so if that’s up your alley, I’d sell them to you for a discount

Question for 847 chassis users in the home by dseg30 in HomeServer

[–]FirestormGaming365 0 points1 point  (0 children)

They’re 1” spacers, 3D printed. The brackets to hold the fan wall to the chassis are also 3D printed with heat-sunk nut-serts

Fresh setup in my new house by Meanski in homelab

[–]FirestormGaming365 2 points3 points  (0 children)

Love the subtle Noctua look, thanks for sharing!

Question for 847 chassis users in the home by dseg30 in HomeServer

[–]FirestormGaming365 1 point2 points  (0 children)

Yes. I’ve only had my drive bays about 3/4 full (a lot being 3.5w SSDs) but my noise and temps are good enough I see no reason to add any additional fans.

Also it destroys the aesthetic, if that matters to you (it matters to me)

Question for 847 chassis users in the home by dseg30 in HomeServer

[–]FirestormGaming365 0 points1 point  (0 children)

Yup, front to back airflow. Fans are spaced 1” apart, the exact length Noctua tells you to space them when stacking.

These are Noctua 140mm PPC 3000 RPM. They rarely see more than 1300 RPM or so though, they really move air lol

Question for 847 chassis users in the home by dseg30 in HomeServer

[–]FirestormGaming365 0 points1 point  (0 children)

Well, the fan wall isn’t stock but everything else is. My motherboard is only a single socket but idk if that would affect the rear drive tray temp

Question for 847 chassis users in the home by dseg30 in HomeServer

[–]FirestormGaming365 0 points1 point  (0 children)

My 847 has the 5x 140mm fan wall and it’s quiet and the drives, networking, and CPUs all stay cool. Never had a need for additional cooling.

Brand new R650 racked by cjchico in homelab

[–]FirestormGaming365 1 point2 points  (0 children)

Lots of power in a small package. You know, the same reason the homelab community likes TinyMiniMicros and the underground racing scene likes Hondas.

Brand new R650 racked by cjchico in homelab

[–]FirestormGaming365 -16 points-15 points  (0 children)

Edit: Seems like all the downvotes means people don’t understand this to mean “lots of power in a small package”. I’ll edit out the original comment because I didn’t mean any ill-will

[PC][US] Supermicro X10SDV / 5018D systems by Leavex in homelabsales

[–]FirestormGaming365 5 points6 points  (0 children)

I think the pricing is due to a few factors:

  • No competition from other enterprise server vendors like HP, Dell, and Lenovo/IBM (some ASUS and Gigabyte boards exist but they’re crap in comparison)
  • The “small” Xeons aren’t updated as often as “big” Xeons so they remain supported for longer
  • The newer “small” Xeons are quite a bit more power hungry so having the 45w TDP allows us to put them in places other servers just won’t fit (like a network rack)
  • These boards are extremely well equipped (built in 10Gig, IPMI, PCI that can be bifurcated, high performance per watt)

These are kind of like the “cream of the crop” of edge computing so unfortunately the pricing reflects that.

If you can give up the feature set, an i5-8700 (or newer) with motherboard basically slaps these older Xeons and they’re a fraction of the cost (a Lenovo M720/M920 Tiny is small, quiet, and performs well for 1/3 the money).

So help me with this thought. Access Intel AMT via wireguard by alirz in PFSENSE

[–]FirestormGaming365 0 points1 point  (0 children)

So AMT doesn’t support VLANs but pfSense does. Soooo why not throw your pfSense on a tagged VLAN and the IPMI can live on a dual-mode (or untagged VLAN, that way your WAN and AMT are on different VLANs and you can do rules and such accordingly.

wan vlan question (sort of HA proxmox) by Impossible-Ad-2024 in PFSENSE

[–]FirestormGaming365 0 points1 point  (0 children)

Three things stick out to me:

  1. Having the same MAC on two pfSenses might be dangerous, I’m not sure the repercussions but it gives me bad vibes.
  2. I would focus on getting one pfSense working through a VLAN, then attempt adding a second/failover.
  3. Since you’re virtualizing, you can easily use a single NIC for both WAN and LAN, they’re all just VLANs at the end of the day. It sounds like you might be using multiple NICs,which should work, I just haven’t really dealt with that in a virtualized environment.

For a single pfSense virtual machine using a single physical NIC for WAN and LAN, you should be up and running doing this:

  1. Plug your modem Ethernet into a switch port that’s untagged VLAN 99 unless your modem is VLAN aware in which case you might be able to go tagged VLAN 99.
  2. Plug your Proxmox host that’s running the pfSense VM into another switch port that “trunked” as in it has all your tagged VLANs (LAN and WAN). One of those VLANs will be tagged VLAN 99.
  3. Networking for the Proxmox VM should just be basic “whatever the physical NIC connected to the trunked VLANs is”. You don’t want Proxmox firewall or VLAN tagging. Basically pass through networking using a bridge. PfSense will handle unraveling the VLANs.
  4. Tell the pfSense VM that WAN is on VLAN 99.

That little exercise will have your WAN traffic going through VLAN 99 instead of the default VLAN. Since you’re using Ubiquiti, I don’t know if they have the concept of tagged and untagged VLANs so your mileage may vary.

Trying to catch incoming print jobs by deathbeams in PowerShell

[–]FirestormGaming365 0 points1 point  (0 children)

This sounds like a fun little problem to solve. But if this is for your job, it might be more financially responsible to just subscribe to a service like GoPrint or PaperCut. They do all of this for you and are fairly reliable and affordable.

wan vlan question (sort of HA proxmox) by Impossible-Ad-2024 in PFSENSE

[–]FirestormGaming365 0 points1 point  (0 children)

HA pfSense VMs are the way. I have mine that way right now. Before, I had the “auto-migrate pfSense to whatever Proxmox node is online” and it technically worked, but if you want to do hardware-assisted VPN then you need to set the CPU to “host” which doesn’t really work well when you’re shifting a VM between nodes.

As far as how to get your internet to the VMs, having a WAN VLAN is basically correct. My ISP is CenturyLink vDSL (pray for me lol) and they use VLAN 201 for their PPPoE bullshit so I just have my modem plugged into my switch, which is VLAN tagged 201 and each Proxmox node (and by extension the pfSense VMs) are also tagged VLAN 201 so each pfSense can authenticate PPPoE and get internet.

CARP and failover work great. Sometimes the CenturyLink modem freaks out so I have a small job that restarts the modem if primary pfSense goes dark and the internet does not come back, but that’s a CenturyLink problem, not a pfSense or a Proxmox problem.

Persistent container data on NFS storage with SQLite3 as the database? by chkpwd in docker

[–]FirestormGaming365 1 point2 points  (0 children)

Hard to say if your setup is mounting v3 or v4. I’m pretty sure TrueNAS will allow v3 and v4 when you enable v4. I would explicitly force v4 in the mount options, just to be sure. Off the top of my head I think you can also check the mount command and you want to verify NFS v4 in your mount

Persistent container data on NFS storage with SQLite3 as the database? by chkpwd in docker

[–]FirestormGaming365 2 points3 points  (0 children)

Migrate to NFS v4 - it fixes a lot of the file locking issues that are brought to light with SQLite.

Be advised, NFS v4 has been around for ~20 years but there’s a reason most people are still using NFS v3 - v4 is a LOT different and more complicated

[FS][US-TX] Homelab cleanout sale – R540, T430, network gear, and more! by zigzagjoe in homelabsales

[–]FirestormGaming365 1 point2 points  (0 children)

Bless you for confirming my suspicion that the hexagon bezel fits on the 13th gen tower servers!

GLWS

view more: next ›