From: Bjoern Steinbrink (bjoern.steinbrink_at_isp4p.net)
Date: Sun 26 Sep 2004 - 17:27:58 BST
On So, 2004-09-26 at 18:24, Bjoern Steinbrink wrote:
> On So, 2004-09-26 at 17:14, Gilles wrote:
> > > >
> > > > Can I create a second purely virtual net inside H2, say 192.168.3.0 ?
> > > > [Where I would put e.g. a "mysql" vserver, with address 192.168.3.55.]
> > >
> > > if you do not accept/route packets for the 192.168.3.0/24
> > > you can assign those IPs to for example the dummy0 interface
> > > (what interface doesn't matter actually) and use it on
> > > the host only ...
> > Ooh, *that* was a piece I was missing; thanks.
> > [I use Debian.] I added something like the following in
> > /etc/network/interfaces
> > on the host:
> > iface dummy0 inet static
> > address 192.168.3.1
> > netmask 255.255.255.0
> > broadcast 192.168.3.255
> > gateway 192.168.1.10
> > (1)
> > But, when the interface is brought up, there is an error message:
> > SIOCADDRT: Network is unreachable
> > Failed to bring up dummy0.
> > This is probably related to the ifupdown Debian scripts, as "ifconfig"
> > shows the interface (and networking with a 192.168.3.2 vserver is OK).
> > Do you have some clues?
> ifup fails if any of the calls fails, in this case the route call fails,
> probably you didn't bring up the interface that makes 192.168.1.10
> reachable _before_ you bring up dummy0
And it does not undo any actions taken before the failing call. Most
probably this (sometimes annoying) behaviour is there, because you can
include arbitrary commands to be executed and the scipt can't guess how
to undo them. That's why the ifa is there although ifup failed.
Vserver mailing list