[ZBXNEXT-3752] Enable IPv6 by default on zabbix server Created: 2017 Mar 22 Updated: 2017 Mar 22 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Installation (I), Proxy (P), Server (S) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Minor |
Reporter: | Andrea Biscuola (Inactive) | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 3 |
Labels: | compatibility, ipv6, network | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
IPv6 is already used by a lot of enterprises in their infrastructure. It's in real world use from enough time ago that i don't think it make sense to have the support disabled by default, (at least on the server). These days all the operating systems the zabbix server run on support IPv6 out of the box and we can also think to remove a lot of preprocessor code that check for this. Also, we use LibCURL that will, probably, have IPv6 always enabled |
Comments |
Comment by richlv [ 2017 Mar 22 ] |
could you please clarify, is this about always compiling in ipv6 support - thus not by default, not making it configurable anymore ? |
Comment by Andrea Biscuola (Inactive) [ 2017 Mar 22 ] |
richlv Maybe the description is a bit misleading indeed . What i meant was that we always compile with ipv6 support, thus removing the need of configuring it. The only weird bit will be to check what can be involved on the agent side (that still support really old operating systems, in particular windows 2000). |
Comment by richlv [ 2017 Mar 22 ] |
what about compiling on older aix/solaris systems ? would ipv6-enabled server/proxy work perfectly there ? |
Comment by Andrea Biscuola (Inactive) [ 2017 Mar 22 ] |
Jep, also true. Definitely should be investigated properly if we decide to see if it's worthwhile. |