Bond and WOL

    This might be a little long winded but I want to give as accurate account as possible:


    System Info:

    8.5.7-1 (Synchrony)

    Processor
    Intel(R) Atom(TM) CPU C2750 @ 2.40GHz

    Kernel
    Linux 7.1.8+deb13-amd64

    (TrueNas Mini)


    I added a dual NIC 2.5g card and set up a bond to take advantage of my 2.5 ports on my pfSense router.

    Everything seemed like it was working just fine with this setup.

    I ran across an issue and needed to set up WOL for my NAS and it wouldn't work with the card I added so I plugged a cable into one of the onboard NICs and plugged that into my switch and set up WOL on that NIC, and set up an automation in Home Assistant to keep an eye on my NAS and if it goes inactive for a couple minutes HA will send a WOL packet.

    My issue is that it appears that since I'm using the onboard NIC for WOL all the traffic is now going through that 1g NIC instead of the 2.5g bond, is there a way to force all the traffic to the bond?

    7.7.24-7 (Sandworm) | 64 bit | Linux 6.1.0-45-amd646.1.0-0Linux 6.1.0-0

    plugins :: omvextrasorg | ssh |Wetty |SMB |openmediavault-backup |openmediavault-compose | openmediavault-rsnapshot |

    openmediavault-sharerootfs |openmediavault-snmp |

    Quote from jgyprime

    set lower "metric" for the 2.5 gbps and higher metric for the 1 gbps one.

    This way, if something goes wrong on the 2.5 gbps netwotk, you will have a fallback on the 1 gbps network.

    So currently both are set to 0 so you're saying set the 2.5g to 1 and the 1g 5?


    Update:

    Tried to set 1g metric and it's grayed out, won't let me change it.

    7.7.24-7 (Sandworm) | 64 bit | Linux 6.1.0-45-amd646.1.0-0Linux 6.1.0-0

    plugins :: omvextrasorg | ssh |Wetty |SMB |openmediavault-backup |openmediavault-compose | openmediavault-rsnapshot |

    openmediavault-sharerootfs |openmediavault-snmp |

    Edited once, last by default_user8 ().

    I don't think WOL packets are addressed to an IP address on the adapter. Try not assigning an address on that adapter. That would prevent any TCP/IP traffic on it.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    Quote from gderf

    I don't think WOL packets are addressed to an IP address on the adapter. Try not assigning an address on that adapter. That would prevent any TCP/IP traffic on it.

    You would be correct the packets go to a mac address, not an ip address, and the router is going to hand out an ip address regardless.

    7.7.24-7 (Sandworm) | 64 bit | Linux 6.1.0-45-amd646.1.0-0Linux 6.1.0-0

    plugins :: omvextrasorg | ssh |Wetty |SMB |openmediavault-backup |openmediavault-compose | openmediavault-rsnapshot |

    openmediavault-sharerootfs |openmediavault-snmp |

    Edited once, last by default_user8 ().

    Quote from default_user8

    You would be correct the packets go to a mac address, not an ip address, and the router is going to hand out an ip address regardless.

    The router will not hand out an IP address unless the adapter is configured to get one via DHCP or it is configured for static IP. So, don't do that.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    Quote from gderf

    The router will not hand out an IP address unless the adapter is configured to get one via DHCP or it is configured for static IP. So, don't do that.

    I got you now, I assumed that the NIC wouldn't communicate with OMV unless it was enabled in the OMV interface, it's a board level operation not on OS level operation. Thanks for that!


    Now i just need to get the pfSense to pass the packet from my home assistant server on my IOT vlan to my OMV nas vlan without and ip address.

    7.7.24-7 (Sandworm) | 64 bit | Linux 6.1.0-45-amd646.1.0-0Linux 6.1.0-0

    plugins :: omvextrasorg | ssh |Wetty |SMB |openmediavault-backup |openmediavault-compose | openmediavault-rsnapshot |

    openmediavault-sharerootfs |openmediavault-snmp |

    WOL packets are addressed to a MAC address.


    But if you need to WOL a computer from outside your network (WAN of your router, although I do not recommend this) you need to forward the correct ports (usually 7-9) to a local (LAN) IP and to bind that local (LAN) IP to the MAC address of the computer you want to wake, because you can't forward packets to a MAC address.


    If tjere is no ip assigned to the 1 gbps network and the 2.5 gbps network has problems, then there will be no fallback and in this case, the NAS will remain without network. Manual intervention (physically connecting a monitor keyboard to the NAS) is needed.

    If the 1 gbps network has a valid IP but with higher metric, the 2.5 gbps network will be the main adapter the traffic goes on and fallback to 1 gbps will work in case it has problems.

Participate now!

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

Register Yourself Login