-
Notifications
You must be signed in to change notification settings - Fork 97
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
IPv6#split #108
Comments
The concept is different in IPv6, that is not to say that there is no use for them.
Bearing in mind that the smallest common Address size is a /64, so you should not split that into smaller bits.
…Sent from my iPhone
On 8 Jan 2019, at 23:19, Michael Richardson ***@***.***> wrote:
Is there any reason why the various subnetting, supernet, split() functions are IPv4 only?
Is it just missing a v6 implementation, or is there something else deeper that makes it hard?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Mike Simkins <[email protected]> wrote:
The concept is different in IPv6, that is not to say that there is no
use for them.
If I have a RIR assigned /32, creating subnets of /48s and /56s
to hand out to customers/networks is pretty much the same as in IPv4.
Bearing in mind that the smallest common Address size is a /64, so you
should not split that into smaller bits.
Yes, I'm pretty much in the middle of the ongoing/continuous IETF 6man debate
on that :-)
|
If you are interested in IPv6 functionality I have forked this into a new repo and gem: It just copies the IPv4 functions to the IPv6 library. |
Thank you, I will look at it.
I did the split work as well, it's at:
https://github.com/AnimaGUS-minerva/fountain/blob/master/app/models/acp_address.rb
I put it into my subclass of IPaddress::IPv6, which does other specific
allocation work. I'll see if I can use your code.
In the end, I found working with IPaddress a bit obtuse as it does not keep
the IPv6 in a binary format. I find my code going to/from binary and
"native" hex string representation a lot just so that it can toggle bits
here and there. It just seemed wrong.
BTW: acp_address implements one of the address modes of
draft-ietf-anima-autonomic-control-plane.
…--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there any reason why the various subnetting, supernet, split() functions are IPv4 only?
Is it just missing a v6 implementation, or is there something else deeper that makes it hard?
The text was updated successfully, but these errors were encountered: