Re: !! SPAM Suspect : SPAM-URL-DBL !! Re: (usagi-core 31424) Re: [PATCH 7/13] [RFC] [IPV6] Move source address selection into route lookup.

2006-11-06 Thread Jean-Mickael Guerin
The host testlab.linux-ipv6.org doesn't seem to be visible to the outside world so could you post the results somewhere where I could take a closer look at the results? It is visible world-wide, assuming you have IPv6 connection. With IPv4-only connection, one can try to append

Re: (usagi-core 31424) Re: [PATCH 7/13] [RFC] [IPV6] Move source address selection into route lookup.

2006-11-06 Thread Jean-Mickael Guerin
[ reposted, with better subject ] http://testlab.linux-ipv6.org/tahi-autorun.2/net-2.6_20061018/ The host testlab.linux-ipv6.org doesn't seem to be visible to the outside world so could you post the results somewhere where I could take a closer look at the results? It is visible world-wide,

Re: [PATCH 7/13] [RFC] [IPV6] Move source address selection into route lookup.

2006-10-17 Thread Jean-Mickael Guerin
David Miller wrote: From: Ville Nuorvala [EMAIL PROTECTED] Date: Tue, 17 Oct 2006 03:13:17 +0300 This patch moves the normal source address selection from ip6_dst_lookup() into ip6_pol_route_output(), but shouldn't change the routing or source address selection behavior in any way.

[PATCH] drivers/net/wireless/d80211: Check configuration type in hw-config_interface.

2006-07-19 Thread Jean-Mickael Guerin
-Mickael Guerin [EMAIL PROTECTED] adm8211/adm8211.c |4 +++- rt2x00/rt2400pci.c |4 +++- rt2x00/rt2500pci.c |4 +++- rt2x00/rt61pci.c |4 +++- 4 files changed, 12 insertions(+), 4 deletions(-) diff --git a/drivers/net/wireless/d80211/adm8211/adm8211.c b/drivers/net/wireless/d80211

Re: [PATCH] shutting down an interface should remove ipv4 addresses

2006-04-11 Thread Jean-Mickael Guerin
Addresses are owned by the host not a particular device, even though they are assosciated with a particular interface. Linux defaults to using the host based addressing model instead of the interface based addressing model. It is true for IPv4, but IPv6 addresses are removed when interface

Re: about cached dst in ip6_tunnel

2006-03-24 Thread Jean-Mickael Guerin
Sorry the patch looks corrupted so I repost with attachment. Jean-Mickael -- [IPV6] ip6ip6_tnl_dst_check() : invalidate dst cache whenever xfrm policies change Signed-off-by: [EMAIL PROTECTED] diff --git a/include/net/ip6_tunnel.h b/include/net/ip6_tunnel.h index 29c9da7..5bc6e98 100644 ---

Re: Fw: IPv6: to take care of permanent routes

2006-03-16 Thread Jean-Mickael Guerin
Sorry, but I don't think this patch is needed. It is OK to add a route with the RTF_EXPIRES flag set and rtmsg_info == 0. It's simply a route that expires straight away. So there is no inconsistency in allowing this. I agree In fact if anything we should find a way to export the

IPv6: avoid dereference of null route entry in ipv6_del_addr()

2006-03-06 Thread Jean-Mickael Guerin
Hi, This patch fixes potential null pointer dereference (I never experiment such crash). The patch is made for net-2.6.17. Regards, Jean-Mickael Signed-off-by: [EMAIL PROTECTED] -- diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c index 8df9eb9..8393f45 100644 ---

Re: IPv6: to take care of permanent routes

2006-01-26 Thread Jean-Mickael Guerin
When adding a route, expiration attribute may be 0. In my understanding, it means the route never expires and rt6i_expires should be 0, and not the current time. If right, attached patch should fix the issue. Well, please drop RTF_EXPIRES also. Thanks. Following patch drops this flag. As

Re: IPv6: to take care of permanent routes

2006-01-26 Thread Jean-Mickael Guerin
Probably, the caller should not set RTF_EXPIRES when allocating new one. Instead, set rt6i_expires and RTF_EXPIRES afterwards (as your patch does). It makes sense. And, please make your patch so that we can apply it by patch -p1 at the top directory of the tree; e.g. % diff -u

IPv6: to take care of permanent routes

2006-01-25 Thread Jean-Mickael Guerin
Hi, When adding a route, expiration attribute may be 0. In my understanding, it means the route never expires and rt6i_expires should be 0, and not the current time. If right, attached patch should fix the issue. Regards, Jean-Mickael Signed-off-by: [EMAIL PROTECTED] --- route.c.orig