Opened 14 years ago
Last modified 4 years ago
#7228 new bug
RFC: BNetworkInterfaceAddress needs to store auto-configuration flags
Reported by: | kallisti5 | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1.1 |
Component: | Network & Internet/Stack | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
BNetworkInterfaceAddress needs to store auto-configuration flags instead of BNetworkInterface.
see the following for an example...
How would you disable either IPv6 *or* IPv4 auto-configuration when the auto-configure flag is only set on the interface?
Scenario:
- I have a blank IPv6 address and a dhcp acquired IPv4 addr.
- I check auto-configure flag for interface
- I from that view... the IPv6 address could be either "configuring" or "None" (configured for no address)
The same situation applies when IPv6 is swapped with IPv4
Change History (3)
comment:1 by , 14 years ago
Description: | modified (diff) |
---|
comment:2 by , 14 years ago
comment:3 by , 4 years ago
Milestone: | R1 → R1.1 |
---|
Note:
See TracTickets
for help on using tickets.
I've already defined the flags in net/if.h, and there is a field in ifaliasreq already, too - they are just not maintained yet (they need to be stored in the stack's InterfaceAddress as well), and not forwarded to BNetworkInterfaceAddress either.
Someone just needs to implement it - it shouldn't be too hard either :-)