Yes, the first vSwitch with the 2*1GbE is my primary interface (default route set).
Plex sees every vSwitch (as interface). So vSwitch 1 is seen as interface qvs0, vSwitch2 as qvs1 and so on. It does not see the two physical interfaces that aren’t attached to any vSwitch, but those interfaces are not configured and down (not connected).
For you then, with qvs0 as the default, and it being enumerated first, you have no problems?
If I paraphrase correctly, this is how it seems to be for everyone regardless of QTS beta, docker or LXC, or just a bunch of adapters. If first enumerated (notice the index number preceding the interface name) is the default, then all is good.
Problems always seem to arise when first enumerated is not the default or when a multi-path situation exists. (two adapters , real or virtual, on the same subnet heading out to the gateway.
No, not good. 1.13.6 does not work! It starts up, but can’t be connected to from clients or Plex/Web. It only works with 1.13.5.
Note though that QTS 4.3.5 has its own issues with interface enumeration. I had trouble with my network config after upgrading to the beta, so I reset the network to defaults (press hardware rest button for 3 seconds). After that, the numbering of my interfaces was messed up. For example, what QTS considered to be Adapter 2 in the UI is actually eth5 when doing an ifconfig. I am also missing eth4 and instead now have an eth7. So something in QNAP’s network stack is severely broken in this beta.
Nothing can be done about that until QTS is out of beta.
There’s a pretty long standing policy about not being able to support any Beta or “fix” PMS because of problems found in a Beta.
Since I have contact with QNAP, I’m hoping we can help pin down the network stack issues and then I can go back to Engineering and address anything needed for QTS 4.3.5 final.
So wanted to test some more and did a reinitialize on my nas as if brand new out of box with 4.3.5 beta installed. Only thing I did was setup a raid5 volume and install Plex. Sadly this still didnt fix anything but wanted to make sure it wasnt a configuration I had setup that was causing it. . At this point I am going to wait for the next QTS beta update then try again.