<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dhcpcd.git, branch dhcpcd-7.1.0</title>
<subtitle>DHCP / IPv4LL / IPv6RA / DHCPv6 client
</subtitle>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/'/>
<entry>
<title>Release dhcpcd-7.1.0</title>
<updated>2019-01-22T14:53:45+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-22T14:53:45+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=e261544746104690723a1d325ef0182a0570a1b2'/>
<id>e261544746104690723a1d325ef0182a0570a1b2</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>BSD: Turn on SO_RERROR for all sockets</title>
<updated>2019-01-22T14:51:42+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-22T14:51:42+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=6fd052590f00d8e531402600492ef54ca9457614'/>
<id>6fd052590f00d8e531402600492ef54ca9457614</id>
<content type='text'>
So we can detect IPv6ND or DHCPv6 overflow as well as route(4)
overflow.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
So we can detect IPv6ND or DHCPv6 overflow as well as route(4)
overflow.
</pre>
</div>
</content>
</entry>
<entry>
<title>IPv4LL: prior prior commit for non NetBSD OS's</title>
<updated>2019-01-17T11:49:52+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-17T11:49:52+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=0efd42cd3bb1cf11e4cb0474b10ccdba40643168'/>
<id>0efd42cd3bb1cf11e4cb0474b10ccdba40643168</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>IPv4LL: Preserve address when carrier drops</title>
<updated>2019-01-17T11:44:08+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-17T11:44:08+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=466fddaeedcdd6fd23b0b33f260243867bcb11bd'/>
<id>466fddaeedcdd6fd23b0b33f260243867bcb11bd</id>
<content type='text'>
Apple Conformance testing now requires this.
However, if associated SSID changes on wireless networks,
any remembered address is reset.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Apple Conformance testing now requires this.
However, if associated SSID changes on wireless networks,
any remembered address is reset.
</pre>
</div>
</content>
</entry>
<entry>
<title>BSD: Fix UP/DOWN for interfaces which dont' report media changes</title>
<updated>2019-01-14T12:57:37+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-14T12:57:37+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=751efa515f8c1000f2bda9023bff7a8f80761db3'/>
<id>751efa515f8c1000f2bda9023bff7a8f80761db3</id>
<content type='text'>
Carrier UP/DOWN state is handled by media change events on BSD.
When the carrier state changes, it's always to LINK_STATE_DOWN or
LINK_STATE_UP.
If we receive LINK_STATE_UNKNOWN from RTM_IFINFO it means the
interface doesn't change media change events and as such won't
report carrier state changes. In this instance, we can only rely
on IFF_UP being set, which is the same condition dhcpcd needs
for LINK_STATE_UP.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Carrier UP/DOWN state is handled by media change events on BSD.
When the carrier state changes, it's always to LINK_STATE_DOWN or
LINK_STATE_UP.
If we receive LINK_STATE_UNKNOWN from RTM_IFINFO it means the
interface doesn't change media change events and as such won't
report carrier state changes. In this instance, we can only rely
on IFF_UP being set, which is the same condition dhcpcd needs
for LINK_STATE_UP.
</pre>
</div>
</content>
</entry>
<entry>
<title>FreeBSD: Fix bogus RTM_DELADDR messages from affecting DHCP lease</title>
<updated>2019-01-12T13:36:01+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-12T13:36:01+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=ca9f7f084f3be88c83fa6f346ac5cccc20ebe80b'/>
<id>ca9f7f084f3be88c83fa6f346ac5cccc20ebe80b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>configure: --with-udev explicity requires libudev to be present</title>
<updated>2019-01-11T12:39:33+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-11T12:39:33+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=18b036c11bc576e244bfff96924a2ada69d5ab05'/>
<id>18b036c11bc576e244bfff96924a2ada69d5ab05</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>configurfe: Remove extra --includedir. It's not hit anyway.</title>
<updated>2019-01-11T12:30:46+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-11T12:30:46+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=9dd073782d83e22b682afb4d4f063a3db7ba7c40'/>
<id>9dd073782d83e22b682afb4d4f063a3db7ba7c40</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>ip6: Install not on link routes with a gateway of the router</title>
<updated>2019-01-06T10:10:59+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-06T10:10:59+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=d292d54e9032ab27ba68f66010c20707cf5925c4'/>
<id>d292d54e9032ab27ba68f66010c20707cf5925c4</id>
<content type='text'>
This allows a secondary router to broadcast prefixes it controls
without being a default router itself.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This allows a secondary router to broadcast prefixes it controls
without being a default router itself.
</pre>
</div>
</content>
</entry>
<entry>
<title>ip6: Implement IPv6 address sharing</title>
<updated>2019-01-05T11:42:12+00:00</updated>
<author>
<name>Roy Marples</name>
<email>roy@marples.name</email>
</author>
<published>2019-01-05T11:42:12+00:00</published>
<link rel='alternate' type='text/html' href='https://roy.marples.name/cgit/dhcpcd.git/commit/?id=cd09e583c76755545396676833fad09313611f72'/>
<id>cd09e583c76755545396676833fad09313611f72</id>
<content type='text'>
This allows the same IPv6 address to exist on more than one
interface. Whenever dhcpcd address an IPv6 address, it will
advertise it along with the hardware address of the preferred
interface.

This is heavliy reliant on the kernel supporting this as it's the
kernel that handle the Duplicate Address Detection.
In a nutshell it needs to support RFC 7527 and ignore NA packets
from any hardware address the host owns.

Currently the only known kernel that fully supports this is
NetBSD-8.99.27
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This allows the same IPv6 address to exist on more than one
interface. Whenever dhcpcd address an IPv6 address, it will
advertise it along with the hardware address of the preferred
interface.

This is heavliy reliant on the kernel supporting this as it's the
kernel that handle the Duplicate Address Detection.
In a nutshell it needs to support RFC 7527 and ignore NA packets
from any hardware address the host owns.

Currently the only known kernel that fully supports this is
NetBSD-8.99.27
</pre>
</div>
</content>
</entry>
</feed>
