Hi Andrew - are you telling me Wikipedia is not infallible? :-) So I agree that stateless DHCPv6 should generally suffice. However, RDNSS support would be nice. Some good use cases:
1) The Internet Of Things - In the embedded market, full DHCPv6 support would be harder - RDNSS would be much more appealing
2) Labs/Test environments - Anything to facilitate the rapid deployment of test/lab networks would be a boon. While DHCP/DHCPv6 isn't hard to setup, using RAs is brain dead and the ability to add a simple option to include DNS would be fantastic.
3) SOHO - Again, for simple environments this would be a plus. Also, when our Refridgerators and Coffee Makers join the network I would think RDNSS would be easier than stateless DHCPv6. Did you have a chance to see how the Internet of Things will hook us up:
3) SOHO: not sure. Assuming the discussion is about the coffee machines (the consumer general purpose OSes would be covered in (2) above) - would depend which kind of code they will run. With the advent of the SoCs like RaspberryPi, the concern about the a few bytes of code space required to run DHCPv6, would no longer hold imho. And I'd be willing to bet that the coffee machine producers will use linux-based hardware to lower the development costs and TTM. What do you think ?
A couple of comments/questions about the implementation:
As for the difficulty of the DHCPv6 implementation: here's a relevant "server" part that I used in my CL12 San Diego "network hijack" demo. Granted, it's a quick and ugly hack script that used scapy libs (and it is only the server side, I did not write the client side code, and in C it would be a bit more verbose of course):
But, just using this to illustrate that for the stateless DHCPv6 the coding is not too hard. And, unlike the RDNSS, it's fully in userspace on the clients. Which may play a role if any tweaks/changes are needed to implementation.
FWIW, I realise the above looks a like a giant excuse "why we don't do it", I ought to mention that last year I did make an experimental image that had a proof-of-concept code for RFC6106, but had a bit of a hard time gathering the business case that would allow me to solicit for any "official" efforts in this area. If you have or have had real projects that would be critically dependent on RDNSS, I'd be very interested - ping me via email with that.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...