-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Liqo-route: liqo.host forward #1979
Merged
Merged
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
Hi @cheina97. Thanks for your PR! I am @adamjensenbot.
Make sure this PR appears in the liqo changelog, adding one of the following labels:
|
cheina97
force-pushed
the
frc/route
branch
3 times, most recently
from
September 4, 2023 15:06
4e5fa2c
to
60938a2
Compare
/rebase test=true |
cheina97
force-pushed
the
frc/route
branch
2 times, most recently
from
September 4, 2023 15:42
c25a254
to
d9bd43b
Compare
/rebase test=true |
adamjensenbot
force-pushed
the
frc/route
branch
from
September 4, 2023 15:43
d9bd43b
to
68d9be0
Compare
/rebase test=true |
aleoli
approved these changes
Sep 6, 2023
cheina97
force-pushed
the
frc/route
branch
2 times, most recently
from
September 7, 2023 07:58
c69f535
to
9c60e4c
Compare
/rebase test=true |
adamjensenbot
force-pushed
the
frc/route
branch
from
September 7, 2023 08:05
9c60e4c
to
5c09a2a
Compare
/merge |
adamjensenbot
added
merge-requested
Request bot merging (automatically managed)
and removed
merge-requested
Request bot merging (automatically managed)
labels
Sep 7, 2023
/merge |
adamjensenbot
added
the
merge-requested
Request bot merging (automatically managed)
label
Sep 7, 2023
adamjensenbot
removed
the
merge-requested
Request bot merging (automatically managed)
label
Sep 7, 2023
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.
Description
This PR adds INPUT, FORWARDING, and OUTPUT rules in liqo-gateway (checks the image)
Liqo-gateway is able to put these rules on the host network namespace of the node where the liqo-gateway is scheduled.
This solves an issue with some calico configurations where the CNI blocks the traffic from liqo.host to the liqo.vxlan interface.