OMV multiple NICs - onboard appears to take priority?

  • Hi all


    OS: OMV 6.9.16-1 (Shaitan) - up to date


    Been using OMV for a few years now but I certainly don't consider myself a pro with it.


    Anyway, I've setup my OMV that has the following NICs:


    1 x onboard NIC

    1 x dual port HP NC360T Dual-Port Gigabit NIC PCI-E

    So the way I have it setup is like so


    Onboard NIC - (on VLAN 2) 10.7.32.x 255.255.255.0 - this NIC has WOL enabled and it works well. WOL works everytime - I use WOL from my smartphone, on the same VLAN


    The Dual Port HP NIC is on another VLAN set up as a bond with IP 10.7.12.x 255.255.255.0


    Firewall rules are in place - I can ping the OMV's dual NIC IP etc.


    Plex seems to work fine when pointing it manually to the bonded 10.7.12.x IP


    However, I've recently noticed that if I'm watching something on Plex, all the traffic appears to go through the onboard NIC, not the dual NIC. My guess is because the device I'm streaming from (TV, phone) are on the same VLAN as the onboard NIC - i.e 10.7.32.x /24


    I've tried port isolation and even intra-vlan rules to 'deny' traffic from the onboard NIC to OMV/Plex. Nothing seems to work. It's like OMV is favouring the onboard NIC over the dual-NIC card.


    Is there some sort of way to 'force' OMV to use a primary NIC? Ideally I just want the onboard NIC to deal with the initial WOL packet then the dual NIC does everything else, including streaming content from plex.


    Apologies if this is confusing. There might be an easier way to do this and I'm just over complicating matters.



    Thanks all

  • aarbron

    Added the Label OMV 6.x
  • ryecoaaron

    Approved the thread.
    • New
    • Official Post

    Assuming you are only worried about outgoing traffic, I would assume setting route metric higher for the bond than the individual interface. I just don't remember if that was an omv6 feature. It is in omv7 (which I highly recommend upgrading to).

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Assuming you are only worried about outgoing traffic, I would assume setting route metric higher for the bond than the individual interface. I just don't remember if that was an omv6 feature. It is in omv7 (which I highly recommend upgrading to).

  • Hi ryecoaaron


    I haven’t poked around too much but I can’t remember seeing route metric in the GUI for OMV 6. I’ll take a look


    Not a bad idea. I did think about upgrading to OMV 7. Is the process still fairly straight forward? I’m using docker with portainer for plex and transmission. Will it break anything?


    Thanks

    • New
    • Official Post

    Is the process still fairly straight forward?

    yes

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks Ryecoaaron


    I've upgraded successfully to version 7.


    Unless I'm doing something wrong, I've set the ipv4 'metric' to 0 on the bond and '1' on the single 'WOL' NIC


    I've also tried it in reverse - so Bond metric 1, WOL NIC - 0



    Traffic is still pushing through the WOL NIC when I stream from Plex


    Either I've set the metric wrong, or it's something else - admittedly I haven't restarted the OMV since changing the metric.


    • New
    • Official Post

    If you only want the WOL interface for WOL, it doesn't need an IP address. You could set the ipv4 and ipv6 fields to disabled and check the wakeonlan checkbox. Then set the metric for the bond to 100.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!