AW: [Vserver] Routing Problem with VServer Kernel
I found the reason / solution of this problem ! I started the sshd with v_sshd wrapper. The chbind bound the sshd and all subprocesses to my ipv4root on eth0, so requests via eth1 interface fails. I configured /etc/ssh/sshd_config to listen only on one address and didn't use v_sshd, now everything works fine. regards Holger -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 21. Januar 2005 13:50 An: vserver@list.linux-vserver.org Betreff: [Vserver] Routing Problem with VServer Kernel Hi, i have a strange behavior of Kernel 2.6.10-vs1.9.3.17 on SuSE 9.2. The kernel uses the wrong route/interface (see below). If i reboot the system with original suse kernel or unpatched vanilla 2.6.10 with same configuration, the outgoing request uses the right interface eth1. This is not inside a vserver, the only change i did was applying the vserver-patch and enabling CONFIG_VSERVER_HARDCPU=y, there are no further iptable or policy routing defines. thanks in advance Holger Manthey My configuration: The 2 network devices eth0 inet addr:x.y.z.10 Bcast:x.y.z.127 Mask:255.255.255.128 eth1 inet addr:172.25.128.10 Bcast:172.25.128.127 Mask:255.255.255.128 and this is my routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.23.152.0172.25.128.1255.255.255.192 UG0 0 0 eth1 172.25.128.00.0.0.0 255.255.255.128 U 0 0 0 eth1 x.y.z.0 0.0.0.0 255.255.255.128 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 x.y.z.1 0.0.0.0 UG0 0 0 eth0 ping 172.25.128.1 PING 172.25.128.1 (172.25.128.1) 56(84) bytes of data. From x.y.z.10: icmp_seq=2 Destination Host Unreachable ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
AW: [Vserver] Routing Problem with VServer Kernel
The routing works fine with an unpatched vanilla 2.6.10 kernel and the SuSE kernel, i tried both -Ursprüngliche Nachricht- Von: Herbert Poetzl [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 21. Januar 2005 20:04 An: Manthey, Holger, NMI-DB Cc: vserver@list.linux-vserver.org Betreff: Re: [Vserver] Routing Problem with VServer Kernel On Fri, Jan 21, 2005 at 01:50:17PM +0100, [EMAIL PROTECTED] wrote: Hi, i have a strange behavior of Kernel 2.6.10-vs1.9.3.17 on SuSE 9.2. The kernel uses the wrong route/interface (see below). If i reboot the system with original suse kernel or unpatched vanilla 2.6.10 with same configuration, the outgoing request uses the right interface eth1. This is not inside a vserver, the only change i did was applying the vserver-patch and enabling CONFIG_VSERVER_HARDCPU=y, there are no further iptable or policy routing defines. hmm, interesting ... will try to reproduce, maybe you could check if the behaviour is different with 2.6.10 vanilla, or maybe this is a vendor patch issue? thanks in advance Holger Manthey best, Herbert My configuration: The 2 network devices eth0 inet addr:x.y.z.10 Bcast:x.y.z.127 Mask:255.255.255.128 eth1 inet addr:172.25.128.10 Bcast:172.25.128.127 Mask:255.255.255.128 and this is my routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.23.152.0172.25.128.1255.255.255.192 UG0 0 0 eth1 172.25.128.00.0.0.0 255.255.255.128 U 0 0 0 eth1 x.y.z.0 0.0.0.0 255.255.255.128 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 x.y.z.1 0.0.0.0 UG0 0 0 eth0 ping 172.25.128.1 PING 172.25.128.1 (172.25.128.1) 56(84) bytes of data. From x.y.z.10: icmp_seq=2 Destination Host Unreachable ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
