From: Liam Helmer (linuxlists_at_thevenue.org)
Date: Tue 12 Oct 2004 - 19:26:18 BST
That sounds like the right package. Go crazy. ;)
On Tue, 2004-10-12 at 11:02 -0700, Roderick A. Anderson wrote:
> Thanks Liam,
> I was just going through some older messages because I was thining it was
> a routing issue and saw a message by Gebhardt Thomas in March of this year
> addressing this same issue.
> Do you think it may be part of Fedora Core 1? Rpm reports a
> iproute-2.4.7-11. Is there another way to test whether this is a
> Redhat/Fedora naming convention or the real thing -- 2?
> On Tue, 12 Oct 2004, Liam Helmer wrote:
> > It sounds to me like you need to build routing tables for the vservers.
> > The problem you're probably having is that linux, by default, wants to
> > use it's default route for everything: you've got to specifically tell
> > it that it needs to use routing from the other ips for packets
> > originating from those ips.
> > www.policyrouting.org has a tonne of information on this, but, the quick
> > version is:
> Darn another book to buy ... (I try to support those in the FOSS world
> > add a vserver routing table to /etc/iproute2/rt_tables:
> This directory does not exist. In fact /etc/iproute2 doesn't. Does this
> indicate whether iproute2 is installed or just not used in this manner.
> > 200 vserver
> I'm assuming vserver is a label so with my naming convertion it would be
> 200 img4
> How about other NICs? I have one system with three in it.
> > (the number doesn't matter much)
> > then run:
> > ip route add table vserver default via <second router>
> Well I used the term router. Should this value, "<second router>", be the
> interface -- eth1 -- I'm trying to get to work? Like this?
> ip route add table img4 default via eth1
> > ip rule add from <vserver.ip.range/netmask> lookup vserver
> This "<vserver.ip.range/netmask>" could be anything (legitimate that is),
> so I'd use:
> ip rule add from 192.168.13.0/255.255.255.0 lookup img4
> > Put those two lines in you startup scripts somewhere. Note, if you have
> > other static routes for your network, you'll need to add them into the
> > "ip route" list too.
> Are there in SysV scripts that do this already and make it easier? I have
> other less-experienced people pressing keys for me while I try to talk
> them through the process over the phone. Having all startup/shutdown
> scripts by init level is nice and consistant.
> > In case you're curious, ping works, because it manually creates packets,
> > rather than using the standard ipv4 interface (which is why it needs
> > CAP_NET_RAW).
> Something new every day. Also I'm asking for this clarification for two
> reasons. My job is easier and this can go into the docs or wiki to help
> the next slightly-clueless vserver user that comes along. (_We_ get to
> say RTFM :-)
> Again thanks,
-- Liam Helmer <linuxlists_at_thevenue.org>
_______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver