Lines Matching refs:we
219 addresses, we must have multiple IP logical interfaces per IA
222 - Because we need to support multiple addresses (and thus multiple
243 Because we need to have multiple IP logical interfaces (LIFs) for a
244 single identity association (IA), we should not store all of the
247 For DHCPv6, we will need to keep LIFs on a single IP physical
263 represent these groupings, we will use a new dhcp_lease_t structure.
272 For all of these new structures, we will use the same insert/hold/
283 For DHCPv6, we need to track multiple LIFs per lease (IA), but we
285 list linkage for each LIF, we can observe that a LIF is on exactly
291 When removing a LIF from the system, we need to decrement the count
296 When removing a lease from a state machine, we need to dispose of
298 a state machine, then all that we can do is canonize the LIF
366 Obviously, we need some DHCPv6 packet data structures and
468 The first thing that we can do is eliminate the need for the
491 gone. Instead, we always receive, and we dispatch the packets as
493 Reply when in BOUND state, we know it's a duplicate, and we can
502 To simplify this, we will open at most one DLPI stream on a PIF, and
510 sockets. Now that we keep track of this in a simpler manner, we no
517 LIF mechanism keeps track of the interface state. And since we have
518 separate lease structures, and INFORM doesn't acquire a lease, we no
529 only if we have a viable local source address. This means using
530 SIOCGDSTINFO each time we try to send unicast. Next, the server may
532 and if we were actually using unicast in our messages to the server,
533 then we need to forget the unicast address, switch back to
541 Because IP_PKTINFO (PSARC 2006/466) has integrated, we could go a
547 In the case of DHCPv6, we already have IPV6_PKTINFO, so we will pave
578 and that server either responds to our requests or doesn't, we can
585 an optimization, we should begin attempting to renew any IAs
589 - When a T1 lease timer expires and we're in RENEWING or REBINDING
593 - At each retransmit timeout, we should check to see if there are
599 - When we reach T2 on any IA and we're in BOUND or RENEWING state,
600 enter REBINDING state. At this point, we have a choice. For
601 those other IAs that are past T1 but not yet at T2, we could
608 - When a T2 lease timer expires and we're in REBINDING state, just
622 on one IA, the server will suddenly start responding when we attempt
631 messages. The DHCPv6 method is a cleaner design, so we will change
669 system, and that if we write before shutdown, we have to cope
673 For DHCPv6, we need to try to keep our stable DUID and IAID values
691 attempt fails with EROFS, we will set a timer for 60 second
693 that it just never succeeds or that we're rebooted before root
695 up once a minute and, ultimately, we'll choose a different DUID on
696 next start-up, and we'll thus lose our leases across a reboot.
700 we will use two strategies. First the IAID value for a given
703 we will save off the IAID we choose in a single /etc/dhcp/iaid file,
793 - When we are constructing an automatic, stable DUID for our own
794 identity, we prefer to use a DUID-LLT if possible. This is done
799 - When we translate a user-configured DUID from
800 /etc/default/dhcpagent into a binary representation, we may have
801 to deal with a physical interface name. In this case, we must
804 - As part of the PIF data structure initialization, we need to read
895 if_{t1,t2,lease} to hold the relative timer values, we will
1003 configured prefix, then we'll prefer that over other addresses. If
1005 DHCPv6, then dynamic. Finally, if there are still multiples, we'll
1060 - If Renew/Rebind doesn't mention one of our leases, then we need to
1069 - If we get "UseMulticast" when we were already using multicast,
1106 extensions. If we associate the DUID with the zone identifier or
1107 name through an extension, then we have a really simple way of
1126 If we implement FQDN in the future, it may be useful to explore some
1149 for IPv4. (For the latter, if we fail to do that, it will likely
1154 If we implement somewhere other than dhcpagent, then we need to give
1170 other than leaving the existing dhcpagent code untouched. If we do
1171 that, then we end up with two implementations that do many similar