Re: Last octet 255 bug on Windows? in Networking

Re: Last octet 255 bug on Windows? in Networking http://www.dslreports.com/forum/r18540749 en Fri, 27 Nov 2009 09:17:32 EDT Fri, 27 Nov 2009 09:17:32 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18548652 anon : Is there a way to ban redhatnation, or do we only get to ignore him?

We have enough misinformation here with out spreading it deliberately.]]> http://www.dslreports.com/forum/remark,18548652 Fri, 22 Jun 2007 08:22:26 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18547929 Da Geek Kid : ok.. Thanks for clarifying what I have said.

Heree are some clues you point out to from your links (neohapsis)

quote:
... However, the TCP/IP stack itself(tcpip.sys, ipsec.sys, etc)is a totally different beast.

... At most MS reused some of the high level concepts and algorithms with possible tiny bits and pieces of BSD support
routines (e.g., checksums, hashing,)

but than agaian, I am sure you have written most of the Red hat software all by yourself, redhatnation...
:D]]> http://www.dslreports.com/forum/remark,18547929 Thu, 21 Jun 2007 19:45:40 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18547748 redhatnation :

said by Da Geek Kid

:

maybe the bolded word above would better help you understand the point.

I remember you now -- Mr. Layer 2 router...

BTW, nice try. The TCP/IP stack used by MS was rewritten and contains zero code directly from the BSD stack. I just wanted to see if you'd bite...again.

Some of the TCP/IP utilities in MS contains BSD code -- and even the copyrights -- but the stack was completely rewritten.

»www.kuro5hin.org/?op=displaystor···641/7357

»archives.neohapsis.com/archives/···827.html

Come back when you aren't so wet behind the ears. lol]]> http://www.dslreports.com/forum/remark,18547748 Thu, 21 Jun 2007 19:13:59 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18545484 sirghost : Works just fine on vista....

Pinging 202.83.176.255 with 32 bytes of data:

Reply from 202.83.176.255: bytes=32 time=241ms TTL=43
Reply from 202.83.176.255: bytes=32 time=239ms TTL=41
Reply from 202.83.176.255: bytes=32 time=245ms TTL=43
Reply from 202.83.176.255: bytes=32 time=201ms TTL=43

Ping statistics for 202.83.176.255:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 245ms, Average = 231ms]]> http://www.dslreports.com/forum/remark,18545484 Thu, 21 Jun 2007 12:32:16 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18545054 Da Geek Kid :

said by redhatnation

said by Da Geek Kid

said by redhatnation

:

Works on a friggin Mac too:

$ ping 202.83.176.255
PING 202.83.176.255 (202.83.176.255): 56 data bytes
64 bytes from 202.83.176.255: icmp_seq=0 ttl=46 time=294.230 ms
64 bytes from 202.83.176.255: icmp_seq=1 ttl=46 time=289.899 ms
^C
--- 202.83.176.255 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 289.899/292.065/294.230/2.166 ms

Mac uses BSD TCP/IP and hence it MUST work... if it doesn't than it must be a user error ;)

Windows uses portions of the BSD TCP/IP stack too. Your point?

maybe the bolded word above would better help you understand the point.]]> http://www.dslreports.com/forum/remark,18545054 Thu, 21 Jun 2007 11:25:37 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18544616 redhatnation :

said by Da Geek Kid

said by redhatnation

Mac uses BSD TCP/IP and hence it MUST work... if it doesn't than it must be a user error ;)

Windows uses portions of the BSD TCP/IP stack too. Your point?]]> http://www.dslreports.com/forum/remark,18544616 Thu, 21 Jun 2007 10:11:02 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18544559 Da Geek Kid :

said by redhatnation

Mac uses BSD TCP/IP and hence it MUST work... if it doesn't than it must be a user error ;)]]> http://www.dslreports.com/forum/remark,18544559 Thu, 21 Jun 2007 10:00:39 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18544425 therube : Interesting (to me at least), I was checking out this Ping/Tracert/Lookup/... Tool,
eToolz, & I was able to successfully DNS, Ping, Trace, Whois from my XP Home system, though a HTTP-Header check returned, "Server not reachable!".]]> http://www.dslreports.com/forum/remark,18544425 Thu, 21 Jun 2007 09:34:40 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18543399 manfmmd : Seems like there are a few open ports:

C:\>nmap -v -v 202.83.176.255 Starting Nmap 4.20 ( http://insecure.org ) at 2007-06-20 23:23 Central DaylightTimeInitiating Parallel DNS resolution of 1 host. at 23:23Completed Parallel DNS resolution of 1 host. at 23:23, 0.03s elapsedInitiating SYN Stealth Scan at 23:23Scanning www.mavetju.org (202.83.176.255) [1697 ports]Discovered open port 22/tcp on 202.83.176.255Discovered open port 199/tcp on 202.83.176.255Discovered open port 802/tcp on 202.83.176.255Discovered open port 2604/tcp on 202.83.176.255Discovered open port 9102/tcp on 202.83.176.255Discovered open port 8443/tcp on 202.83.176.255Discovered open port 2601/tcp on 202.83.176.255Completed SYN Stealth Scan at 23:24, 55.77s elapsed (1697 total ports)Host www.mavetju.org (202.83.176.255) appears to be up ... good.Interesting ports on www.mavetju.org (202.83.176.255):Not shown: 1689 closed portsPORT     STATE    SERVICE22/tcp   open     ssh25/tcp   filtered smtp199/tcp  open     smux802/tcp  open     unknown2601/tcp open     zebra2604/tcp open     ospfd8443/tcp open     https-alt9102/tcp open     jetdirect Nmap finished: 1 IP address (1 host up) scanned in 58.188 seconds               Raw packets sent: 1768 (77.772KB) | Rcvd: 1733 (79.718KB) C:\>

]]> http://www.dslreports.com/forum/remark,18543399 Thu, 21 Jun 2007 00:25:42 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18543214 OZO : My Ethereal (v.0.10.14) on WXP Pro SP2 shows me that ICMP packets ("ping" command) are sent and received. At the same time I'm getting output from the "ping" command: Request timed out.

So, problem seems to be not in sending requests, but rather in interpreting replies. That, BTW, explains why we can tracert to up to this IP (but not the IP).
--
Keep it simple, it'll become complex by itself...]]> http://www.dslreports.com/forum/remark,18543214 Wed, 20 Jun 2007 23:43:54 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18543167 anon : You can try port 5666. It will immediately close, but it will show you if the TCP connection works with Vista.]]> http://www.dslreports.com/forum/remark,18543167 Wed, 20 Jun 2007 23:34:53 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18543141 koitsu :

said by trog

:

Might this be related to the XP parameter UseZeroBroadcast

Documentation on this states:
UseZeroBroadcast
Key: Tcpip\Parameters\Interfaces\ID for Adapter
Value Type: REG_DWORD - Boolean
Valid Range: 0 or 1 (False or True)
Default: 0 (False)
Description: If this parameter is set to 1 (True), the IP will use zeros-broadcasts (0.0.0.0) instead of ones-broadcasts (255.255.255.255). Most computers use ones-broadcasts, but some computers that are derived from BSD implementations use zeros-broadcasts. Computers that use different broadcasts do not interoperate well on the same network.

Peter

A good guess, but I think that's for very (repeat: VERY) old network configurations where broadcast traffic used to be sent across an all-zero address (e.g. x.x.x.0/24) instead of an all-ones address (e.g. x.x.x.255/24).

For comparison, I believe on Lucent/Livingston Portmasters, this is referred to as having a "high" (all ones) or "low" (zero) broadcast address. The default is "low", but the Portmaster does this out of paranoia/concern for very old OSes, where the broadcast was all zeros. On all of my Portmasters, I have to do a `set ether0 broadcast high` for broadcast traffic to work. Cross-reference:

»www.stat.ufl.edu/system/man/port···.fm.html
--
Making life hard for others since 1977.]]> http://www.dslreports.com/forum/remark,18543141 Wed, 20 Jun 2007 23:30:33 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18543109 anon : he said ping was fine, TCP doesn't work... try again with telnet (not that I can find an open port)

until TCP is confirmed I call Vista is broken as well]]> http://www.dslreports.com/forum/remark,18543109 Wed, 20 Jun 2007 23:23:20 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18543053 gilligun : Windows 2000 Professional SvcPk 4.....fail

Thru Sam Spade ........fail
--
Why do I have long hair?? It covers my bald spot!]]> http://www.dslreports.com/forum/remark,18543053 Wed, 20 Jun 2007 23:10:48 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18542957 trog : Might this be related to the XP parameter UseZeroBroadcast

Documentation on this states:
UseZeroBroadcast
Key: Tcpip\Parameters\Interfaces\ID for Adapter
Value Type: REG_DWORD - Boolean
Valid Range: 0 or 1 (False or True)
Default: 0 (False)
Description: If this parameter is set to 1 (True), the IP will use zeros-broadcasts (0.0.0.0) instead of ones-broadcasts (255.255.255.255). Most computers use ones-broadcasts, but some computers that are derived from BSD implementations use zeros-broadcasts. Computers that use different broadcasts do not interoperate well on the same network.

Peter]]> http://www.dslreports.com/forum/remark,18542957 Wed, 20 Jun 2007 22:55:28 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18542740 panda : Using my XP Pro laptop, I cannot ping but I can tracert;

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\NextStep>ping 202.83.176.255

Pinging 202.83.176.255 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 202.83.176.255:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\NextStep>tracert 202.83.176.255

Tracing route to www.mavetju.org [202.83.176.255]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.1.2
2 39 ms 24 ms 26 ms 10.9.95.1
3 38 ms 24 ms 26 ms at-1-1-0-1714.CORE-RTR1.BOS.verizon-gni.net [130
.81.9.225]
4 41 ms 26 ms 25 ms so-0-2-0-0.BB-RTR1.BOS.verizon-gni.net [130.81.2
0.84]
5 43 ms 27 ms 26 ms 0.so-5-2-0.XL1.BOS4.ALTER.NET [152.63.19.129]
6 114 ms 102 ms 99 ms 0.so-3-0-0.IL1.SAC1.ALTER.NET [152.63.48.37]
7 113 ms 98 ms 98 ms 0.so-2-0-0.IR1.SAC2.ALTER.NET [152.63.48.34]
8 305 ms 306 ms 306 ms so-5-0-0.XT1.SYD2.ALTER.NET [210.80.33.233]
9 329 ms 306 ms 306 ms so-3-2-0.GW5.SYD2.ALTER.NET [210.80.33.58]
10 430 ms 306 ms 306 ms barnet2-syd-gw.aspac.customer.alter.net [221.133
.215.62]
11 328 ms 306 ms 307 ms to-internet.hs2-bd8806.int.barnet.com.au [202.83
.178.178]
12 330 ms 306 ms 409 ms to-hs2.sjh-bd8806.int.barnet.com.au [202.83.178.
185]
13 329 ms 306 ms 409 ms nat2.barnet.com.au [202.83.178.242]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Strange...
--
"[He] couldn't get a clue if he stripped naked, rubbed himself with clue musk, went to the middle of the clue breeding grounds at the height of clue breeding season when it was full of horny clues and did the clue mating dance for days."]]> http://www.dslreports.com/forum/remark,18542740 Wed, 20 Jun 2007 22:19:40 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18542585 redhatnation : Works on a friggin Mac too:

$ ping 202.83.176.255
PING 202.83.176.255 (202.83.176.255): 56 data bytes
64 bytes from 202.83.176.255: icmp_seq=0 ttl=46 time=294.230 ms
64 bytes from 202.83.176.255: icmp_seq=1 ttl=46 time=289.899 ms
^C
--- 202.83.176.255 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 289.899/292.065/294.230/2.166 ms]]> http://www.dslreports.com/forum/remark,18542585 Wed, 20 Jun 2007 21:55:07 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18542515 Devanchya : See, Vista does not totally suck:

--
»www.codecipher.com - Marking the way to tomorrow's solutions]]> http://www.dslreports.com/forum/remark,18542515 Wed, 20 Jun 2007 21:44:36 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18542496 manfmmd : Also works on my Vista Laptop, but not my WinXP Laptop.]]> http://www.dslreports.com/forum/remark,18542496 Wed, 20 Jun 2007 21:42:34 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18541904 anon : »www.mavetju.org/weblog/html/00174.html
^-- found out what was the cause: strange classfull stack filtering.]]> http://www.dslreports.com/forum/remark,18541904 Wed, 20 Jun 2007 20:00:27 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18540832 Da Geek Kid : I would have someone else verify that... I hate to believe that MS actually fixed something...]]> http://www.dslreports.com/forum/remark,18540832 Wed, 20 Jun 2007 16:43:31 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18540749 Paulg : works in vista.]]> http://www.dslreports.com/forum/remark,18540749 Wed, 20 Jun 2007 16:25:54 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18540144 Da Geek Kid : that's been well known, BS MS TCPIP... This was one of the reasons we used to make fun of people taking MS TCP/IP test for MCSE... NT/2k and xp, and highly possible that vista won't work either...

They call this an advance TCP/IP feature... :D]]> http://www.dslreports.com/forum/remark,18540144 Wed, 20 Jun 2007 14:27:31 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18539358 DaSneaky1D : Confirmed again.

Linux = OK
XP = Not OK]]> http://www.dslreports.com/forum/remark,18539358 Wed, 20 Jun 2007 12:05:35 EDT Re: Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18539325 PetePuma : I hate to confirm that you appear to be right.

I tested this first on my home FIOS network. My Linux box on that network has no trouble reaching or rendering 202.83.176.255.

A Win2k box on the same network will fail immediately.

I also tried this on my XP Pro box at the office, with the same results as 2k.

There's no commonality amongst security software or firewalls on the 2 windows boxes, so I think this is a Windows-level thing. And frankly I'm quite surprised.

This article seems to indicate this is true:

»articles.techrepublic.com.com/51···906.html

"Specifically, Windows NT and 2000 do not allow the use of the X.X.X.255 or X.X.X.0 IP addresses. (For more information on this, see Microsoft Knowledge Base Article 281579.) Because the available hosts for this range of addresses will exceed our requirements, the loss of these few addresses will not be an issue."

KB 281579: »support.microsoft.com/kb/281579 seems to confirm this.]]> http://www.dslreports.com/forum/remark,18539325 Wed, 20 Jun 2007 11:58:53 EDT Last octet 255 bug on Windows? http://www.dslreports.com/forum/remark,18539206 koitsu : I'm sure I'm going to get a bunch of follow-ups lecturing me on netmasks despite my comprehension of them being quite decent, so I'll do my best to cover my bases while explaining the problem. :-)

An acquaintence of mine happens to manage a network as part of 202.83.176.0/21. The network, as far as what I've been told, is not subnetted into smaller blocks (that is, they do not split the network into separate /24s or otherwise). Heck, even if it was, it shouldn't matter (from my end).

The issue is that he's receiving reports of random Internet people not being able to reach 202.83.176.255 (ICMP echo, TCP port 80, or TCP port 8022). By "random" I mean he receives occasional mentions of it, but hasn't managed to figure out why those individuals have issues. I was baffled, thus offered to help.

I found that from my own LAN (192.168.1.0/255), my FreeBSD box has no problem pinging 202.83.176.255 or reaching either of the aforementioned TCP ports.

However, from my Windows XP box on the same LAN, packets never even make it out of the IP stack. I've sniffed using Wireshark on the Windows box, and packets aren't going out the wire. My local gateway also sees no such packets. Another acquaintence of mine (in Canada somewhere I believe) sees the same from his Windows machine.

Other addresses like 202.83.176.253 (to TCP port 80) work just fine from both BSD and Windows. It's as if Windows makes some blind assumption that any address ending in 255 is a broadcast address, rather than taking into consideration the local netmask.

There's apparently a history with the Windows IP stack doing retarded things when it comes to the last octet being 255, but according to the KB article, it only applies to Windows 98 and locally bound IP addresses (or something -- the KB article reads very badly and is vague):

»support.microsoft.com/kb/238727

There's a couple references I've found mentioning this problem, but none were conclusive; just lots of "I've seen on Windows..." and a forum post mentioning Cisco loopback addresses ending in 255 not playing well with Windows. But loopback is its own beast; I'm talking about publicly routed IP space here.

Does anyone here have something conclusive they can point me to documenting this problem? The workaround is pretty obvious (do not use addresses ending in 255), but the implications of that workaround should be obvious.

Thanks.
--
Making life hard for others since 1977.]]> http://www.dslreports.com/forum/remark,18539206 Wed, 20 Jun 2007 11:35:58 EDT