#16348 closed bug (invalid)
Network App - Inconsistent DHCP naming
| Reported by: | Coldfirex | Owned by: | pulkomandy |
|---|---|---|---|
| Priority: | low | Milestone: | Unscheduled |
| Component: | Preferences/Network | Version: | R1/beta2 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Howdy, I noticed that under IPv4 the setting for DHCP is labeled as "DHCP" correctly. However, under IPv6 its labeled as "Automatic". We should have these be the same.
Change History (5)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 by , 4 years ago
If that's the case should'nt we update the IPv4 section to say Automatic instead of DHCP then?
comment:4 by , 4 years ago
No, because (1) I'm not sure we even implement that addressing mode, and (2) it's only a fallback; DHCP is the default way of getting an address automatically. That is not true on IPv6.
comment:5 by , 4 years ago
Got it. As a network admin I'm ashamed to say I've always glazed over IPv6 since I've never had any hands-on with it yet.
Note:
See TracTickets
for help on using tickets.
It should be "Automatic" because it can also be SLAAC (for IPv6) or the equivament for IPv4 with 169.something addresses, when no DHCP server is available.