• [6.9.0-RC1] VLAN+DHCP issue


    HalianElf
    • Urgent

    After updating to 6.9.0-RC1 I'm having issues with routing seemingly related to having VLANs enabled.

     

    My setup:

    Bonded eth0+eth1 - untagged VLAN with DHCP - metric 0 for default gateway (LAN)

    VLAN 10 - originally had static but also tried DHCP for the hell of it - metric 99 for default gateway (DMZ)

    BIND_MGMT is set so it's only accessible on the LAN (and my PC is on a different network so it's inaccessible when the route is missing)

     

    First boot on 6.9, I had an IP address but no default gateway on the untagged interface. Default route was going out the secondary (DMZ) interface. Tried a reboot, got the same results. This is when I tried setting DHCP on the VLAN as well which also just had the default gateway on the DMZ interface, so rolled back to 6.8.3 where this worked fine. (Routing did work if I added the route in on the RC as well but since it wipes it when you do anything involving networking, that's not really useful)

     

    JonP suggested trying a clean network.cfg/network-rules.cfg so removed those and tried reinstalling the RC again. This time I was able to get it routing properly with the one interface. Went into the network settings to set it back up how I had it, enabled VLANs and as soon as I did, lost the IP it had and all routes.

    tempest-diagnostics-20201212-0012.zip




    User Feedback

    Recommended Comments

    There are no comments to display.



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.