TechnitiumSoftware
[Feature Request] Support DHCPv6
The usage of IPv6 is increasing and many ISP now provide IPv6 to their customers so it would be useful also to have support for DHCPv6
Thanks for the feature request. Will add this in the to-do list. It may take some time though since there are many features already in pipeline.
Agreed. I actually just realized this does not have DHCPv6 and its something i'm working on implementing in my environment. Hoping this will be added eventually.
Technitium is almost the perfect solution for my homelab (as well as SMB).
All it is lacking is DHCP6, and more DHCP options.
Technitium is almost the perfect solution for my homelab (as well as SMB).
All it is lacking is DHCP6, and more DHCP options.
Thanks for the post. What DHCP options are you looking for? There is plan to implement a few options in next couple of releases so any specific option that is required can be accommodated.
Technitium is almost the perfect solution for my homelab (as well as SMB). All it is lacking is DHCP6, and more DHCP options.
Thanks for the post. What DHCP options are you looking for? There is plan to implement a few options in next couple of releases so any specific option that is required can be accommodated.
Of course, anytime. These are the options that I can see as very important:
- 4 - time server
- 60 - vendor type/ID
- 66 - tftp (PXE booting)
- 67 - filename (specify file for PXE booting)
- 82 - WLAN Controller
- 138 - discovery services (used by some WiFi Access points so they can find their WLAN controller - TP-Link Omada, UniFi, etc.)
These are the options that I can see as very important:
4 - time server
60 - vendor type/ID
66 - tftp (PXE booting)
67 - filename (specify file for PXE booting)
82 - WLAN Controller
138 - discovery services (used by some WiFi Access points so they can find their WLAN controller - TP-Link Omada, UniFi, etc.)
First 4 options are already available. Will try to add the other 2.
These are the options that I can see as very important:
- 4 - time server
- 60 - vendor type/ID
- 66 - tftp (PXE booting)
- 67 - filename (specify file for PXE booting)
- 82 - WLAN Controller
- 138 - discovery services (used by some WiFi Access points so they can find their WLAN controller - TP-Link Omada, UniFi, etc.)
First 4 options are already available. Will try to add the other 2.
Awesome! Thanks!
82 - WLAN Controller
138 - discovery services (used by some WiFi Access points so they can find their WLAN controller - TP-Link Omada, UniFi, etc.)
@CyberMainstay can you confirm the options above?
- Option 82 is Relay Agent Information, nothing about WLAN.
- Option 138 is CAPWAP Access Controller addresses.
You might want to refer to this list of options here.
- 82 - WLAN Controller
- 138 - discovery services (used by some WiFi Access points so they can find their WLAN controller - TP-Link Omada, UniFi, etc.)
@CyberMainstay can you confirm the options above?
* Option 82 is [Relay Agent Information](https://www.rfc-editor.org/rfc/rfc3046.html), nothing about WLAN. * Option 138 is [CAPWAP Access Controller addresses](https://www.rfc-editor.org/rfc/rfc5417.html).You might want to refer to this list of options here.
Option 138 is specifically used by TP-Link Omada to help APs find the WLAN controller. For some reason, my mind is drawing a blank on why I suggest option 82, but I've run across it before with another WLAN controller vendor that used it.
Option 138 is specifically used by TP-Link Omada to help APs find the WLAN controller. For some reason, my mind is drawing a blank on why I suggest option 82, but I've run across it before with another WLAN controller vendor that used it.
Thanks for the confirmation. Will get the option 138 added.
Option 82 seems to be too specialized that is supposed to be used by ISPs to communicate between the DHCP server and DHCP Relay Agents so does not seem to be useful for this project.
Any update on implementing DHCP6?
The next update will include syslog support and the update after that is planned for DHCPv6. So it could be 3-4 months from now depending on how it goes.
Any update on implementing DHCP6?
The next update will include syslog support and the update after that is planned for DHCPv6. So it could be 3-4 months from now depending on how it goes.
That is awesome to hear! I'll be greatly looking forward to trying it out. DNS resolution to IPv6 releases will be a very welcomed addition!
Heya @ShreyasZare, Wanted to ask how the progress on implementing ipv6 dhcp support is going.
Heya @ShreyasZare, Wanted to ask how the progress on implementing ipv6 dhcp support is going.
Thanks for asking. It is getting a bit delayed due to time constrains since a few months. So, it may take some more time.
Heya @ShreyasZare, Wanted to ask how the progress on implementing ipv6 dhcp support is going.
Thanks for asking. It is getting a bit delayed due to time constrains since a few months. So, it may take some more time.
Heya @ShreyasZare, Just checking in again to ask if there was progress on ipv6. Also, just curious on if you accept funding to prioritize features?
Heya @ShreyasZare, Just checking in again to ask if there was progress on ipv6.
@josemanimala Thanks for asking. The DNS server clustering feature is now prioritized over DHCPv6. So, it will take some more time. Once the clustering feature is implemented for DNS and server settings, the DHCP server is planned to have a major upgrade which will include making scopes more flexible, adding DHCPv6 support and adding failover support.
Also, just curious on if you accept funding to prioritize features?
The project development is not my full time work, as its done after I get time from my day job. So its not feasible to commit time for some funding.
@ShreyasZare Thank you. Will be patiently waiting for the overhaul. IPv6 became more relevant recently with AWS starting to charge for IPv4 and most ISP networks starting to support it. I wanted to make sure that I was ready to switch to IPv6 when the time came :).