Pinging to 'crazy' IP address
- Thread starter ~J~
- Start date
Man of Honour
- Joined
- 31 Jan 2004
- Posts
- 16,338
- Location
- Plymouth
That's nothing...try 127.0.0.1 
Nope, can guarantee (and can provide a trace when I get back tomorrow), that I get a response.
Ends up coming from a company called, and I'm been serious, "Giraffe Factory Housing" or something.
The actual ping-back is NOT from 192.789.255.255, but from a different IP, but I'm still surprised that it's been accepted.
Ends up coming from a company called, and I'm been serious, "Giraffe Factory Housing" or something.
The actual ping-back is NOT from 192.789.255.255, but from a different IP, but I'm still surprised that it's been accepted.
Soldato
- Joined
- 3 Aug 2005
- Posts
- 4,534
- Location
- UK
Well I hope at least one of you is right 'cos we've been scratching our heads on this one! 
Will post the trace tomorrow, I know the trace bounced off everywhere, and the "overflowing the buffer" sounds right, but I'm just surprised that the command prompt didn't give an immediate error with the second octet been out of range.
O well, I'm sure you'll be able to explain the trace tomorrow for me.
Will post the trace tomorrow, I know the trace bounced off everywhere, and the "overflowing the buffer" sounds right, but I'm just surprised that the command prompt didn't give an immediate error with the second octet been out of range.
O well, I'm sure you'll be able to explain the trace tomorrow for me.
Soldato
- Joined
- 12 Apr 2004
- Posts
- 11,788
- Location
- Somewhere
Sounds most probable.phykell said:
Add some error handling as well. Your code should probably raise an exception if someone tries to enter a number > 255.~J~ said:Well I hope at least one of you is right 'cos we've been scratching our heads on this one!
Will post the trace tomorrow, I know the trace bounced off everywhere, and the "overflowing the buffer" sounds right, but I'm just surprised that the command prompt didn't give an immediate error with the second octet been out of range.
O well, I'm sure you'll be able to explain the trace tomorrow for me.
phykell said:
O that's all sorted. I was just testing a dummy IP address and by chance entered the 192 (as you do!), a random number, and thought "Well nowt is gonna have 255.255" so I entered that!
I think the common response is correct, that the overflow is kicking in, but like I said, I'm just surprised the Ping in command prompt didn't give an error.
Associate
- Joined
- 18 Oct 2002
- Posts
- 2,055
- Location
- Brighton, UK
from Windows
from Linux
What version of windows are you using?
from Linux
What version of windows are you using?
I'm sorry, I completely misunderstood you then but you said that you were writing a program to test the validity of an IP address and you certainly *didn't* say you entered it into the command prompt specifically. I thought you meant you'd put the IP address into your program~J~ said:Ping 192.759.255.255
Did say in my recent post that I did this in the Command Prompt.
I have no idea why a Windows command prompt version of ping would work on such an IP address assuming it was a Windows command prompt version. I've written my own ping program in the distant past, in C, and one of the things I checked for was that the octets were valid.
Windows XP SP2.
Trying from my machine, I get the error I'd expect, " Ping request could not find host 192.759.255.255. Please check the name and try again."
Bottom line is it's not that important, I can test with a PC that I know is off, I'm just confused overall as to why I get a response.
The 2 lines I've omitted are 1) Our domain, and 2) our router. Other than that, what you see is what I got.
Trying from my machine, I get the error I'd expect, " Ping request could not find host 192.759.255.255. Please check the name and try again."
Bottom line is it's not that important, I can test with a PC that I know is off, I'm just confused overall as to why I get a response.
The 2 lines I've omitted are 1) Our domain, and 2) our router. Other than that, what you see is what I got.
phykell said:The real question is, is it repeatable? If it isn't, are you sure you saw what you say you saw?
LOL - you wanna come to the office
Yeah it's repeatable, 100%. Can't get it on my machine at home, unless I VPN into work, and then I can ping it. Each and every machine in the office (on the domain) can ping to it too.
I'll create a movie as proof!!
