netdev - Re: source route ignored in favor of local interface

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]

Date:	Tue, 01 Mar 2011 14:31:58 -0500
From:	Joe Buehler <aspam@....net>
To:	Chris Friesen <chris.friesen@...band.com>
CC:	netdev@...r.kernel.org
Subject: Re: source route ignored in favor of local interface

> If you really want to modify things, have you looked at your ip rules?
> "ip ru" will dump them.  Typically it looks something like
> 
> 0:      from all lookup local
> 32766:  from all lookup main
> 32767:  from all lookup default
> 
> The last item in each row is the name of the routing table.  As you can
> see, the first rule is for local interfaces, and a later rule deals with
> the main and default routing tables.
> 
> You could move the local lookup to rule 1 and add in a new rule 0
> specifically dealing with your situation.

We have tried some variations on modifications to ip rules, but the
kernel appears to treat rule 0 specially -- it cannot be deleted, for
example.  This results in the enforcing of local interfaces before
source routes -- surely something that should be a policy decision, not
hard-coded.

Let me rephrase and ask: Does anyone know how to replace the priority 0
rule?

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