re: On my OpenSuSE Leap 15.3 host, the PMS process binds to port 32400, but on all interfaces (I have a somewhat odd network configuration due to IPTV considerations.) If I stop my PMS processes, the interface still responds to pings, ssh processes, other support proceses, etc.
Could this be different from truenas? Does Truenas possibly have VNET whereas Linux doesn’t use VNET options and linux maybe just “binds” PMS to the same IP as the machine PMS is running off of?
You are probably right. Thank you for all the help / knowledge you’ve shared with me, I highly appreciate it.
TrueNAS is built on FreeBSD… okay, wait. Are you running TrueNAS CORE, or TrueNAS SCALE? Core is built on FreeBSD, SCALE is built on Linux (Frequently Asked Questions and Answers About TrueNAS .) Looking more at the TrueNAS pages, I rather doubt you’re running SCALE, that’s for much larger implementations. I don’t know anything at all about VNET., nor how it’s going to apply to networking.
I’m on Truenas core
I don’t know about VNET either, I’m running off a google search myself atm.
“A VNet, or a virtual network, is a service that allows you to create a private network in the cloud. You can use a VNet to run virtual machines and applications securely and efficiently.”
I think VNET is automatically enabled when running PMS using DCHP on TrueNAS core which is why i was looking into it because i don’t know a lot myself
Ah… ha. I’m used to seeing the terms virtual IP, or auxiliary IP. This means implementing another IP address on a NIC. I THINK that by default they have to be on the same IP network (VLAN tagging is probably out of scope here.) Implementing a VNET address will effectively implement another interface, and then the behavior I suggested above would still apply. PMS can (or not) bind to the VNET address, or to the parent interface.
I’m not trying to be offensive here, but given what I’m hearing from you, I think that I’d suggest simplifying your configuration. I don’t think that you need a virtual network. Virtual networks are frequently used to move IP addresses between hosts live without interrupting other services (enterprise scale stuff.) Not knowing TrueNAS at all, I have no idea how VNET interfaces would be administered.
I don’t run any virtual networking here. Okay, I do run network bridging, but that’s to implement virtual machines (that’s yet another discussion.)
Perfect suggestion! when i turn off VNET I’m able to connect direct remotely but everything is considered a “Remote” stream in plex. I don’t want to use data when watching videos locally.
With this setup will plex use my internet data to stream locally since it is considered as a “Remote Stream” in the plex dashboard?
If so do you have any idea how to fix it?
Thank you so much for your time
VNET is required to be on when running DHCP on TrueNAS Core so I’ll set a static IP instead to be able to try a “No VNET” route.
(scratches head) TrueNAS Core requires a static address for the primary interface, then can use DHCP for VNET interfaces? Interesting. I’d expect some MAC address work to be taking place there to allow DHCP bookkeeping to succeed.
Is your TrueNAS Core static address on the same IP network as your local clients? If it’s not, you need to list all of your local network in PMS Settings/Network/Local Networks. Be careful with that field, it’s very picky about exact syntax. You’ll also need an appropriate IP gate, probably in your network router. Based on your above ping testing from Win10, I’d suspect you’ve got networking in place.
TrueNAS Core doesn’t require a static address I just have one set to make accessing SMB (Windows Share from NAS) easier from my windows PC.
I believe my PMS is working properly and now is direct connecting to remote devices and still treats my local devices as local devices and doesn’t classify them “remote”.
I think my problem was netmask settings but am unsure. I’ll post pics for others, hopefully it helps someone 
I private messaged you.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
