Jerm
join:2000-04-10
Richland, WA | Re: So... Well it could be many things, but the example below is one option-
::EAT0:BEEF:4.2.2.1 | |
|
 Napsterbater
Premium
join:2002-12-28
Milledgeville, GA
 ·Windstream
 ·BroadVoice
1 edit | Re: So... said by Jerm  :Well it could be many things, but the example below is one option- ::EAT0:BEEF:4.2.2.1 That dose not seem to work. but 0:0:0:0:0:0:402:201 and ::402:201 do. Start -> run -> cmd -> "tracert ::402:201" Works
"tracert ::EAT0:BEEF:4.2.2.1" dose not. Not saying its not right but... meh. | |
|
 |
Jerm
join:2000-04-10
Richland, WA
| Re: So... From IPV6 Wikipedia article:
"A sequence of 4 bytes at the end of an IPv6 address can also be written in decimal, using dots as separators. This notation is often used with compatibility addresses (see below). This addressing scheme is convenient when dealing with the mixed environment of IPv4 and IPv6 addresses. The general notation is of the form x:x:x:x:x:x:d.d.d.d where x's are the 6 higher order hexadecimal digits whereas d's correspond to the decimal digits of lower order 8 bit pieces of address, as it is the IPv4 format. For example, ::ffff:12.34.56.78 is the same address as ::ffff:0c22:384e and 0:0:0:0:0:ffff:0c22:384e. Usage of this notation is deprecated and unsupported by numerous applications."
Note that last sentence, which means IPV6 in winblows is one of those "unsupported" configs... thanks MS!
»en.wikipedia.org/wiki/IPv6 | |
|
shashinka
join:2000-09-16
West Boylston, MA | hexadecimal doesn't include T 0-9,a-f | |
|
|
Jerm
join:2000-04-10
Richland, WA
1 edit | Re: So... oops yeah sorry:
feed.ea70.deaf.beef.f00d | |
|
|
|
|
