From: Martin Pauly (pauly_at_hrz.uni-marburg.de)
Date: Mon 14 Mar 2005 - 16:29:22 GMT
Hi all,
I want to build a setup with 1 box running 2 vservers on top of
2.4.29-vs1.2.10, each one using its own Ethernet interface
and its own gateway. Its's exactly what has been discussed in
http://www.paul.sladen.org/vserver/archives/200302/0091.html
So I start off with the master IP 192.168.1.18/25 and the first
vserver (called rsf1) at 137.248.1.53/25, both set up on eth1:
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:0e:0c:5c:53:75 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:0e:0c:5c:53:74 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.18/25 brd 192.168.1.127 scope global eth1
inet 137.248.1.53/25 brd 137.248.1.127 scope global eth1:rsf1
master22:/etc/vservers# ip route sh
The routing table is what you'd expect:
137.248.1.0/25 dev eth1 proto kernel scope link src 137.248.1.53
192.168.1.0/25 dev eth1 proto kernel scope link src 192.168.1.18
default via 192.168.1.126 dev eth1
After starting the second vserver (called rst1) I get:
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:0e:0c:5c:53:75 brd ff:ff:ff:ff:ff:ff
inet 137.248.9.13/27 brd 137.248.9.31 scope global eth0:rst1
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:0e:0c:5c:53:74 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.18/25 brd 192.168.1.127 scope global eth1
inet 137.248.1.53/25 brd 137.248.1.127 scope global eth1:rsf1
The ifconfig call inside /sbin/vserver introduces another route on eth1:
master22:/etc/vservers# ip route sh
137.248.9.0/27 dev eth0 proto kernel scope link src 137.248.9.13
137.248.1.0/25 dev eth1 proto kernel scope link src 137.248.1.53
192.168.1.0/25 dev eth1 proto kernel scope link src 192.168.1.18
default via 192.168.1.126 dev eth1
4. Now I adjust the routing tables:
master22:/etc/vservers# ip route del 137.248.9.0/27 dev eth0
master22:/etc/vservers# ip route add 137.248.9.0/27 dev eth0 src 137.248.9.13 table 2
master22:/etc/vservers# ip route add default dev eth0 via 137.248.9.30 src
137.248.9.13 table 2
RTNETLINK answers: Network is unreachable
Any idea what might go wrong here?
Thanks for any hints
Martin
-- Dr. Martin Pauly Fax: 49-6421-28-26994 HRZ Univ. Marburg Phone: 49-6421-28-23527 Hans-Meerwein-Str. E-Mail: pauly_at_HRZ.Uni-Marburg.DE D-35032 Marburg_______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver