in reply to Re^4: Optimized remote ping (syn/ack)
in thread Optimized remote ping

I made the necessary changes in the code.

currently I am running on localhost...so according only "127.0.0.1"should be pingable on port "3000".

But I get this IP "127.115.99.245" also pingable as TRUE. is there some more changes like timeout or something which i might need to tweak around.

Replies are listed 'Best First'.
Re^6: Optimized remote ping (syn/ack)
by afoken (Chancellor) on Jul 17, 2015 at 20:03 UTC
    currently I am running on localhost...so according only "127.0.0.1"should be pingable on port "3000". But I get this IP "127.115.99.245" also pingable as TRUE

    Yes, that's perfectly ok. localhost has a whole Class-A subnet assigned in IPv4, 16.7 million addresses, all starting with "127.", all just for the machine you are currently working with. Yes, that's a big waste of IP addresses, but it's an old decision that can't be changed now.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
      Thanks for sharing your awesomeness!!!!!