[The following is what I would try, without any warranty.]
> I have, using ifconfig, set up on the physical machine this:
I think that you should have a look at the vserver config file
(if it's the old config style) or the vserver config directory
tree (for new config style). Then, duplicate the information
pertaining to the first interface, replacing what should be,
(i.e. eth0 -> eth1 and 192.168.81.20 -> 192.168.91.22).
The vserver startup script should then care of setting up the
interface. [I.e. you don't have to call ifconfig beforehand.]
> [...] I presume I need to set up a route to the
> 192.168.91.0 segment. Would I do that inside the running vserver,
> after restarting it, or on the physical machine somewhere before the
Routing must be done on the host (until "ngnet" comes out).
Vserver mailing list
Received on Fri Jan 27 19:55:30 2006