|
Ok...pinging to real servers from laptop on the same network works.
What I need to do is, I need to yum install some packages for
real_server running fedora. When I take the real server fedora
machine and hook it up to another network that is connected to
internet (has same subnet mask, pretty much same as network without
internet), real_server_fedora can't get on the internet and download
packages?
/sbin/ifconfig shows eth0 interface is up.
Any idea?
On 28/08/2007, j j <rampeters@xxxxxxxxx> wrote:
> ssh and ping is not working on both real_server machines. I can't do
> "ping 192.168.0.4" or ssh into real_server machines. I haven't turn
> on the linux_director yet. After I followed the instructions on
> http://www.ultramonkey.org/3/topologies/hc-ha-lb-eg.html, and rebooted
> the real_server machine, and tried ssh, and got this:
>
> [me@localhost ~]$ ssh me@xxxxxxxxxxx
> ssh: connect to host 192.168.0.4 port 22: No route to host
>
>
> Right now I have omitted setup info on linux_director.
>
>
> My setup for High Capacity High Availability and Load Balancing:
>
> Gateway_IP_Address: 192.168.0.1
> virtual_IP_Address: 192.168.0.240
> Linux_Director_1: 192.168.0.2
> Real_Server_1: 192.168.0.4
> Real_Server_2: 192.168.0.5
>
>
> On my real servers, my setup is like this:
> Real Server1 (for Real_server2, I replace below content that have
> 192.168.0.4 with 192.168.0.5):
>
> [root@localhost me]# /sbin/arptables -L -v -n
> Chain IN (policy ACCEPT 9 packets, 252 bytes)
> pkts bytes target in out source-ip
> destination-ip source-hw destination-hw hlen op
> hrd pro
> 0 0 DROP * * 0.0.0.0/0
> 192.168.0.240 00/00 00/00 any
> 0000/0000 0000/0000 0000/0000
>
> Chain OUT (policy ACCEPT 18 packets, 504 bytes)
> pkts bytes target in out source-ip
> destination-ip source-hw destination-hw hlen op
> hrd pro
> 0 0 mangle * eth0 192.168.0.240 0.0.0.0/0
> 00/00 00/00 any 0000/0000
> 0000/0000 0000/0000 --mangle-ip-s 192.168.0.4
>
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target in out source-ip
> destination-ip source-hw destination-hw hlen op
> hrd pro
>
>
> Configured Loopback Interface:
>
> /etc/sysconfig/network-scripts/ifcfg-lo:0:
>
> DEVICE=lo:0
> IPADDR=192.168.0.240
> NETMASK=255.255.255.255
> NETWORK=192.168.0.0
> BROADCAST=192.168.0.255
> ONBOOT=yes
> NAME=loopback
>
>
> Default Route:
>
> /etc/sysconfig/network-scripts/ifcfg-eth0:
>
> DEVICE=eth0
> BOOTPROTO=static
> IPADDR=192.168.0.4
> NETMASK=255.255.255.0
> NETWORK=192.168.0.0
> BOARDCAST=192.168.0.255
>
> #GATEWAY=192.168.0.3
> GATEWAY=192.168.0.1
> HWADDR=00:45:25:24:46:EF
> ONBOOT=yes
>
> If I do ifconfig, I get the following:
>
> [root@localhost me]# /sbin/ifconfig
> eth0 Link encap:Ethernet HWaddr 00:45:25:24:46:ef
> inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: ee80::203:25ad:cc42:46da/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:50 errors:0 dropped:0 overruns:0 frame:0
> TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:13486 (13.1 KiB) TX bytes:10340 (10.0 KiB)
> Interrupt:17
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:9590 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9590 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:69607264 (66.3 MiB) TX bytes:69607264 (66.3 MiB)
>
> lo:0 Link encap:Local Loopback
> inet addr:192.168.0.240 Mask:255.255.255.255
> UP LOOPBACK RUNNING MTU:16436 Metric:1
>
> Why does lo:0 has only three lines as comapred to other ones?
>
> thanks.
>
|
