[#244] Add feature in order to use loopback as uplink interface in dhcrelay agent #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request introduces 1 alert when merging ce6131e into 31e68e5 - view on LGTM.com new alerts:
|
|
The part of this patch related to dhcrelay will not be accepted. See 4.4.3 release notes. Relevant part:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ignore the fatal logging (Example: "Unsupported device type 128 for lo") in common/lpf.c file, add the case for ARPHRD_LOOPBACK type and handle as a ARPHRD_ETHER type interface.
When you specify the loopback interface as uplink using -U option and this interface has one more ip address, except the link local (127.0.0.1/8), use this ip address as outbound uplink "giaddr" in "DHCP Option 82" described in RFC3527.