<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-toradex.git/include/linux/ipv6.h, branch v2.6.35-rc3</title>
<subtitle>Linux kernel for Apalis and Colibri modules</subtitle>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/'/>
<entry>
<title>ipv6: ip6mr: support multiple tables</title>
<updated>2010-05-11T12:40:55+00:00</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2010-05-11T12:40:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=d1db275dd3f6e4182c4c4b4a1ac6287925d60569'/>
<id>d1db275dd3f6e4182c4c4b4a1ac6287925d60569</id>
<content type='text'>
This patch adds support for multiple independant multicast routing instances,
named "tables".

Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT6_TABLE. The table number is
stored in the raw socket data and affects all following ip6mr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT6_TABLE_DFLT)
is created with a default routing rule pointing to it. Newly created pim6reg
devices have the table number appended ("pim6regX"), with the exception of
devices created in the default table, which are named just "pim6reg" for
compatibility reasons.

Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.

Example usage:

- bind pimd/xorp/... to a specific table:

uint32_t table = 123;
setsockopt(fd, SOL_IPV6, MRT6_TABLE, &amp;table, sizeof(table));

- create routing rules directing packets to the new table:

# ip -6 mrule add iif eth0 lookup 123
# ip -6 mrule add oif eth0 lookup 123

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch adds support for multiple independant multicast routing instances,
named "tables".

Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT6_TABLE. The table number is
stored in the raw socket data and affects all following ip6mr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT6_TABLE_DFLT)
is created with a default routing rule pointing to it. Newly created pim6reg
devices have the table number appended ("pim6regX"), with the exception of
devices created in the default table, which are named just "pim6reg" for
compatibility reasons.

Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.

Example usage:

- bind pimd/xorp/... to a specific table:

uint32_t table = 123;
setsockopt(fd, SOL_IPV6, MRT6_TABLE, &amp;table, sizeof(table));

- create routing rules directing packets to the new table:

# ip -6 mrule add iif eth0 lookup 123
# ip -6 mrule add oif eth0 lookup 123

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'master' of /repos/git/net-next-2.6</title>
<updated>2010-05-10T16:39:28+00:00</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2010-05-10T16:39:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=1e4b1057121bc756b91758a434b504d2010f6088'/>
<id>1e4b1057121bc756b91758a434b504d2010f6088</id>
<content type='text'>
Conflicts:
	net/bridge/br_device.c
	net/bridge/br_forward.c

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Conflicts:
	net/bridge/br_device.c
	net/bridge/br_forward.c

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>IPv6: Complete IPV6_DONTFRAG support</title>
<updated>2010-04-24T06:35:29+00:00</updated>
<author>
<name>Brian Haley</name>
<email>brian.haley@hp.com</email>
</author>
<published>2010-04-23T11:26:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=4b340ae20d0e2366792abe70f46629e576adaf5e'/>
<id>4b340ae20d0e2366792abe70f46629e576adaf5e</id>
<content type='text'>
Finally add support to detect a local IPV6_DONTFRAG event
and return the relevant data to the user if they've enabled
IPV6_RECVPATHMTU on the socket.  The next recvmsg() will
return no data, but have an IPV6_PATHMTU as ancillary data.

Signed-off-by: Brian Haley &lt;brian.haley@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Finally add support to detect a local IPV6_DONTFRAG event
and return the relevant data to the user if they've enabled
IPV6_RECVPATHMTU on the socket.  The next recvmsg() will
return no data, but have an IPV6_PATHMTU as ancillary data.

Signed-off-by: Brian Haley &lt;brian.haley@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>IPv6: data structure changes for new socket options</title>
<updated>2010-04-24T06:35:28+00:00</updated>
<author>
<name>Brian Haley</name>
<email>brian.haley@hp.com</email>
</author>
<published>2010-04-23T11:26:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=793b14731686595a741d9f47726ad8b9a235385a'/>
<id>793b14731686595a741d9f47726ad8b9a235385a</id>
<content type='text'>
Add underlying data structure changes and basic setsockopt()
and getsockopt() support for IPV6_RECVPATHMTU, IPV6_PATHMTU,
and IPV6_DONTFRAG.  IPV6_PATHMTU is actually fully functional
at this point.

Signed-off-by: Brian Haley &lt;brian.haley@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add underlying data structure changes and basic setsockopt()
and getsockopt() support for IPV6_RECVPATHMTU, IPV6_PATHMTU,
and IPV6_DONTFRAG.  IPV6_PATHMTU is actually fully functional
at this point.

Signed-off-by: Brian Haley &lt;brian.haley@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>IPv6: Generic TTL Security Mechanism (final version)</title>
<updated>2010-04-22T22:24:53+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>shemminger@vyatta.com</email>
</author>
<published>2010-04-22T22:24:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=e802af9cabb011f09b9c19a82faef3dd315f27eb'/>
<id>e802af9cabb011f09b9c19a82faef3dd315f27eb</id>
<content type='text'>
This patch adds IPv6 support for RFC5082 Generalized TTL Security Mechanism.  

Not to users of mapped address; the IPV6 and IPV4 socket options are seperate.
The server does have to deal with both IPv4 and IPv6 socket options
and the client has to handle the different for each family.

On client:
	int ttl = 255;
	getaddrinfo(argv[1], argv[2], &amp;hint, &amp;result);

	for (rp = result; rp != NULL; rp = rp-&gt;ai_next) {
		s = socket(rp-&gt;ai_family, rp-&gt;ai_socktype, rp-&gt;ai_protocol);
		if (s &lt; 0) continue;

		if (rp-&gt;ai_family == AF_INET) {
			setsockopt(s, IPPROTO_IP, IP_TTL, &amp;ttl, sizeof(ttl));
		} else if (rp-&gt;ai_family == AF_INET6) {
			setsockopt(s, IPPROTO_IPV6,  IPV6_UNICAST_HOPS, 
					&amp;ttl, sizeof(ttl)))
		}
			
		if (connect(s, rp-&gt;ai_addr, rp-&gt;ai_addrlen) == 0) {
		   ...

On server:
	int minttl = 255 - maxhops;
   
	getaddrinfo(NULL, port, &amp;hints, &amp;result);
	for (rp = result; rp != NULL; rp = rp-&gt;ai_next) {
		s = socket(rp-&gt;ai_family, rp-&gt;ai_socktype, rp-&gt;ai_protocol);
		if (s &lt; 0) continue;

		if (rp-&gt;ai_family == AF_INET6)
			setsockopt(s, IPPROTO_IPV6,  IPV6_MINHOPCOUNT,
					&amp;minttl, sizeof(minttl));
		setsockopt(s, IPPROTO_IP, IP_MINTTL, &amp;minttl, sizeof(minttl));
			
		if (bind(s, rp-&gt;ai_addr, rp-&gt;ai_addrlen) == 0)
			break
...

Signed-off-by: Stephen Hemminger &lt;shemminger@vyatta.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch adds IPv6 support for RFC5082 Generalized TTL Security Mechanism.  

Not to users of mapped address; the IPV6 and IPV4 socket options are seperate.
The server does have to deal with both IPv4 and IPv6 socket options
and the client has to handle the different for each family.

On client:
	int ttl = 255;
	getaddrinfo(argv[1], argv[2], &amp;hint, &amp;result);

	for (rp = result; rp != NULL; rp = rp-&gt;ai_next) {
		s = socket(rp-&gt;ai_family, rp-&gt;ai_socktype, rp-&gt;ai_protocol);
		if (s &lt; 0) continue;

		if (rp-&gt;ai_family == AF_INET) {
			setsockopt(s, IPPROTO_IP, IP_TTL, &amp;ttl, sizeof(ttl));
		} else if (rp-&gt;ai_family == AF_INET6) {
			setsockopt(s, IPPROTO_IPV6,  IPV6_UNICAST_HOPS, 
					&amp;ttl, sizeof(ttl)))
		}
			
		if (connect(s, rp-&gt;ai_addr, rp-&gt;ai_addrlen) == 0) {
		   ...

On server:
	int minttl = 255 - maxhops;
   
	getaddrinfo(NULL, port, &amp;hints, &amp;result);
	for (rp = result; rp != NULL; rp = rp-&gt;ai_next) {
		s = socket(rp-&gt;ai_family, rp-&gt;ai_socktype, rp-&gt;ai_protocol);
		if (s &lt; 0) continue;

		if (rp-&gt;ai_family == AF_INET6)
			setsockopt(s, IPPROTO_IPV6,  IPV6_MINHOPCOUNT,
					&amp;minttl, sizeof(minttl));
		setsockopt(s, IPPROTO_IP, IP_MINTTL, &amp;minttl, sizeof(minttl));
			
		if (bind(s, rp-&gt;ai_addr, rp-&gt;ai_addrlen) == 0)
			break
...

Signed-off-by: Stephen Hemminger &lt;shemminger@vyatta.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>netfilter: ipv6: add IPSKB_REROUTED exclusion to NF_HOOK/POSTROUTING invocation</title>
<updated>2010-04-13T13:32:16+00:00</updated>
<author>
<name>Jan Engelhardt</name>
<email>jengelh@medozas.de</email>
</author>
<published>2010-04-13T13:32:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=9c6eb28aca52d562f3ffbaebaa56385df9972a43'/>
<id>9c6eb28aca52d562f3ffbaebaa56385df9972a43</id>
<content type='text'>
Similar to how IPv4's ip_output.c works, have ip6_output also check
the IPSKB_REROUTED flag. It will be set from xt_TEE for cloned packets
since Xtables can currently only deal with a single packet in flight
at a time.

Signed-off-by: Jan Engelhardt &lt;jengelh@medozas.de&gt;
Acked-by: David S. Miller &lt;davem@davemloft.net&gt;
[Patrick: changed to use an IP6SKB value instead of IPSKB]
Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Similar to how IPv4's ip_output.c works, have ip6_output also check
the IPSKB_REROUTED flag. It will be set from xt_TEE for cloned packets
since Xtables can currently only deal with a single packet in flight
at a time.

Signed-off-by: Jan Engelhardt &lt;jengelh@medozas.de&gt;
Acked-by: David S. Miller &lt;davem@davemloft.net&gt;
[Patrick: changed to use an IP6SKB value instead of IPSKB]
Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>inet: rename some inet_sock fields</title>
<updated>2009-10-19T01:52:53+00:00</updated>
<author>
<name>Eric Dumazet</name>
<email>eric.dumazet@gmail.com</email>
</author>
<published>2009-10-15T06:30:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=c720c7e8383aff1cb219bddf474ed89d850336e3'/>
<id>c720c7e8383aff1cb219bddf474ed89d850336e3</id>
<content type='text'>
In order to have better cache layouts of struct sock (separate zones
for rx/tx paths), we need this preliminary patch.

Goal is to transfert fields used at lookup time in the first
read-mostly cache line (inside struct sock_common) and move sk_refcnt
to a separate cache line (only written by rx path)

This patch adds inet_ prefix to daddr, rcv_saddr, dport, num, saddr,
sport and id fields. This allows a future patch to define these
fields as macros, like sk_refcnt, without name clashes.

Signed-off-by: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In order to have better cache layouts of struct sock (separate zones
for rx/tx paths), we need this preliminary patch.

Goal is to transfert fields used at lookup time in the first
read-mostly cache line (inside struct sock_common) and move sk_refcnt
to a separate cache line (only written by rx path)

This patch adds inet_ prefix to daddr, rcv_saddr, dport, num, saddr,
sport and id fields. This allows a future patch to define these
fields as macros, like sk_refcnt, without name clashes.

Signed-off-by: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ipv6: Fix the size overflow of addrconf_sysctl array</title>
<updated>2009-10-09T05:44:47+00:00</updated>
<author>
<name>Jin Dongming</name>
<email>jin.dongming@np.css.fujitsu.com</email>
</author>
<published>2009-10-09T05:44:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=e0e6f55d298af03ab88bfe8455b671d29d78f426'/>
<id>e0e6f55d298af03ab88bfe8455b671d29d78f426</id>
<content type='text'>
(This patch fixes bug of commit f7734fdf61ec6bb848e0bafc1fb8bad2c124bb50
 title "make TLLAO option for NA packets configurable")

When the IPV6 conf is used, the function sysctl_set_parent is called and the
array addrconf_sysctl is used as a parameter of the function.

The above patch added new conf "force_tllao" into the array addrconf_sysctl,
but the size of the array was not modified, the static allocated size is
DEVCONF_MAX + 1 but the real size is DEVCONF_MAX + 2, so the problem is
that the function sysctl_set_parent accessed wrong address.

I got the following information.
Call Trace:
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff810622d5&gt;] __register_sysctl_paths+0xde/0x272
    [&lt;ffffffff8110892d&gt;] ? __kmalloc_track_caller+0x16e/0x180
    [&lt;ffffffffa00cfac3&gt;] ? __addrconf_sysctl_register+0xc5/0x144 [ipv6]
    [&lt;ffffffff8141f2c9&gt;] register_net_sysctl_table+0x48/0x4b
    [&lt;ffffffffa00cfaf5&gt;] __addrconf_sysctl_register+0xf7/0x144 [ipv6]
    [&lt;ffffffffa00cfc16&gt;] addrconf_init_net+0xd4/0x104 [ipv6]
    [&lt;ffffffff8139195f&gt;] setup_net+0x35/0x82
    [&lt;ffffffff81391f6c&gt;] copy_net_ns+0x76/0xe0
    [&lt;ffffffff8107ad60&gt;] create_new_namespaces+0xf0/0x16e
    [&lt;ffffffff8107afee&gt;] copy_namespaces+0x65/0x9f
    [&lt;ffffffff81056dff&gt;] copy_process+0xb2c/0x12c3
    [&lt;ffffffff810576e1&gt;] do_fork+0x14b/0x2d2
    [&lt;ffffffff8107ac4e&gt;] ? up_read+0xe/0x10
    [&lt;ffffffff81438e73&gt;] ? do_page_fault+0x27a/0x2aa
    [&lt;ffffffff8101044b&gt;] sys_clone+0x28/0x2a
    [&lt;ffffffff81011fb3&gt;] stub_clone+0x13/0x20
    [&lt;ffffffff81011c72&gt;] ? system_call_fastpath+0x16/0x1b

And the information of IPV6 in .config is as following.
IPV6 in .config:
    CONFIG_IPV6=m
    CONFIG_IPV6_PRIVACY=y
    CONFIG_IPV6_ROUTER_PREF=y
    CONFIG_IPV6_ROUTE_INFO=y
    CONFIG_IPV6_OPTIMISTIC_DAD=y
    CONFIG_IPV6_MIP6=m
    CONFIG_IPV6_SIT=m
    # CONFIG_IPV6_SIT_6RD is not set
    CONFIG_IPV6_NDISC_NODETYPE=y
    CONFIG_IPV6_TUNNEL=m
    CONFIG_IPV6_MULTIPLE_TABLES=y
    CONFIG_IPV6_SUBTREES=y
    CONFIG_IPV6_MROUTE=y
    CONFIG_IPV6_PIMSM_V2=y
    # CONFIG_IP_VS_IPV6 is not set
    CONFIG_NF_CONNTRACK_IPV6=m
    CONFIG_IP6_NF_MATCH_IPV6HEADER=m

I confirmed this patch fixes this problem.

Signed-off-by: Jin Dongming &lt;jin.dongming@np.css.fujitsu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
(This patch fixes bug of commit f7734fdf61ec6bb848e0bafc1fb8bad2c124bb50
 title "make TLLAO option for NA packets configurable")

When the IPV6 conf is used, the function sysctl_set_parent is called and the
array addrconf_sysctl is used as a parameter of the function.

The above patch added new conf "force_tllao" into the array addrconf_sysctl,
but the size of the array was not modified, the static allocated size is
DEVCONF_MAX + 1 but the real size is DEVCONF_MAX + 2, so the problem is
that the function sysctl_set_parent accessed wrong address.

I got the following information.
Call Trace:
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff8106085d&gt;] sysctl_set_parent+0x29/0x3e
    [&lt;ffffffff810622d5&gt;] __register_sysctl_paths+0xde/0x272
    [&lt;ffffffff8110892d&gt;] ? __kmalloc_track_caller+0x16e/0x180
    [&lt;ffffffffa00cfac3&gt;] ? __addrconf_sysctl_register+0xc5/0x144 [ipv6]
    [&lt;ffffffff8141f2c9&gt;] register_net_sysctl_table+0x48/0x4b
    [&lt;ffffffffa00cfaf5&gt;] __addrconf_sysctl_register+0xf7/0x144 [ipv6]
    [&lt;ffffffffa00cfc16&gt;] addrconf_init_net+0xd4/0x104 [ipv6]
    [&lt;ffffffff8139195f&gt;] setup_net+0x35/0x82
    [&lt;ffffffff81391f6c&gt;] copy_net_ns+0x76/0xe0
    [&lt;ffffffff8107ad60&gt;] create_new_namespaces+0xf0/0x16e
    [&lt;ffffffff8107afee&gt;] copy_namespaces+0x65/0x9f
    [&lt;ffffffff81056dff&gt;] copy_process+0xb2c/0x12c3
    [&lt;ffffffff810576e1&gt;] do_fork+0x14b/0x2d2
    [&lt;ffffffff8107ac4e&gt;] ? up_read+0xe/0x10
    [&lt;ffffffff81438e73&gt;] ? do_page_fault+0x27a/0x2aa
    [&lt;ffffffff8101044b&gt;] sys_clone+0x28/0x2a
    [&lt;ffffffff81011fb3&gt;] stub_clone+0x13/0x20
    [&lt;ffffffff81011c72&gt;] ? system_call_fastpath+0x16/0x1b

And the information of IPV6 in .config is as following.
IPV6 in .config:
    CONFIG_IPV6=m
    CONFIG_IPV6_PRIVACY=y
    CONFIG_IPV6_ROUTER_PREF=y
    CONFIG_IPV6_ROUTE_INFO=y
    CONFIG_IPV6_OPTIMISTIC_DAD=y
    CONFIG_IPV6_MIP6=m
    CONFIG_IPV6_SIT=m
    # CONFIG_IPV6_SIT_6RD is not set
    CONFIG_IPV6_NDISC_NODETYPE=y
    CONFIG_IPV6_TUNNEL=m
    CONFIG_IPV6_MULTIPLE_TABLES=y
    CONFIG_IPV6_SUBTREES=y
    CONFIG_IPV6_MROUTE=y
    CONFIG_IPV6_PIMSM_V2=y
    # CONFIG_IP_VS_IPV6 is not set
    CONFIG_NF_CONNTRACK_IPV6=m
    CONFIG_IP6_NF_MATCH_IPV6HEADER=m

I confirmed this patch fixes this problem.

Signed-off-by: Jin Dongming &lt;jin.dongming@np.css.fujitsu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>make TLLAO option for NA packets configurable</title>
<updated>2009-10-07T08:10:45+00:00</updated>
<author>
<name>Octavian Purdila</name>
<email>opurdila@ixiacom.com</email>
</author>
<published>2009-10-02T11:39:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=f7734fdf61ec6bb848e0bafc1fb8bad2c124bb50'/>
<id>f7734fdf61ec6bb848e0bafc1fb8bad2c124bb50</id>
<content type='text'>
On Friday 02 October 2009 20:53:51 you wrote:

&gt; This is good although I would have shortened the name.

Ah, I knew I forgot something :) Here is v4.

tavi

&gt;From 24d96d825b9fa832b22878cc6c990d5711968734 Mon Sep 17 00:00:00 2001
From: Octavian Purdila &lt;opurdila@ixiacom.com&gt;
Date: Fri, 2 Oct 2009 00:51:15 +0300
Subject: [PATCH] ipv6: new sysctl for sending TLLAO with unicast NAs

Neighbor advertisements responding to unicast neighbor solicitations
did not include the target link-layer address option. This patch adds
a new sysctl option (disabled by default) which controls whether this
option should be sent even with unicast NAs.

The need for this arose because certain routers expect the TLLAO in
some situations even as a response to unicast NS packets.

Moreover, RFC 2461 recommends sending this to avoid a race condition
(section 4.4, Target link-layer address)

Signed-off-by: Cosmin Ratiu &lt;cratiu@ixiacom.com&gt;
Signed-off-by: Octavian Purdila &lt;opurdila@ixiacom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On Friday 02 October 2009 20:53:51 you wrote:

&gt; This is good although I would have shortened the name.

Ah, I knew I forgot something :) Here is v4.

tavi

&gt;From 24d96d825b9fa832b22878cc6c990d5711968734 Mon Sep 17 00:00:00 2001
From: Octavian Purdila &lt;opurdila@ixiacom.com&gt;
Date: Fri, 2 Oct 2009 00:51:15 +0300
Subject: [PATCH] ipv6: new sysctl for sending TLLAO with unicast NAs

Neighbor advertisements responding to unicast neighbor solicitations
did not include the target link-layer address option. This patch adds
a new sysctl option (disabled by default) which controls whether this
option should be sent even with unicast NAs.

The need for this arose because certain routers expect the TLLAO in
some situations even as a response to unicast NS packets.

Moreover, RFC 2461 recommends sending this to avoid a race condition
(section 4.4, Target link-layer address)

Signed-off-by: Cosmin Ratiu &lt;cratiu@ixiacom.com&gt;
Signed-off-by: Octavian Purdila &lt;opurdila@ixiacom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>IPv6: Add 'autoconf' and 'disable_ipv6' module parameters</title>
<updated>2009-06-01T10:07:33+00:00</updated>
<author>
<name>Brian Haley</name>
<email>brian.haley@hp.com</email>
</author>
<published>2009-06-01T10:07:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=56d417b12e57dfe11c9b7ba4bea3882c62a55815'/>
<id>56d417b12e57dfe11c9b7ba4bea3882c62a55815</id>
<content type='text'>
Add 'autoconf' and 'disable_ipv6' parameters to the IPv6 module.

The first controls if IPv6 addresses are autoconfigured from
prefixes received in Router Advertisements.  The IPv6 loopback
(::1) and link-local addresses are still configured.

The second controls if IPv6 addresses are desired at all.  No
IPv6 addresses will be added to any interfaces.

Signed-off-by: Brian Haley &lt;brian.haley@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add 'autoconf' and 'disable_ipv6' parameters to the IPv6 module.

The first controls if IPv6 addresses are autoconfigured from
prefixes received in Router Advertisements.  The IPv6 loopback
(::1) and link-local addresses are still configured.

The second controls if IPv6 addresses are desired at all.  No
IPv6 addresses will be added to any interfaces.

Signed-off-by: Brian Haley &lt;brian.haley@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
</feed>
