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

Correct me if my understanding is wrong.

All you need is:

$p->port_number( 3000 );

[download]
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!

Replies are listed 'Best First'.
Re^5: Optimized remote ping (syn/ack)
by themonk (Acolyte) on Jul 17, 2015 at 19:49 UTC

    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.

[reply]
      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". ;-)
[reply]
        Thanks for sharing your awesomeness!!!!!
[reply]

In Section Seekers of Perl Wisdom