Creating - not activating - a Bridge Interface breaks DHCP on members

StefanZ
StefanZ Posts: 190  Master Member
First Anniversary 10 Comments Friend Collector First Answer

I was trying out a bridge interface and created one – but did not set it to "activated".

Never the less, the DHCP on member interfaces breaks as soon as the bridge is created.

Is that the expected behaviour?

Accepted Solution

  • zyman2008
    zyman2008 Posts: 199  Master Member
    First Anniversary 10 Comments Friend Collector First Answer
    Answer ✓

    Once the interface join into a ridge interface.

    The original interface function will be turn off and acting like a layer 2 port.

    No matter the bridge interface is active or not.

All Replies

  • zyman2008
    zyman2008 Posts: 199  Master Member
    First Anniversary 10 Comments Friend Collector First Answer
    Answer ✓

    Once the interface join into a ridge interface.

    The original interface function will be turn off and acting like a layer 2 port.

    No matter the bridge interface is active or not.

  • StefanZ
    StefanZ Posts: 190  Master Member
    First Anniversary 10 Comments Friend Collector First Answer

    Thanks for the clarification.

    This should somehow denoted in the interface, since it is different to pretty much any other interfcace part.

    Knowing this and reading the manual…

    When you create a bridge interface, the Zyxel Device removes the members' entries from the routing
    table and adds the bridge interface's entries to the routing table.

    … confirms it, but it sure could be highlighted a bit.

    Especially since this can completely break your network access to the device.

Security Highlight