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

Jool should whine when a non-zero suffix is inserted to the IPv6 pool. #77

Closed
ydahhrk opened this Issue Feb 21, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@ydahhrk
Member

ydahhrk commented Feb 21, 2014

This is how it normally goes:

# modprobe jool pool6=64::/32

If a IPv4 packet with destination address 192.0.2.1 arrives, Jool will translate it into a packet with destination address 64:192.0.2.1:: as expected.

That might give the user the impression that if s/he does this,

# modprobe jool pool6=64::1/32

then the same address will be translated into 64:192.0.2.1::1.

However, RFC 6052 says

"the remaining bits of the address constitute the suffix. These bits are reserved for future extensions and SHOULD be set to zero."

so the address is STILL supposed to be translated into 64:192.0.2.1::.

Jool does that correctly, but the fact that it allows the user to insert the non-zero suffix (and still prints it when the userspace app requests the IPv6 pool) is confusing.

So we should bounce back the suffix to the user and force him/her to input a "suffixless prefix".

@ydahhrk ydahhrk modified the milestone: 3.1.2 Feb 21, 2014

@ydahhrk

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Mar 6, 2014

Member

Fixed and collapsed to the master branch. Closing.

Member

ydahhrk commented Mar 6, 2014

Fixed and collapsed to the master branch. Closing.

@ydahhrk ydahhrk closed this Mar 6, 2014

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