Destination on subnet unreachable

Discussion in 'Installation/Configuration' started by unsichtbare, Nov 26, 2011.

  1. unsichtbare

    unsichtbare Member HowtoForge Supporter

    I did a perfect build of CentOS 6 for ISPConfig 2 on my LAN (192.168.10.0/24) and then moved the server to my WAN (23.XXX.YYY.160/29) and changed all of the appropriate files.

    The server works fine on the WAN, but there is no connectivity within MY tiny little /29 subnet.

    In my case, my firewall/router has a public IP of 23.XXX.YYY.162/29

    My webserver has a public IP of 23.XXX.YYY.165/29

    Both share a gateway of 23.XXX.YYY.161/29

    If I ping my firewall/router (it is pingable) from WAN, I get replies.
    If I ping my webserver from WAN, I get replies

    I can not ping my firewall/router from webserver or vice-versa! This means I have to go somewhere else to use my own webserver!

    HELP?

    ifcfg-eth0
    Code:
    DEVICE=eth0
    HWADDR=00:13:21:6a:21:fb
    NM_CONTROLLED=yes
    ONBOOT=yes
    IPADDR=23.XXX.YYY.165
    BOOTPROTO=none
    NETMASK=255.255.255.248
    GATEWAY=23.XXX.YYY.161
    NETWORK=23.XXX.YYY.160
    DNS2=8.8.4.4
    TYPE=Ethernet
    DNS1=8.8.8.8
    IPV6INIT=no
    USERCTL=no
    Code:
    [root@web1 network-scripts]# netstat -r
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
    23.XXX.YYY.160  *               255.255.255.248 U         0 0          0 eth0
    link-local      *               255.255.0.0     U         0 0          0 eth0
    default         23-XXX-YYY-161. 0.0.0.0         UG        0 0          0 eth0
    Code:
    [root@web1 ~]# ping 23.XXX.YYY.162
    PING 23.XXX.YYY.162 (24.156.121.162) 56(84) bytes of data.
    From 23.XXX.YYY.165 icmp_seq=2 Destination Host Unreachable
    How can it be unreachable! I shouldn't even need to have a router to send pings back and forth between two IP's on the same subnet!
     

Share This Page