Toes♀

Would love to see this as a universal mandate.

32 is still pretty low. I’d like to see that bumped up another factor. 64GB would be more practical, given the nature of recording in 4k.

After all this time I’ve become so used to glide typing that I don’t see any value in this tool. But I guess there’s a market for it. So enjoy

That’s frustrating 😕

If you’re lucky someone has created a rom and jailbreak solution. The XDA forums would be your best bet to find out.

But it is rather unlikely unless it was very popular.

I haven’t tried setting up jellyfin myself. However, if you’re able to use pcie passthrough on your container, you could probably use any spare card you might have? (assuming it fits and your psu can handle it)

Oh thanks I must have missed that in the title.

The xeon does have more cache too. So if the GPU acceleration is the make or break it option. You could toss a card in there.

I’m assuming you’re talking about version 1 of the 2620.

Although the xeon is the weaker processor, if you’re planning on having those containers active together the larger thread count will potentially be more beneficial than the faster i7.

But this is one of those things where you’d need to test against both and see. Since there’s a bunch at play.

I’m assuming the xeon comes with ECC ram?

I’d decide based on how loud it’s gonna make my homelab, if I get to use ECC ram and the type of workload being applied.

Since you’re just looking to make a router the xeon would be my tentative choice.

That must be a very unfortunate situation where you don’t have control of your network for that to be a concern though. in which case I wouldn’t expect it to be suitable for a internet facing homelab?

Like I’m struggling to think of scenarios for this.

I suppose you could be trying to setup a homelab on a college network or using someone else’s internet connection where you have no input on the matter.

Perhaps, I could see a case for CGNAT like another user mentioned, where the whole town shares an single IP for example. But I’d imagine such a network would offer poor performance.

But in all those scenarios, a VPS is cheaper and you can do everything this service offers and more.

Yeah that’s a fair point, much like a VPN I could see this being useful in scenarios where you have limited control over your network.

It’s fairly straightforward to do for free with Hurricane Electric. Some home routers even have it built in as an option. https://tunnelbroker.net/

I’m assuming anyone who’s playing around with servers is capable of implementing it.

Go on eBay, punch in the price you’re looking to spend and search for an old server. Keep in mind some manufacturers use proprietary connectors.

Look for servers with lots of ECC ram, clean photos of the internals.

They probably won’t have a drive that’s pretty common.

To meet that 16 core requirement, you’ll probably be looking at older dual socket systems.

Edit: a quick search I found this. https://www.ebay.com/itm/225978893065?

Not a perfect match but the price is pretty good.

If I was in your IT department I’d be required to shut this down and probably revoke your access until our bosses decide on your future.

Keep in mind, your employer has a responsibility to protect their data and this would subject your homelab to any legal liabilities such as a lawsuit search order and data privacy auditing.

Any solution you work out needs to be signed off on in writing if it’s outside their expected usage.

Another important point o365 requires oauth2 authentication unless your IT department has intentionally allowed other forms of authentication or they are in a hybrid legacy environment.

When they broke EWS and office 2010 compatibility they crippled many foss solutions without an additional license and the tools that do work will report details to exchange about your homelab. So if your department is diligent it’ll come to their attention.

My clients when they text me the server is down.

I’d suggest configuring it for AV1 and use a RDNA 3 GPU.

Yeah give that a go. Glad to help 🙂

Ok in that case. The goal is to use a cipher suite that works well on your device that is still secure. AES is accelerated on most processors these days. But you’ll want to confirm that by looking up your specific cpu (both host and client machines!) and checking for AES acceleration.

AES-128-GCM would be my suggestion.

UDP mode provides less overhead, so it should be faster for you.

Alternatively you could use IPsec instead of openvpn but that’s a chore to configure. But it has the benefit of being free and being natively supported by many devices.

You would still want to configure an appropriate cipher suite that’s fast and secure.

You mentioned that your cpu is getting maxed out on wireguard. That makes a lot of sense since it’s generally not hardware accelerated, old low end CPUs could struggle here.

What choices do you have for protocols with your VPN software?

Try AES128 UDP mode with openVPN.

Try switching to openwrt firmware on the router.

D-Link stock firmware tends to be rather buggy in my experiences.

Power saving features sounds like a strong possibility.

I’ve seen a problem like this where it was related to the client switching between 2.4ghz and 5ghz and the router switching channels rather frequently.

Try writing a keep alive job. Every ten seconds ping Google.