Packet Filter Linux ignore VLAN tagged packets #119
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
svenauhagen
force-pushed
the
feature/vlanfilter
branch
from
e26caa3
to
949e441
Compare
If you define kea dhcp on an untagged interface that also has a tagged vlan interface on top, it will see both dhcp packets (eth0 and eth0.10). Linux has a feature for auxiliary data on raw sockets which contains data about the vlan of the packet received. Kea should only answer packets without a vlan in the aux data, since those are the data send to the attached interface. vlan data are missing on the intended interface eth0.10 but set on eth0 for the same packet. There was a discussion about this here: http://kea-users.7364.n8.nabble.com/Kea-users-KEA-DHCP-and-VLANS-td1618.html Signed-off-by: Sven Auhagen <[email protected]>
svenauhagen
force-pushed
the
feature/vlanfilter
branch
from
949e441
to
d0e1bb3
Compare
|
Very thanks. There was a discussion about this here: |
|
Hi, ah I did not see that ticket, thanks. |
|
Yes. |
|
Great, thank you for testing! |
|
Hello, Any reason why the merge of this task is still pending? |
|
Any ETA on getting a release with this fixed merged in ? |
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.
If you define kea dhcp on an untagged interface that also has a tagged
vlan interface on top, it will see both dhcp packets (eth0 and eth0.10).
Linux has a feature for auxiliary data on raw sockets which contains
data about the vlan of the packet received.
Kea should only answer packets without a vlan in the aux data,
since those are the data send to the attached interface.
vlan data are missing on the intended interface eth0.10 but set on eth0
for the same packet.
There was a discussion about this here:
http://kea-users.7364.n8.nabble.com/Kea-users-KEA-DHCP-and-VLANS-td1618.html
Signed-off-by: Sven Auhagen [email protected]