Skip to content

gk: only forward to known neighbors#522

Merged
AltraMayor merged 2 commits intomasterfrom
no-neigh
Aug 16, 2021
Merged

gk: only forward to known neighbors#522
AltraMayor merged 2 commits intomasterfrom
no-neigh

Conversation

@AltraMayor
Copy link
Owner

When a Gatekeeper server is going to forward a packet from an interface to a neighbor of the other interface, Gatekeeper looks up the MAC address of that neighbor in the known-neighbor subtable of the FIB.

Gatekeeper has wrongly assumed that any neighbor is always known. This patch drops packets destined to unknown neighbors.

When a Gatekeeper server is going to forward a packet from
the front interface to a neighbor of the back interface,
Gatekeeper looks up the MAC address of that back neighbor in
the known-neighbor subtable of the FIB.

Gatekeeper has wrongly assumed that any neighbor is always known.
This patch drops packets destined to unknown back neighbors.

This problem was first reported in issue #519.
@AltraMayor AltraMayor added the bug label Aug 13, 2021
@AltraMayor AltraMayor added this to the First deployment milestone Aug 13, 2021
When a Gatekeeper server is going to forward a packet from
the back interface to a neighbor of the front interface,
Gatekeeper looks up the MAC address of that front neighbor in
the known-neighbor subtable of the FIB.

Gatekeeper has wrongly assumed that any neighbor is always known.
This patch drops packets destined to unknown front neighbors.
@AltraMayor
Copy link
Owner Author

Tested on XIA1 server.

@AltraMayor AltraMayor merged commit f742bbd into master Aug 16, 2021
@AltraMayor AltraMayor deleted the no-neigh branch August 16, 2021 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant