Skip to content

Conversation

@rcgoodfellow
Copy link
Contributor

@rcgoodfellow rcgoodfellow commented Dec 19, 2025

@rcgoodfellow rcgoodfellow added this to the 18 milestone Dec 19, 2025
@rcgoodfellow rcgoodfellow marked this pull request as ready for review December 19, 2025 07:54
@rcgoodfellow
Copy link
Contributor Author

Took this for a spin in a4x2, tunnel routing still working and no crashes on sync of v6 routes to v2b

root@g0:~# ./opteadm dump-v2b
Virtual to Boundary Mappings
======================================================================

IPv4 mappings
----------------------------------------------------------------------
TUNNELED PREFIX  BOUNDARY IP             VNI
0.0.0.0/0        fdb1:c4dc:978c:54af::1  99
0.0.0.0/0        fddf:dd88:4ccd:6bbe::1  99

IPv6 mappings
----------------------------------------------------------------------
TUNNELED PREFIX  BOUNDARY IP             VNI
fdfd::/56        fddf:dd88:4ccd:6bbe::1  99

Copy link
Collaborator

@FelixMcFelix FelixMcFelix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad to see on Matrix that everything works now!

Comment on lines +83 to +84
poptrie = { git = "https://github.com/oxidecomputer/poptrie", branch = "ry/8-byte-key-alignment" }
#poptrie = { git = "https://github.com/oxidecomputer/poptrie", branch = "main" }
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving a reminder to unset this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Setting Virt-to-Boundary mappings for IPv6 inner addresses kernel panics due to alignment constraints

3 participants