[201811][dhcp-relay]: Launch DHCP Relay On L3 Vlan Only #7085
Conversation
jleveque
changed the title
|
@tahmed-dev: Can you confirm that this change is already in all upstream branches? I don't see any mention of it in your description. |
jleveque
changed the title
@jleveque: it is included in 20201231 and 20191130 branches. |
Great. And master, I assume? |
Yes, it is in master. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
2 similar comments
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tahmed-dev
force-pushed
the
taahme/port-dhcp-l2-vlan-fix
branch
2 times, most recently
from
7ac7e9a
to
689545f
Compare
Recent changes brought l2 vlan concept which does not have DHCP clients behind them and so DHCP relay is not required. Also, dhcpmon fails to launch on those vlans as their interfaces lack IP addresses. This PR limits launch of both DHCP relay and dhcpmon to L3 vlans only. singed-off-by: Tamer Ahmed <tamer.ahmed@microsoft.com>
tahmed-dev
force-pushed
the
taahme/port-dhcp-l2-vlan-fix
branch
from
689545f
to
a8c7f45
Compare
tahmed-dev
changed the title
Recent changes brought l2 vlan concept which does not have DHCP
clients behind them and so DHCP relay is not required. Also,
dhcpmon fails to launch on those vlans as their interfaces
lack IP addresses. This PR backposts #6527 that limits launch
of both DHCP relay and dhcpmon to L3 vlans only.
original-pr: #6527
singed-off-by: Tamer Ahmed tamer.ahmed@microsoft.com
Why I did it
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)