• 1 Post
  • 85 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle

  • If you want to use the PI as a router you’ll probably end up with a double NAT situation which isn’t ideal but may work well enough. In terms of wifi performance, I wouldn’t expect a Pi to be particularly good here so I’m not sure this even worth it unless it’s just a budget issue and you don’t have any other options.

    In terms of your problem, you should be able to assign the Pi ethernet port to the default WAN and WAN6 networks. As for wifi, the Pi adapter needs to have support for AP mode, and looking around it doesn’t seem clear if the built in wifi adapter supports that or not (most people using the Pi are using it purely as a router and not a wireless AP). If not, you’d need a USB wifi adapter that supports AP mode. You might want to get that additional ethernet adapter too for testing/debugging and it will allow you to add a dedicated wireless AP.


  • It’s nice not to deal with HTTPS warnings etc and as you said it’s more convenient to access by domain name rather than remembering port numbers. You should be able to technically achieve the latter in another way by using docker and configuring it to assign a real IP for each service (a bridge network presumably), then setting each service to use port 80 externally. But that’s probably as much work as just setting up a reverse proxy.

    And if you’re concerned about exposing ports, you can use DNS challenge which doesn’t require opening port 80 on your router.





  • I think there are more people that are #1 and #2 the same time

    Probably where some of the attitude comes from. People are assuming that it’s paid IT people bringing their work home with them, which is a different case then a casual user trying out self-hosting without the broader background.

    Although I haven’t seen this attitude myself so I suspect it’s not that common, and probably just a handful of users jumping to conclusions.







  • Mainly because running multiple desktop machines adds up to a lot of power, even at idle. If you power them off and on as needed it’s better, but then it’s not as convenient. Of course, if you leave a single machine with multiple GPUs on 24/7 that will also eat a lot of power, but it will be less than multiple machines turned on 24/7 at least.

    And the physical space taken up by multiple desktop machines starts to add up significantly, particularly if you live in an apartment or smaller house.



  • I’ve recently tried to do that using sunsine and different linux gaming distros and it was awful, the VM was working great for a few minutes and then suddenly crashes and I have to hard stop it.

    Are you running this with something like libvirtd/qemu? If so, VFIO configurations can get pretty complex. Random crashes seem like MSI interrupt issues (or you’ve allocated too much RAM to the guest). Or it could be GPU reset issues that would also occur on the (Linux) host, a newer kernel and Mesa version in the guest may help.

    Setting on the kernel commandline for the host to workaround MSR interrupt crashes:

    kvm.ignore_msrs=1

    If you’re running on a Windows host or with something like Virtualbox (assuming GPU passthrough is supported by these), YMMV but I wouldn’t expect good results.