> 1. How this is any different than configuring the IP address of vlite
> (72.16.1.65) on the loopback interface.
It's very different. RH's parctice of configuring the loopback device
as something other than (in addition to) localhost (no domain!) is just
plain broken, as umpteen administrators will tell you. localhost is
in the root domain, and nowhere else, netwise.
> 2. The implementation of dummy_xmit() unconditionally drops every packet
> sent to it which suggests that intra-node communication can never
> occur over a dummy interface. The loopback interface on the other
> hand queues packets sent to it on the receive queue (allowing intra-
> node communication even when the dialup line is down)
> I can't think of a condition where a dummy device is useful (other than
> for simulating a blackhole device which sucks every packet sent to it).
The dummy device is conventionally used to provide a separate interface
that can be used to bind the hostname to when there is no real nic in
the box to bind it to (binding it to loopback being a no no). One
ususally does if-down ppp0, for example, with a few lines in that
brings up the hostname on dummy0. When ppp comes up, the hostname may
be bound to the ppp0 connection, but personally I prefer t leave it
stable.
"a stable binding point" for the hostname is another use for dummy0,
when the configuration is dynamic, such as in a failover cluster.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/