Howdy, Stranger!

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

Advertise on LowEndTalk.com
Anyone experienced this ever?
New on LowEndTalk? Please read our 'Community Rules' by clicking on it in the right menu!

Anyone experienced this ever?

RadiRadi Member, Provider

Hi guys and girls,

I have a Xen HVM vps, which "got on drugs".

Right now, it is able to be ssh-ed to, with a difference that it hangs for a while when you enter the "root" username.

Once I am in, this is where the troubles begin.

VPS is not able to either ping or traceroute the outside world.

Pings and traceroutes to the IP of the host node, IP of another VPS on the host node, IP of another VPS on a different hostnode in the same vLAN are working fine.

Anyone ever experienced this issue? If yes, how did you solve it?

I have been playing with this for whole morning now. Checked network configuration against a working VPS, everything looked correct.

4 GB RAM/90 GB SSD/4 TB Traffic/KVM/1 IPv4 for $7/mo only here with coupon code "LET-It-GO".

Comments

  • AnthonySmithAnthonySmith Top Provider
    edited February 2017

    maybe you have someone trying to steal the IP somewhere on the network and its messing your arp caches up?

    Change its IP and mac to rule this out.

    The 'issue' you are describing is a fairly generic one, really its not something anyone can help you with unless we see some toubleshooting outputs or look at it ourselves.

    Based on the limited info though, I would try a different IP, test that IP on another VPS and run wireshark on the VPS to see how far the traffic is getting and why it is not getting beyond a certain point.

    I am no longer active here, find me at https://talk.lowendspirit.com (Just like LET without the scams)

  • RadiRadi Member, Provider

    Looks like that is the case. The problem VPS has multiple IPs though. I tried one of them on another VPS and well, you can guess - no inbound network as well, no SSH, nothing. I'll have to renumber the entire thing or find the thief.

    4 GB RAM/90 GB SSD/4 TB Traffic/KVM/1 IPv4 for $7/mo only here with coupon code "LET-It-GO".

  • AnthonySmithAnthonySmith Top Provider
    edited February 2017

    shut it down, ping the IP, arp -n, cat /path/to/your/xen/cfg's | grep mac you found in the arp cache

    if the mac is the pysical from another node then do the same thing on that node.

    poke me on skype if you need a hand.

    I am no longer active here, find me at https://talk.lowendspirit.com (Just like LET without the scams)

  • The hang on initial connect seems possibly due to dns (dns lookups) being enabled in sshd_config and the delay is because of your notwork (sic) :-)

    Disabling that should allow you to quickly login but you'll still be stuck in the notwork until you fix that.

  • File system in read only and needs to be fsck'd then reboot?

    How to clean up a questionable reputation: throw the kids some BF/CM offers.

  • @nullnothere said:
    The hang on initial connect seems possibly due to dns (dns lookups) being enabled in sshd_config and the delay is because of your notwork (sic) :-)

    Disabling that should allow you to quickly login but you'll still be stuck in the notwork until you fix that.

    At least I had this problem some time ago. Here you can find more information askubuntu.com/questions/246323/why-does-sshs-password-prompt-take-so-long-to-appear

  • Sounds like a duplicate IP

  • Radi said: it hangs for a while when you enter the "root" username

    OpenSSH ships with the UseDNS option enabled by default, so it tries to check the reverse DNS of a client's IP. No route to the internet = no route to your DNS server = SSHd waits until the DNS query runs into a timeout.

    Thanked by 1doughmanes

    Favourite providers (recommended for their reliable service, not their referral payouts): UltraVPSLiteServerVultr

    It's not that I'm an angry person, it's just that everything is terrible and nobody else seems to care.

  • oneilonlineoneilonline Member, Provider

    Yes, sounds like duplicate IP assigned.

    Have you tried recreating the VPS?

Sign In or Register to comment.