Need to add Vlans to my NetPlan Config with KVM Bridge and bondingBridge interfaces and KVM17.10 netplan config with bridgeInvalid YAML in Netplan/Bridging/VLAN tags for qemu/libvertdConfig bridge network in order to using KVMBridging, bonding and netplanNetplan add VLAN on the fly?

How can an immortal member of the nobility be prevented from taking the throne?

I am particularly fascinated by the Chinese character that is pronounced SHIN & means faith or belief

How to deal with non-stop callers in the service desk

Why does the SR-71 Blackbird sometimes have dents in the nose?

Why is more music written in sharp keys than flat keys?

Command which removes data left side of ";" (semicolon) on each row

Paint numbers from 1 to 23 with three colours

If a tournament advertises G/30, can either player demand G/25 d5?

What elements would be created in a star composed entirely of gold?

Hangman game backward #12

How can I filter an EntityClass by _not_ having a property?

Heat involved in isenthalpic process

What type of key profile is this?

Term for anticipating counterarguments and rebutting them

In Cura, can I make my top and bottom layer be all perimiters?

How could a sequence of random dates be generated, given year interval?

Why does the Joker do this to Bob?

Why was the "Cave of the Patriarchs" forbidden to Jews?

NFL football incentives

Simple code that checks if you're old enough to drive

Can you identify this fighter aircraft?

What could a technologically advanced but outnumbered alien race do to destroy humanity?

Regular sized fonts in oubraces package

Why are my plastic credit card and activation code sent separately?



Need to add Vlans to my NetPlan Config with KVM Bridge and bonding


Bridge interfaces and KVM17.10 netplan config with bridgeInvalid YAML in Netplan/Bridging/VLAN tags for qemu/libvertdConfig bridge network in order to using KVMBridging, bonding and netplanNetplan add VLAN on the fly?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









0

















I have made this yaml for a 4 nic bond and a static IP but I need to add four VLANs to the bond. The VLANs are 77, 88, 99, 333 could someone help me with this config? I also use the configuration for a KVM bridge with br0 and need that to still work.



This current yaml works but just need to add the VLANs.



https://gist.githubusercontent.com/R...nager-all.yaml



network:
bridges:
br0:
addresses:
- 10.0.77.2/24
dhcp4: false
gateway4: 10.0.77.1
nameservers:
addresses:
- 10.0.77.1
- 8.8.8.8
interfaces:
- bond0
bonds:
bond0:
interfaces:
- eno1
- eno2
- eno3
- eno4
parameters:
mode: balance-xor
ethernets:
eno1:
addresses: []
dhcp4: false
dhcp6: false
eno2:
addresses: []
dhcp4: false
dhcp6: false
eno3:
addresses: []
dhcp4: false
dhcp6: false
eno4:
addresses: []
dhcp4: false
dhcp6: false









share|improve this question




























  • Your link is not valid.

    – heynnema
    Jun 1 at 14:47

















0

















I have made this yaml for a 4 nic bond and a static IP but I need to add four VLANs to the bond. The VLANs are 77, 88, 99, 333 could someone help me with this config? I also use the configuration for a KVM bridge with br0 and need that to still work.



This current yaml works but just need to add the VLANs.



https://gist.githubusercontent.com/R...nager-all.yaml



network:
bridges:
br0:
addresses:
- 10.0.77.2/24
dhcp4: false
gateway4: 10.0.77.1
nameservers:
addresses:
- 10.0.77.1
- 8.8.8.8
interfaces:
- bond0
bonds:
bond0:
interfaces:
- eno1
- eno2
- eno3
- eno4
parameters:
mode: balance-xor
ethernets:
eno1:
addresses: []
dhcp4: false
dhcp6: false
eno2:
addresses: []
dhcp4: false
dhcp6: false
eno3:
addresses: []
dhcp4: false
dhcp6: false
eno4:
addresses: []
dhcp4: false
dhcp6: false









share|improve this question




























  • Your link is not valid.

    – heynnema
    Jun 1 at 14:47













0












0








0








I have made this yaml for a 4 nic bond and a static IP but I need to add four VLANs to the bond. The VLANs are 77, 88, 99, 333 could someone help me with this config? I also use the configuration for a KVM bridge with br0 and need that to still work.



This current yaml works but just need to add the VLANs.



https://gist.githubusercontent.com/R...nager-all.yaml



network:
bridges:
br0:
addresses:
- 10.0.77.2/24
dhcp4: false
gateway4: 10.0.77.1
nameservers:
addresses:
- 10.0.77.1
- 8.8.8.8
interfaces:
- bond0
bonds:
bond0:
interfaces:
- eno1
- eno2
- eno3
- eno4
parameters:
mode: balance-xor
ethernets:
eno1:
addresses: []
dhcp4: false
dhcp6: false
eno2:
addresses: []
dhcp4: false
dhcp6: false
eno3:
addresses: []
dhcp4: false
dhcp6: false
eno4:
addresses: []
dhcp4: false
dhcp6: false









share|improve this question

















I have made this yaml for a 4 nic bond and a static IP but I need to add four VLANs to the bond. The VLANs are 77, 88, 99, 333 could someone help me with this config? I also use the configuration for a KVM bridge with br0 and need that to still work.



This current yaml works but just need to add the VLANs.



https://gist.githubusercontent.com/R...nager-all.yaml



network:
bridges:
br0:
addresses:
- 10.0.77.2/24
dhcp4: false
gateway4: 10.0.77.1
nameservers:
addresses:
- 10.0.77.1
- 8.8.8.8
interfaces:
- bond0
bonds:
bond0:
interfaces:
- eno1
- eno2
- eno3
- eno4
parameters:
mode: balance-xor
ethernets:
eno1:
addresses: []
dhcp4: false
dhcp6: false
eno2:
addresses: []
dhcp4: false
dhcp6: false
eno3:
addresses: []
dhcp4: false
dhcp6: false
eno4:
addresses: []
dhcp4: false
dhcp6: false






networking server maas kvm vlan






share|improve this question
















share|improve this question













share|improve this question




share|improve this question








edited May 31 at 17:46









Yufenyuy Veyeh Dider

1,7105 gold badges11 silver badges25 bronze badges




1,7105 gold badges11 silver badges25 bronze badges










asked May 31 at 16:18









GodSyNcGodSyNc

32 bronze badges




32 bronze badges















  • Your link is not valid.

    – heynnema
    Jun 1 at 14:47

















  • Your link is not valid.

    – heynnema
    Jun 1 at 14:47
















Your link is not valid.

– heynnema
Jun 1 at 14:47





Your link is not valid.

– heynnema
Jun 1 at 14:47










1 Answer
1






active

oldest

votes


















0


















This is the netplan file I would start out with. I am assuming vlan77 (from 10.0.77.0/24) is the native and the bond is a trunk. I also assume you want the VMs to be located in different vlans:



#/etc/netplan/01-networkd-vlan-bond.yml
network:
version: 2
renderer: networkd
ethernets:
eno1:
addresses: []
dhcp4: false
dhcp6: false
eno2:
addresses: []
dhcp4: false
dhcp6: false
eno3:
addresses: []
dhcp4: false
dhcp6: false
eno4:
addresses: []
dhcp4: false
dhcp6: false
bonds:
bond0:
interfaces: [eno1, eno2, eno3, eno4]
addresses: [10.0.77.2/24]
gateway4: 10.0.77.1
nameservers:
addresses: [10.0.77.1,8.8.8.8]
search: [domain.tld]
dhcp4: false
dhcp6: false
parameters:
mode: balance-xor

bridges:
br0:
interfaces: [ bond0 ]
dhcp4: false
dhcp6: false
parameters:
forward-delay: 0
stp: true
br88:
interfaces: [ vlan.88 ]
dhcp4: false
dhcp6: false
addresses: []
parameters:
forward-delay: 0
stp: true
br99:
interfaces: [ vlan.99 ]
dhcp4: false
dhcp6: false
addresses: []
parameters:
forward-delay: 0
stp: false
br333:
interfaces: [ vlan.333 ]
dhcp4: false
dhcp6: false
addresses: []
parameters:
forward-delay: 0
stp: true

vlans:
vlan.88:
id: 88
link: bond0
dhcp4: false
dhcp6: false
vlan.99:
id: 99
link: bond0
dhcp4: false
dhcp6: false
vlan.333:
id: 333
link: bond0
dhcp4: false
dhcp6: false


This is all assuming vlan77 is the native vlan so if that isn't the case, some modifications would need to be made. Since vlan77 is native you don't need a separate entry for vlan77.



I assign all IP addresses via my dhcp servers so my setup is slightly different and I've noticed on some networks I've had to have both the bond and the native vlan set to receive dhcp addressing so you may need to put the same IP address info in both the bond and the native bridge, which, in your case, would look like:



 br0:
interfaces: [ bond0 ]
dhcp4: false
dhcp6: false
addresses: [10.0.77.2/24]
gateway4: 10.0.77.1
nameservers:
addresses: [10.0.77.1,8.8.8.8]
search: [domain.tld]
parameters:
forward-delay: 0
stp: true


But you shouldn't need this as it is not documented and really doesn't make much sense.






share|improve this answer



























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );














    draft saved

    draft discarded
















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1147686%2fneed-to-add-vlans-to-my-netplan-config-with-kvm-bridge-and-bonding%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown


























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0


















    This is the netplan file I would start out with. I am assuming vlan77 (from 10.0.77.0/24) is the native and the bond is a trunk. I also assume you want the VMs to be located in different vlans:



    #/etc/netplan/01-networkd-vlan-bond.yml
    network:
    version: 2
    renderer: networkd
    ethernets:
    eno1:
    addresses: []
    dhcp4: false
    dhcp6: false
    eno2:
    addresses: []
    dhcp4: false
    dhcp6: false
    eno3:
    addresses: []
    dhcp4: false
    dhcp6: false
    eno4:
    addresses: []
    dhcp4: false
    dhcp6: false
    bonds:
    bond0:
    interfaces: [eno1, eno2, eno3, eno4]
    addresses: [10.0.77.2/24]
    gateway4: 10.0.77.1
    nameservers:
    addresses: [10.0.77.1,8.8.8.8]
    search: [domain.tld]
    dhcp4: false
    dhcp6: false
    parameters:
    mode: balance-xor

    bridges:
    br0:
    interfaces: [ bond0 ]
    dhcp4: false
    dhcp6: false
    parameters:
    forward-delay: 0
    stp: true
    br88:
    interfaces: [ vlan.88 ]
    dhcp4: false
    dhcp6: false
    addresses: []
    parameters:
    forward-delay: 0
    stp: true
    br99:
    interfaces: [ vlan.99 ]
    dhcp4: false
    dhcp6: false
    addresses: []
    parameters:
    forward-delay: 0
    stp: false
    br333:
    interfaces: [ vlan.333 ]
    dhcp4: false
    dhcp6: false
    addresses: []
    parameters:
    forward-delay: 0
    stp: true

    vlans:
    vlan.88:
    id: 88
    link: bond0
    dhcp4: false
    dhcp6: false
    vlan.99:
    id: 99
    link: bond0
    dhcp4: false
    dhcp6: false
    vlan.333:
    id: 333
    link: bond0
    dhcp4: false
    dhcp6: false


    This is all assuming vlan77 is the native vlan so if that isn't the case, some modifications would need to be made. Since vlan77 is native you don't need a separate entry for vlan77.



    I assign all IP addresses via my dhcp servers so my setup is slightly different and I've noticed on some networks I've had to have both the bond and the native vlan set to receive dhcp addressing so you may need to put the same IP address info in both the bond and the native bridge, which, in your case, would look like:



     br0:
    interfaces: [ bond0 ]
    dhcp4: false
    dhcp6: false
    addresses: [10.0.77.2/24]
    gateway4: 10.0.77.1
    nameservers:
    addresses: [10.0.77.1,8.8.8.8]
    search: [domain.tld]
    parameters:
    forward-delay: 0
    stp: true


    But you shouldn't need this as it is not documented and really doesn't make much sense.






    share|improve this answer






























      0


















      This is the netplan file I would start out with. I am assuming vlan77 (from 10.0.77.0/24) is the native and the bond is a trunk. I also assume you want the VMs to be located in different vlans:



      #/etc/netplan/01-networkd-vlan-bond.yml
      network:
      version: 2
      renderer: networkd
      ethernets:
      eno1:
      addresses: []
      dhcp4: false
      dhcp6: false
      eno2:
      addresses: []
      dhcp4: false
      dhcp6: false
      eno3:
      addresses: []
      dhcp4: false
      dhcp6: false
      eno4:
      addresses: []
      dhcp4: false
      dhcp6: false
      bonds:
      bond0:
      interfaces: [eno1, eno2, eno3, eno4]
      addresses: [10.0.77.2/24]
      gateway4: 10.0.77.1
      nameservers:
      addresses: [10.0.77.1,8.8.8.8]
      search: [domain.tld]
      dhcp4: false
      dhcp6: false
      parameters:
      mode: balance-xor

      bridges:
      br0:
      interfaces: [ bond0 ]
      dhcp4: false
      dhcp6: false
      parameters:
      forward-delay: 0
      stp: true
      br88:
      interfaces: [ vlan.88 ]
      dhcp4: false
      dhcp6: false
      addresses: []
      parameters:
      forward-delay: 0
      stp: true
      br99:
      interfaces: [ vlan.99 ]
      dhcp4: false
      dhcp6: false
      addresses: []
      parameters:
      forward-delay: 0
      stp: false
      br333:
      interfaces: [ vlan.333 ]
      dhcp4: false
      dhcp6: false
      addresses: []
      parameters:
      forward-delay: 0
      stp: true

      vlans:
      vlan.88:
      id: 88
      link: bond0
      dhcp4: false
      dhcp6: false
      vlan.99:
      id: 99
      link: bond0
      dhcp4: false
      dhcp6: false
      vlan.333:
      id: 333
      link: bond0
      dhcp4: false
      dhcp6: false


      This is all assuming vlan77 is the native vlan so if that isn't the case, some modifications would need to be made. Since vlan77 is native you don't need a separate entry for vlan77.



      I assign all IP addresses via my dhcp servers so my setup is slightly different and I've noticed on some networks I've had to have both the bond and the native vlan set to receive dhcp addressing so you may need to put the same IP address info in both the bond and the native bridge, which, in your case, would look like:



       br0:
      interfaces: [ bond0 ]
      dhcp4: false
      dhcp6: false
      addresses: [10.0.77.2/24]
      gateway4: 10.0.77.1
      nameservers:
      addresses: [10.0.77.1,8.8.8.8]
      search: [domain.tld]
      parameters:
      forward-delay: 0
      stp: true


      But you shouldn't need this as it is not documented and really doesn't make much sense.






      share|improve this answer




























        0














        0










        0









        This is the netplan file I would start out with. I am assuming vlan77 (from 10.0.77.0/24) is the native and the bond is a trunk. I also assume you want the VMs to be located in different vlans:



        #/etc/netplan/01-networkd-vlan-bond.yml
        network:
        version: 2
        renderer: networkd
        ethernets:
        eno1:
        addresses: []
        dhcp4: false
        dhcp6: false
        eno2:
        addresses: []
        dhcp4: false
        dhcp6: false
        eno3:
        addresses: []
        dhcp4: false
        dhcp6: false
        eno4:
        addresses: []
        dhcp4: false
        dhcp6: false
        bonds:
        bond0:
        interfaces: [eno1, eno2, eno3, eno4]
        addresses: [10.0.77.2/24]
        gateway4: 10.0.77.1
        nameservers:
        addresses: [10.0.77.1,8.8.8.8]
        search: [domain.tld]
        dhcp4: false
        dhcp6: false
        parameters:
        mode: balance-xor

        bridges:
        br0:
        interfaces: [ bond0 ]
        dhcp4: false
        dhcp6: false
        parameters:
        forward-delay: 0
        stp: true
        br88:
        interfaces: [ vlan.88 ]
        dhcp4: false
        dhcp6: false
        addresses: []
        parameters:
        forward-delay: 0
        stp: true
        br99:
        interfaces: [ vlan.99 ]
        dhcp4: false
        dhcp6: false
        addresses: []
        parameters:
        forward-delay: 0
        stp: false
        br333:
        interfaces: [ vlan.333 ]
        dhcp4: false
        dhcp6: false
        addresses: []
        parameters:
        forward-delay: 0
        stp: true

        vlans:
        vlan.88:
        id: 88
        link: bond0
        dhcp4: false
        dhcp6: false
        vlan.99:
        id: 99
        link: bond0
        dhcp4: false
        dhcp6: false
        vlan.333:
        id: 333
        link: bond0
        dhcp4: false
        dhcp6: false


        This is all assuming vlan77 is the native vlan so if that isn't the case, some modifications would need to be made. Since vlan77 is native you don't need a separate entry for vlan77.



        I assign all IP addresses via my dhcp servers so my setup is slightly different and I've noticed on some networks I've had to have both the bond and the native vlan set to receive dhcp addressing so you may need to put the same IP address info in both the bond and the native bridge, which, in your case, would look like:



         br0:
        interfaces: [ bond0 ]
        dhcp4: false
        dhcp6: false
        addresses: [10.0.77.2/24]
        gateway4: 10.0.77.1
        nameservers:
        addresses: [10.0.77.1,8.8.8.8]
        search: [domain.tld]
        parameters:
        forward-delay: 0
        stp: true


        But you shouldn't need this as it is not documented and really doesn't make much sense.






        share|improve this answer














        This is the netplan file I would start out with. I am assuming vlan77 (from 10.0.77.0/24) is the native and the bond is a trunk. I also assume you want the VMs to be located in different vlans:



        #/etc/netplan/01-networkd-vlan-bond.yml
        network:
        version: 2
        renderer: networkd
        ethernets:
        eno1:
        addresses: []
        dhcp4: false
        dhcp6: false
        eno2:
        addresses: []
        dhcp4: false
        dhcp6: false
        eno3:
        addresses: []
        dhcp4: false
        dhcp6: false
        eno4:
        addresses: []
        dhcp4: false
        dhcp6: false
        bonds:
        bond0:
        interfaces: [eno1, eno2, eno3, eno4]
        addresses: [10.0.77.2/24]
        gateway4: 10.0.77.1
        nameservers:
        addresses: [10.0.77.1,8.8.8.8]
        search: [domain.tld]
        dhcp4: false
        dhcp6: false
        parameters:
        mode: balance-xor

        bridges:
        br0:
        interfaces: [ bond0 ]
        dhcp4: false
        dhcp6: false
        parameters:
        forward-delay: 0
        stp: true
        br88:
        interfaces: [ vlan.88 ]
        dhcp4: false
        dhcp6: false
        addresses: []
        parameters:
        forward-delay: 0
        stp: true
        br99:
        interfaces: [ vlan.99 ]
        dhcp4: false
        dhcp6: false
        addresses: []
        parameters:
        forward-delay: 0
        stp: false
        br333:
        interfaces: [ vlan.333 ]
        dhcp4: false
        dhcp6: false
        addresses: []
        parameters:
        forward-delay: 0
        stp: true

        vlans:
        vlan.88:
        id: 88
        link: bond0
        dhcp4: false
        dhcp6: false
        vlan.99:
        id: 99
        link: bond0
        dhcp4: false
        dhcp6: false
        vlan.333:
        id: 333
        link: bond0
        dhcp4: false
        dhcp6: false


        This is all assuming vlan77 is the native vlan so if that isn't the case, some modifications would need to be made. Since vlan77 is native you don't need a separate entry for vlan77.



        I assign all IP addresses via my dhcp servers so my setup is slightly different and I've noticed on some networks I've had to have both the bond and the native vlan set to receive dhcp addressing so you may need to put the same IP address info in both the bond and the native bridge, which, in your case, would look like:



         br0:
        interfaces: [ bond0 ]
        dhcp4: false
        dhcp6: false
        addresses: [10.0.77.2/24]
        gateway4: 10.0.77.1
        nameservers:
        addresses: [10.0.77.1,8.8.8.8]
        search: [domain.tld]
        parameters:
        forward-delay: 0
        stp: true


        But you shouldn't need this as it is not documented and really doesn't make much sense.







        share|improve this answer













        share|improve this answer




        share|improve this answer










        answered Jun 5 at 14:14









        Jarad DowningJarad Downing

        1586 bronze badges




        1586 bronze badges































            draft saved

            draft discarded















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1147686%2fneed-to-add-vlans-to-my-netplan-config-with-kvm-bridge-and-bonding%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown









            Popular posts from this blog

            Distance measures on a map of a game The 2019 Stack Overflow Developer Survey Results Are Inmin distance in a graphShortest distance path on contour plotHow to plot a tilted map?Finding points outside of a diskDelaunay link distanceAnnulus from GeoDisks: drawing a ring on a mapNegative Correlation DistanceFind distance along a path (GPS coordinates)Finding position at given distance in a GeoPathMathematics behind distance estimation using camera

            How to get a smooth, uniform ParametricPlot of a 2D Region?How to plot a complicated Region?How to exclude a region from ParametricPlotHow discretize a region placing vertices on a specific non-uniform gridHow to transform a Plot or a ParametricPlot into a RegionHow can I get a smooth plot of a bounded region?Smooth ParametricPlot3D with RegionFunction?Smooth border of a region ParametricPlotSmooth region boundarySmooth region plot from list of pointsGet minimum y of a certain x in a region

            Genealogie vun de Merowenger Vum Merowech bis zum Chilperich I. | Navigatiounsmenü