netdev - IP address: property of host or 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-next>] [day] [month] [year] [list]

Date:	Sat, 24 Jan 2009 16:57:50 +0300
From:	Michael Tokarev <mjt@....msk.ru>
To:	netdev <netdev@...r.kernel.org>
Subject: IP address: property of host or interface?

Hello!

Long time ago there was an ifconfig command and
interface "aliases".  Now, thanks to new way of
doing things and to famous `ip' utility, we learned
that there's no such thing as INTERFACE alias and
an IP address belongs to whole interface, not to
some "alias" of it.  So far so good.

But now I'm asking if an IP really belongs to any
particular interface, instead of the whole HOST
in question.

For example, suppose we have two interfaces, eth0
and eth1, and two addresses/nets, A0/24 and A1/24,
configured.

Let's ping address A1 from segment 0: the host in
question will answer those pings, provided we've
routing on our "external" host set up to point to
A0.  The same is true when pinging A0 from segment 1.
So, it makes no difference which IP address to access,
a host will happily answer to any of them assigned to
it, *except* of 127/8 (which is a different story).
Note that this works regardless of ip_forward, because
it's not forwarding.

Now, I'm setting up the host interfaces somewhat
differently:

 ip addr add A0/32 dev lo
 ip route add A0/24 dev eth0 src A0
 ip addr add A1/32 dev lo
 ip route add A1/24 dev eth1 src A1

I.e., I'm assigning both addresses to loopback interface
and adding ROUTES to corresponding networks/interfaces.
And guess what?  This thing will work exactly the same
way as traditional setup.

In other words, I can assign all addresses that belongs
to the host to it's loopback interface, and only add
routes (which gets added automatically behind the scenes
when I configure ADDRESS with mask != 32 on a broadcast
iface) to corresponding "remote" (not belonging to the
host) addresses.

There's even more: think of peer-to-peer (not broadcast)
interfaces, such as tun or ppp.  Traditionally we used
to have "local IP" and "remote IP" or "peer IP", and
used to set up routes to that remote IP.  For example,

  ip addr add A peer R dev ppp0
  ip route add RS/M via R

but the same works without assigning any address at all
to ppp0 interface!

  ip route add R dev ppp0
  ip route add RS/M dev ppp0

(if A is not listed locally, it's possible to add it to
lo interface again).

So.. am I right that an IP address is a HOST property,
not an INTERFACE property, and that the traditional
way is just more convenient to set up?
And that all the tools that complains that "there's
no IP address assigned to this interface" (tcpdump)
are wrong? :)

Thanks!

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