netdev - Re: IPV6 routing problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140122070759.GB28225@order.stressinduktion.org>
Date:	Wed, 22 Jan 2014 08:07:59 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Sharat Masetty <sharat04@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: IPV6 routing problem

Hi!

On Tue, Jan 21, 2014 at 06:41:58PM -0700, Sharat Masetty wrote:
>  I have an IPV6 routing problem that has only surfaced on a 3.10
> kernel version. This problem is not seen on 3.4 kernel. I will keep
> the problem statement as brief as possible.

Could you do me a favor and test this on a recent 3.13 kernel? Thanks!
Please also state the specific kernel version (I guess you use one).

> I have two interfaces say eth0 and eth1. I have a host route to a
> destination over eth1, but this route has a global gateway
> address(via) of the router on the link. When this global gateway is
> present in the route, the kernel does not seem to pick up the route,
> but falls back to the default route which is eth0. When this gateway
> is removed from the route or if the gateway is changed to a link local
> address of the router, instead of the global address, then routing
> seems to work as expected and kernel picks up interface eth1.
> 
> == does not work ==
> <dest-addr> via <global scope -gateway addr>dev eth1 metric 1024
> <global scope -gateway addr> dev eth1  metric 1024

Do you have CONFIG_IPV6_ROUTER_PREF activated?

> 
> I checked the git commits diff between 3.4 and 3.10 for ipv6/route.c
> and ipv6/ip6_fib.c, but looks like they are close to an year apart
> with lots of changes. Hence I wanted to reach out to you to see if any
> recent changes in IPV6 routing is causing this difference in behavior.

It should be a problem in ipv6/route.c, ip6_fib.c does not really care about
interfaces that much.

Thanks,

  Hannes

--
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