Skip to content
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

fix issue #4025: 6rd with single /64 prefix #4635

Merged
merged 1 commit into from
Jan 25, 2021

Conversation

mhofer117
Copy link
Contributor

Builds upon the 6rd routing fixes discussed in https://forum.opnsense.org/index.php?topic=20260.0

Instead of setting the calculated /64 subnet length on the _stf interface, I set the original ISP provided subnet length.
And change the gateway to be inside the ISP provided prefix instead of the calculated /64.

wan address will still be the same but the wider subnet solves any routing issues with single /64 prefixes.

@fichtner fichtner self-assigned this Jan 25, 2021
@fichtner fichtner merged commit 866e8f2 into opnsense:master Jan 25, 2021
@fichtner
Copy link
Member

Merging as discussed, thank you ❤️

@marjohn56
Copy link
Member

Got something for you to have a look at. I'll be on IRC tomorrow morning, DHCPDv6 needed a rethink. :)

fichtner pushed a commit that referenced this pull request Jan 26, 2021
Builds upon the 6rd routing fixes discussed in https://forum.opnsense.org/index.php?topic=20260.0

Instead of setting the calculated /64 subnet length on the _stf interface, I set the original ISP provided subnet length.
And change the gateway to be inside the ISP provided prefix instead of the calculated /64.

wan address will still be the same but the wider subnet solves any routing issues with single /64 prefixes

(cherry picked from commit 866e8f2)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants