biscuitswalrus

What a great post.

Hey I don't know your technical capability, but Steve Gibson pointed out the lowest knowledge way to get an isolated network just by buying two more cheap NAT routers. Your current router stays routing internet, but in LAN1 you plug in one of the new routers, let's call it your home network, and LAN2 of your internet router plug in the other router and call it insecure. Plug in your WiFi access points into home and your devices. Plug in work laptop and other IoT to insecure. Home won't be able to talk to insecure, and insecure can't talk to home. This is all because of NAT. Just make sure the home network range is a different range to the insecure.

Otherwise it's just a vlan on router and switches and access points with no firewall rules that allow INSECURE to HOME.

You might already know all this in which case never mind!

https://www.grc.com/nat/nat.htm

I thought this was an onion article.

Thank you sir

Don't waste time on pandering to proof of ability when actions speak louder than words. The release of your research is personally something I'm looking forward to regardless of your history or experience. I will interpret your research and evaluation with my own bias and sceptical stance. I'd rather question you afterwards if your article left questions unanswered or unclear.

Jumping the gun now and questioning you before we start just wastes both our time.

Good luck with your research!

Probably because it uses nothing online, including the voice to text. It's only local device. A rare claim for those kinds of features.

Gog doesn't* (as often?) sell licenses that can be revoked as part of purchasing eula and therefore shouldn't really have to remove the misleading 'buy' word.

Many steam games you don't own and aren't buying, you're being granted access that can be revoked by the property owner. That's not just steam.

*I'm not a big Gog or games purchaser in general so I'm not sure if that's accurate. I'm sure you get the point though.

Sr-iov works already though? That's not needed for this. The motherboard presents the pci bus to the guest regardless of what's plugged in. Works fine.

This is when you want many guests to have shared graphics by partitioning a gpu. So the host still retains it and presents the graphics card to guests. You need to partition the ram up equally though, so useful only in VDI generally where you want a RTX A6000 like card to split to 10 guests each with 8gb of ram, and they share the gpu, but keep their individual video ram. Economy of scale can work out in graphics or maybe ML situations. Not so useful at home since you'll probably have a Rtx 3080 with like 10-12gb of ram, and at most you wouldn't want to split it below 8gb for modern games and partitions need to be equally sized. For 10g two = 2x5gb which would be a poor experience probably. Lots of frame stutters as it switches stuff between ram to video ram.

Hope that helps. Unless this technology unlocks better partitions it's more about opening to vdi and machine learning in a full open source context like proxmox rather than just the driver being locked behind hyperv vmware and citrix hypervisor/xen and a big yearly license. Maybe it still needs that yearly license.

This is possible now, but in xen or vmware you need to buy a nvidia license to unlock this feature. You can trial it for a minute in a lab but you can't give 4 guests each 2gb of vram on your graphics card without Nvidia specialist proprietary driver on both the host and the guest.

For vdi where you can buy 48gb rtx a6000 graphics cards, with architects (for example) each user getting each about 8gb each, you can 10 guests concurrently per card. Which at a few hundred architects scales better than buying many $5000 dollar workstations that struggle with WFH.

For a home user, maybe being able to split for your two kids on a standard rtx 3070 with what like 8gb might be OK? Probably not though.

Right now I have a hacky way that isn't really supported in nvidia to split graphics cards to two guest vms but it's neither license compatible or what I'd call "production ready". I'd like proxmox to be able to handle this out of the box because it's already in the kernel.

I've no idea what this means with licensing though. The yearly license cost to allow you to use your driver is actually stupidly expensive. The Rtx A series cards are already dumb money.

Either way it's a good thing, but probably not much news for the average enthusiast

My brothers overpriced merc uses lighting zones and detection to turn off areas to not blind incoming traffic. Cool, but I'm sure within 5 years these extremely complex lighting arrays will fail and not be user serviceable, other than full headlight cluster replacement for $4k.

More complexity, shorter life. You'll get what you want but only because it suits the makers.

Pop! Os

Imo.

What an unhinged rant. Even 30 seconds after posting I can barely understand my point. I'll leave it there unedited though.