Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Centos 6.4 "ping : unknown host google.com" - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Centos 6.4 "ping : unknown host google.com"

2»

Comments

  • DewlanceVPSDewlanceVPS Member, Patron Provider

    @kucingbelang4

    Which eth is used? (eth0 or eth1?)

    I am sure your Server/VPS is not using a eth0 or eth1, run a command and check which eth is used?




    What is output of this command?

    ifconfig

  • @DewlanceVPS He clearly said he is using eth0, is it that difficult to read?

  • DewlanceVPSDewlanceVPS Member, Patron Provider

    @Bogdacutuu said:
    DewlanceVPS He clearly said he is using eth0, is it that difficult to read?

    I know but I want to see output of ifconfig command.

    (I know how to fix it)

  • @kucingbelang4 said:
    why should i disabling it off?

    Any progress now?

  • @kucingbelang4 said:
    what is that mean??

    It seems your router does not allow passing traffic, could u please check / do ping from your router?

  • @DewlanceVPS said:
    (I know how to fix it)

    eth0 Link encap:Ethernet HWaddr 00:0C:29:9E:9D:79
    inet addr:192.168.19.20 Bcast:192.168.19.255 Mask:255.255.255.0
    inet6 addr: fe80::20c:29ff:fe9e:9d79/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1127 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1747 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:189389 (184.9 KiB) TX bytes:170546 (166.5 KiB)

    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:1023 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1023 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:262731 (256.5 KiB) TX bytes:262731 (256.5 KiB)

  • @knopix80 said:
    Any progress now?

    yes ,thx am turn off the iptables , now it can ping self, but i still cant ping google :/

  • BrianHarrisonBrianHarrison Member, Patron Provider

    Definitely need the output of 'ifconfig' to diagnose this. From trace route it doesn't look like anything is getting past your gateway.

  • @BrianHarrison said:
    Definitely need the output of 'ifconfig' to diagnose this. From trace route it doesn't look like anything is getting past your gateway.

    ifconfig output*

    eth0 Link encap:Ethernet HWaddr 00:0C:29:9E:9D:79
    inet addr:192.168.19.20 Bcast:192.168.19.255 Mask:255.255.255.0
    inet6 addr: fe80::20c:29ff:fe9e:9d79/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:626 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1271 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:126672 (123.7 KiB) TX bytes:113335 (110.6 KiB)

    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:815 errors:0 dropped:0 overruns:0 frame:0
    TX packets:815 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:208957 (204.0 KiB) TX bytes:208957 (204.0 KiB)

  • When I'm playing with vmware a few years ago, I need to try one by one of the network interfaces, sometimes it's NAT, sometimes BRIDGE.

  • @ErawanArifNugroho said:
    When I'm playing with vmware a few years ago, I need to try one by one of the network interfaces, sometimes it's NAT, sometimes BRIDGE.

    my vm network using NAT

  • VPNVPN Member

    I assume as you have no internet connectivity but are still able to see the command line that you have KVM-IP access? If so I would be inclined to suggest you reinstall via KVM with the graphical installation wizard - this will allow you to better setup the network interfaces as they should be.

    You probably won't lose much as you're not connected to the internet and this means nothing generally will be installed.

    Generally speaking from my experience (not extensive but enough), you of been given at least your IP and perhaps the gateway from your provider when you signed up for the VPS. Using this in the installation will allow for you to set it up correctly.

    If you're stuck then let me know and I will be more than happy to try and help further.

  • @kucingbelang4, sudah bisa belum?

  • DewlanceVPSDewlanceVPS Member, Patron Provider



    down "lo" device by running this command

    ifconfig lo down

    then remove ifconfig-lo from /etc/sysconfig/network-scripts/ and restart your network.


    service network restart

  • SpeedBusSpeedBus Member, Host Rep

    Why do you need to shutdown lo ? lo has not caused me any issues till date.

  • DewlanceVPSDewlanceVPS Member, Patron Provider
    edited August 2013

    @SpeedBus said:
    Why do you need to shutdown lo ? lo has not caused me any issues till date.

    This is a resolution, If OP shutdown lo then internet will start working.
    (Note: Also need to remove lo file and restart network)

Sign In or Register to comment.