InGreenwood
@rr.com | reply to redhatnation
Re: Last octet 255 bug on Windows?
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. |
|
redhatnation
Premium
join:2005-06-02
Woodbridge, VA
 ·Comcast
| reply to Da Geek Kid
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 |
|
Da Geek Kid
join:2003-10-11
Mclean, VA
| reply to redhatnation
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. |
|
redhatnation
Premium
join:2005-06-02
Woodbridge, VA
·Comcast
| reply to Da Geek Kid
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? |
|
Da Geek Kid
join:2003-10-11
Mclean, VA
| reply to redhatnation
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 |
|
redhatnation
Premium
join:2005-06-02
Woodbridge, VA
·Comcast
| reply to koitsu
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 |
|
