Hi Jon, Making the API call using the sw_if_index of the interface with enable=0 will remove the interface from the bridge domain. The interface will then be back in L3 mode, as I implied from my original reply.
Regards, John From: Jon Loeliger [mailto:j...@netgate.com] Sent: Tuesday, March 14, 2017 3:23 PM To: John Lo (loj) <l...@cisco.com> Cc: vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] Some L2 Bridge API Questions On Tue, Mar 14, 2017 at 1:50 PM, John Lo (loj) <l...@cisco.com<mailto:l...@cisco.com>> wrote: Hi Jon, Hi John, You make a valid point about the name chosen for the API param “enable”. Rather than argue about the best name, let me describe how it works. Sure! The API is intended to enable or disable an interface in L2 bridging mode. By disable, or enable=0, it will put the interface back to L3 mode which is the default mode for an interface. If the API is called with enable=1 while the interface is already in L2 bridging mode, the code would actually perform a disable followed by enable of the interface’s current bridging mode as specified. Ah, OK. So at that time (the re-enable), and differing parameter would being to take effect. So simply re-issuing the API call with the new parameters and an "enable" will be sufficient. So there isn't a way to remove the bridge from the interface once it has been associated the first time? Or will that be accomplished by actually removing the bridge from the bridge table? Even if the bridge_domain ID is left dangling on the interface? I take your point and will remember to update its comment in the API file, including fix the typo for “bridge”. Thanks! jdl
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
