Jump to content

freetgy

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

freetgy's Achievements

Noob

Noob (1/14)

0

Reputation

  1. As far as i can tell ipv4 192.168.2.208 wg0 gets added automatically, if i add 192.168.2.208 as allowed peer IPs under Wireguard VPN Manager. • Removed 192.168.2.208 from allowed peers under VPN • Disabled Bridging The Disabling of Bridging did it i think, access to all Dockers works now as well as other network devices and router. Thank you very much for taking your time of supporting a newbie here. Thank you for your patience, I see i need to learn more network stuff to understand all the mechanics at play in Unraid. Any tips for a good read-up? Also i fundamentally lack understanding on the difference between macvlan and ipvlan. I understand we should use ipvlan going forward as per the latest release notes of Unraid?
  2. OK, trying to follow all your guidances. Step by Step Added Host Access to Custom Networks on Docker Added Route from 192.168.2.201 to 192.168.2.208 Docker Setting: Example Docker: Network Tab: WireGuard Result same for me: Access to 192.168.2.201 works, 192.168.2.208 does not. Rebooting the Server now just in case.
  3. See my Wireguard Setting: My Unraid is 192.168.2.201 My Docker is e. g. 192.168.2.208 Access to Unraid works fine, no access to docker on 192.168.2.208 with the above config.
  4. I was reading on the following thread, that did not provide a solution to the question raised. I have Dockers and VMs running on a different IP than the Host IP. 1. I have setup Wireguard to connect to the Unraid Server, working fine. 2. I'd like to access now the other Dockers and VMs as well, but based on my current setup there is no connection. 3. My issue is that my Router does not support static routing. Is there a way to resolve this feature gap my router has? I am hoping there is maybe a way to let the Host (Unraid) route the call of the remote device to the respective Docker/VM IP?
  5. So the screen went black, but the backlight is still powered, so there is no power reduction to be seen.
  6. So I rebooted now to see if and how long it stays on. Closing the lid has no effect display is still active at the moment.
  7. I am running Unraid OS 6.12.8 on a Dell XPS 17 Notebook (Intel Quadcore), running various Dockers and a Home Assistant VM (working perfectly fine so far). However I want to minimize Energy Consumption, the machine eats on fresh boot eats approx. 70W, in that situation the Notebook Screen is still powered on. I want to put the Monitor Display to sleep, so it does not burn energy, if I achieve that energy consumption goes down significantly (down to 35-40W). I am not aware of a way to power down the monitor at the moment via Unraid, however I have realized that if I put the Notebook to sleep (mem) and start it again via Wake On Lan, the machine fully available but keeps the Notebook display off of achieving the desired reduction of power consumption. However, when I do this procedure it seems to cause issues with my Home Assistant VM, as it can't detect Bluetooth devices anymore with the Bluetooth Adapter (Asus BT-500) = Bluetooth Integration tries to connect to Bluetooth adapter but fails. Strange thing is that the Bluetooth Adapter is still available in Unraid as well as in the Home Assistant Console (I can connect to it via Unraid Console as well as Home Assistant Terminal), so i am not sure what is causing the issue here. To simplify my life I am looking for a way to either: a) to deactivate the Notebook Display without the Wake on Lan workaround or b) resolve the issue with the Bluetooth Adapter not working correctly after waking the Notebook up again. My Current procedure to by pass this is as follows: 1. Deactivate Autostart of Home Assistant VM 2. Shutdown Unraid 3. Start Unraid, 4. Put to Sleep/Mem 5. Wake on Lan 6. Start Home Assistant VM In this scenario everything works perfectly fine. If Home Assistant Runs before putting to Sleep/Mem a) Full Shutdown and Start of the Home Assistant VM does not solve the issue b) Full Restart of Unraid solves the issue Currently not sure how to solve it. Any tips?
  8. Appreciate your guidance, still a newbie. Forgive my lack of understanding and my curiousity, why would the installation of a driver from the manufacturer for a device I own cause an violation of EULA? I'd have written a PN, but I don't see a functionality for it.
  9. I use a Workstation Notebook as a Unraid Server. Which has Geforce GTX 555. Nvidia has the driver Version 390.157 for it. How can I install this driver? I do not get it as an option with this plugin. Any guideance is appreciated.
×
×
  • Create New...