netdev
[Top] [All Lists]

Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!

To: David Ford <david@xxxxxxxxx>
Subject: Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!)
From: Chris Wedgwood <cw@xxxxxxxx>
Date: Mon, 8 Jan 2001 01:13:08 +1300
Cc: Ben Greear <greearb@xxxxxxxxxxxxxxx>, linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.10.10101070220410.4173-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>; from david@xxxxxxxxx on Sun, Jan 07, 2001 at 02:22:31AM -0800
References: <20010107162905.B1804@xxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.10.10101070220410.4173-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Sun, Jan 07, 2001 at 02:22:31AM -0800, David Ford wrote:

    BIND copes just fine, how would it not?  I haven't heard any
    problems with routing daemons either.

Bind knows about multiple virtual interfaces; but we can also have
multiple addresses on a single interface and have no virtual
interfaces at all.

I doubt bind knows about this nor handles it.

<pause>

OK, I'm a liar -- bind does handle this. Cool.

Jan  8 01:09:12 tapu named[599]: listening on [127.0.0.1].53 (lo)
Jan  8 01:09:12 tapu named[599]: listening on [10.0.0.1].53 (lo)
Jan  8 01:09:12 tapu named[599]: listening on [x.x.x.x].53 (x0)
Jan  8 01:09:12 tapu named[599]: Forwarding source address is [0.0.0.0].1032

This is good news, because it means there is a precedent for multiple
addresses on a single interface so we can kill the <ifname>:<n>
syntax in favor of the above which is cleaner of more accurately
represents what is happening.



  --cw

<Prev in Thread] Current Thread [Next in Thread>