[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.03.1310180921200.1581@ssi.bg>
Date: Fri, 18 Oct 2013 09:33:13 +0300 (EEST)
From: Julian Anastasov <ja@....bg>
To: Hannes Frederic Sowa <hannes@...essinduktion.org>
cc: Simon Horman <horms@...ge.net.au>,
YOSHIFUJI Hideaki / 吉藤英明
<yoshfuji@...ux-ipv6.org>, lvs-devel@...r.kernel.org,
netdev@...r.kernel.org, Mark Brooks <mark@...dbalancer.org>,
Phil Oester <kernel@...uxace.com>
Subject: Re: [RFC net-next] ipv6: Use destination address determined by
IPVS
Hello,
On Fri, 18 Oct 2013, Hannes Frederic Sowa wrote:
> I played around with your patch and tested xt_TEE. I added a TEE rule to
> mangle/OUTPUT and pinged. This happend, I have not yet analyzed it:
May be a side effect of using some multicast address?
Can you test it with such address check?:
if (rt->rt6i_flags & RTF_GATEWAY ||
ipv6_addr_type(&rt->rt6i_gateway) & IPV6_ADDR_UNICAST)
> [ 101.129421] [<ffffffff816d4e47>] icmp6_dst_alloc+0xf7/0x430
> [ 101.129421] [<ffffffff816d4d55>] ? icmp6_dst_alloc+0x5/0x430
> [ 101.129421] [<ffffffff816dde26>] ndisc_send_skb+0x3e6/0x540
> [ 101.129421] [<ffffffff816df81c>] ndisc_send_ns+0xdc/0x140
> [ 101.129421] [<ffffffff816d394b>] rt6_probe+0x31b/0x380
> [ 101.129421] [<ffffffff816d3690>] ? rt6_probe+0x60/0x380
> [ 101.129421] [<ffffffff816d1b93>] ? rt6_score_route+0xa3/0x380
> [ 101.129421] [<ffffffff816d471c>] ip6_pol_route.isra.47+0x2fc/0x4f0
Regards
--
Julian Anastasov <ja@....bg>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists