netdev - Re: Setting mac address of loopback device

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: <20140124001026.GN7269@order.stressinduktion.org>
Date:	Fri, 24 Jan 2014 01:10:26 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Cong Wang <cwang@...pensource.com>
Cc:	David Miller <davem@...emloft.net>, stephen@...workplumber.org,
	netdev <netdev@...r.kernel.org>
Subject: Re: Setting mac address of loopback device

On Thu, Jan 23, 2014 at 04:03:29PM -0800, Cong Wang wrote:
> On Thu, Jan 23, 2014 at 3:49 PM, Hannes Frederic Sowa
> <hannes@...essinduktion.org> wrote:
> > On Thu, Jan 23, 2014 at 11:53:49AM -0800, Cong Wang wrote:
> >> BTW, how to change route to redirect _local_ traffic (that is packets
> >> sending to itself) to a non-loopback device? I tried to modify local
> >> route table, but have no luck to make it working.
> >
> > Have you seen the route_localnet sysctl? It should avoid the check for
> > loopback addresses when building outgoing route.
> 
> I noticed it, the doc said:
> 
> This enables the use of 127/8 for local routing purposes.
> 
> but I don't care 127/8 traffic at all, only the traffic sending to itself
> via a non-127/8 IP. :(
> 
> Or the doc is not accurate?

It seems accurate. Only other idea is to try netfilter with TEE target on
loopback.

Greetings,

  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