| Commit message (Collapse) | Author | Age |
| | |
|
| |
|
|
| |
While here, include fcntl.h in if.c for older environments.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
When passing PARSE_STRING_NULL we expect to store the string
NULL terminated. As such, allocate space for it an ensure we have
space for it.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
I get bored of adding similar code from time to time just to
aid debugging, so let's just add it in.
Someone else might find it useful too.
|
| |
|
|
|
|
|
|
|
|
| |
Split ipv6_addaddrs out so ipv6_doaddr can operate on a single address.
Call this when deprecating delegated addresses to avoid calling
ipv6_addaddrs.
This allows a more simple ipv6_addaddrs that doesn't need to test
which address collection we are deleting from and removes DHCPv6
specific code from the generic IPv6 module.
|
| |
|
|
|
| |
Be sure to remove the address using the right TAILQ member.
While here, simplify the initialisation of pd_pfxs.
|
| |
|
|
| |
As such it should be domain and not ip6address.
|
| |
|
|
|
|
|
| |
And as such just log infinite lease rather than an arbitary
number.
Backported from d7e68001.
|
| |
|
|
| |
Just to be more RFC conformant.
|
| |
|
|
| |
Thanks to Andreas
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
We should keep DHCP6 running even if routers expire or link changes.
This is noted in RFC3315 18.1.2:
If the client receives no responses before the message transmission
process terminates, as described in section 14, the client SHOULD
continue to use any IP addresses, using the last known
lifetimes for those addresses, and SHOULD continue to use any other
previously obtained configuration parameters.
|
| |
|
|
| |
As not all are of equal size.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
We could do ((char *)rtm) + rtm->rtm_msglen but that looks
more ugly than rtm + 1.
|
| |
|
|
| |
Doubtful these lengths would be invalid, but you never know.
|
| |
|
|
|
|
| |
While here, clarify the BPF instruction space needed for ARP as it
could overflow in the very unlikely event we ARP for three
addresses at the same time.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
dhcpcd only checks that the prefix length of the exclusion
matches the prefix length of the ia and equals the length of the
data in the option.
This could potentially overrun the in6_addr structure.
This is fixed by enforcing RFC 6603 section 4.2 option limits
more clearly.
Thanks to Maxime Villard <max@m00nbsd.net> for finding this.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
RTM_IFINFO messages now send the un-molested link status to
the main carrier handler which no longer polls on LINK_UNKNOWN.
Instead, we check carrier status directly, which if unsupported
we instead interface flags.
This is 2019, all interface drivers should report link status
correctly via RTM_IFINFO messages and trying to constantly work
around this is error prone and time consuming.
|
| | |
|
| |
|
|
|
| |
It has to work for wireless interfaces, but we have no idea
about other interfaces. So test valid carrier for unknown.
|
| | |
|
| | |
|
| |
|
|
| |
... before trying to process the received BOOTP message on it.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The error is "No route to host".
OpenBSD does not support IPv6 address sharing, so it's no biggie.
As such, only log an error when debugging.
|
| |
|
|
|
| |
FreeBSD it seems sensibly uses a monotonic clock for IPv6 lifetimes
but the others use the wall clock.
|
| | |
|
| |
|
|
|
| |
Let's not pretend these exist and adjust existing #ifdefs
to compensate.
|
| |
|
|
|
|
|
|
|
| |
I suspect this is because the broadcast address needs to be set
after the address, but RTM_NEWADDR is triggered from adding the
address.
While here, actually set the broadcast address requested
for IPv4 and simplify the code.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Just to be on the safe side as it is per interface ....
|
| | |
|