drkCrix
Members
-
Joined
-
Last visited
-
Good evening, I am trying to figure out if I have things setup correctly. I currently am using Wireguard with Mullvad to have my entire Unraid server behind a VPN. I have all my dockers setup as bridge. I would like to forward a port from Mullvad to a container. Right now I have a iptables PREROUTING entry that maps the external port that mullvad assigned to me to the internal IP and port of the docker image. Is that the correct way to do it? Or is there a better way? Appreciate any and all information people are willing to share, Cheers, Chris
-
What I have done thus far is this I created a tunnel using Mullvad following the Wireguard guide below https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access-to-a-commercial-vpn-provider/ Then I went back to the Mullvad site and created a port forward for that connection Then using a iptables line I found in the article below https://yevhen.ca/running-a-plex-server-through-starlink-cgnat-with-mullvad-vpn/ I added it to Unraid using the terminal window substituting the port I received from Mullvad Once that was done I went into plex and set the external port to the port that was assigned to my from Mullvad and hit apply With any luck it should show accessible. This may not be the best way of doing it and I would welcome to hear what others have to say Cheers, Chris
-
Good afternoon, Currently searching for an option to my issue and hope wireguard might be the solution. My only internet option currently is Starlink and due to CGNat I will not be able to access my plex server remotely. Can this be used to allow external access to my plex server again? Cheers, Chris
-
Good afternoon all, I have recently moved and my best bet for high speed internet was to start using my starlink dish as my main internet source. Currently they are running CGNat for IP distribution and the IPv6 service is still not 100%. What I would like to do is somehow connect to a service that allows me to assign a static IP to my Plex docker. Does anyone have a recommendation on how to best do that? Also what service would be best to suited for this? Appreciate all the info that you can provide Cheers, Chris
-
Placed my order last night (Order number 492131842) Still haven't received a key for my purchase
-
I am having this issue with 2 Adata XPG GAMMIX S5 256GB drives. Both are seen in the BIOS but I see the following during system start up. Jul 14 21:56:11 TheWatchtower kernel: nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2018-05.com.example:nvme:nvm-subsystem-OUI00E04C). Jul 14 21:56:11 TheWatchtower kernel: nvme nvme1: Removing after probe failure status: -22 Further digging I came across this *NEW* https://lkml.org/lkml/2019/7/15/57 Date: Mon, 15 Jul 2019 00:11:49 -0700 From: Misha Nasledov <> Subject: [PATCH] NVME: ignore subnqn for ADATA SX6000LNP The ADATA SX6000LNP NVMe SSDs have the same subnqn and, due to this, a system with more than one of these SSDs will only have one usable. [ 0.942706] nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2018-05.com.example:nvme:nvm-subsystem-OUI00E04C). [ 0.943017] nvme nvme1: Removing after probe failure status: -22 # lspci | grep Non-Volatile 02:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5762] (rev 01) 71:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5762] (rev 01) There are no firmware updates available from the vendor, unfortunately. Applying the NVME_QUIRK_IGNORE_DEV_SUBNQN quirk for these SSDs resolves the issue, and they all work after this patch: # nvme list /dev/nvme0n1 2J1120050420 ADATA SX6000LNP [...] /dev/nvme1n1 2J1120050540 ADATA SX6000LNP [...] Signed-off-by: Misha Nasledov <[email protected]> --- drivers/nvme/host/pci.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c index 189352081994..762ae6927689 100644 --- a/drivers/nvme/host/pci.c +++ b/drivers/nvme/host/pci.c @@ -3005,6 +3005,8 @@ static const struct pci_device_id nvme_id_table[] = { { PCI_VDEVICE(INTEL, 0x5845), /* Qemu emulated controller */ .driver_data = NVME_QUIRK_IDENTIFY_CNS | NVME_QUIRK_DISABLE_WRITE_ZEROES, }, + { PCI_DEVICE(0x10ec, 0x5762), /* ADATA SX6000LNP */ + .driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN, }, { PCI_DEVICE(0x1bb1, 0x0100), /* Seagate Nytro Flash Storage */ .driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, }, { PCI_DEVICE(0x1c58, 0x0003), /* HGST adapter */ -- Misha Nasledov <[email protected]> GPG: A063 B99A 2BD3 2D48 F2D7 8E68 0F27 4D21 948F 8F06 and this (specific for the Adata drives that use the Realtek Controller) If I need to get more info please let me know Running lspci | grep Non-Volatile I get 01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5762 (rev 01) 23:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5762 (rev 01) In a nut shell, if the system has 2 similar drives that don't have a unique NQN the system assumes its a duplicate and doesn't use it. Cheers, Chris