| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | weird ping result.. |
Jean Parrot -> August Abolins said.. AA>> Anyone see anything unusual with this result: AA>> C:\Documents and Settings\Thnikpad>ping 192.168.0/1 AA>> Pinging 192.168.0/1 [67.215.65.132] with 32 bytes of data: AA>> Reply from 67.215.65.132: bytes=32 time=347ms TTL=49 JP> I do. If your are pinging your router, the transit time should JP> be 0 ms. Mine is. Why now, I have no clew. Maybe the line JP> should be dot dot dot, not dot dot slash, I used 192.168.0.1. You noticed more than what I expected from you. From an ex-pilot your attention to detail is pretty good. ;) The main thing that I thought was weird was the ping address itself. I erroneously entered 192.168.0/1 (with the slash), and got a result from 67.215.65.132. Further digging reveals that the address is part of the range assigned to OpenDNS. So, the address makes sense since OpenDNS is my DNS server. But I find it unusual that 192.168.x.x would produce an "outside" result, and not just limit it to the LAN. What do you get when you use a slash the same way? Do you get an address that represents your public DNS server? I have two routers in my LAN. The one wired to the cloud is 192.168.0.1 and produces a 2ms ping result. The other router connects into the first and provides the wi-fi to my "Thnikpad" with a 1ms round trip. JP> And it should be Thinkpad, not Thnikpad. "Thnikpad" is on purpose. The laptop arrived with that name. It flustered me a first, but then I grew to like its uniqueness. --- Thunderbird 2.0.0.24 (Windows/20100228)* Origin: Fidonet Via Newsreader - http://www.easternstar.info (1:123/789.0) SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 @PATH: 123/789 500 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.