I have this document already, and I do understand that
this is a link local address. The fact that java generates
an execption and indicates this is an unsupported protocol
seems indicative of a problem with Windows and not the
application itself.
I may not be correct about this, but this exact same java application
works just fine on a Linux machine with link local addresses. I have a
Windows 2K O/S w/o IPv6 support. I added IPv6 support by downloading
a self-extracting archive from Microsoft that installed the dual stack IPv4/IPv6 on
my Windows 2K machine. So is it possible that the JVM does not bind to the IPv6
protocol stack due to the manual installation? How can I determine if the JVM is using
the IPv6 stack I manually installed properly? This seems to be the problem.
What I would like to do is try this same Java IPv6 Client/Server application on WindowsXP
with built in IPv6 support. Also, I am using j2se instead of j2ee. Perhaps there is a difference?
Let me know what you think ....
Thanks,
MarkL
sasson, shuki wrote:
No, read the IPv6 addressing RFC. FE80:: is a Link Local address. The
problem is that as an application one should specify the scope for this
address.
Actually the physical interface throughout the server is "listening" I don't
know what is the format for that for the java application.
I suggested that you would configure a global address in addition to the
Link Local (please read the addressing RFC if you do not understand) and
take it from there...
Here is a document that is a good introduction to IPv6 hope this helps,
Shuki
-----Original Message-----
From: Mark Leary [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 6:10 PM
To: sasson, shuki
Cc: [EMAIL PROTECTED]
Subject: Re: Windows IPv6 Support for Java
Hi Sasson,
When you mention a global address, do you mean
a multicast address? For example, my host machine
running windows2k looks like this ...
C:\>ipv6 if
Interface 2 (site 1): Local Area Connection
uses Neighbor Discovery
link-level address: 00-50-04-b6-21-5a
preferred address fe80::250:4ff:feb6:215a, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ffb6:215a, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 39000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 1 (site 0): Loopback Pseudo-Interface
does not use Neighbor Discovery
link-level address:
preferred address ::1, infinite/infinite
link MTU 1500 (true link MTU 1500)
current hop limit 1
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
Sh ould I be using the v6 address with the ff02:: prefix?
I am able to ping the fe80: : link local address from my
Linux machine just fine.
MarkL
sasson, shuki wrote:Hi Mark, fe80:: is a Link Local address. You have to supply a scope while
using such an address. I suggest you first try to use
a global address and see how this is working...
Shuki
-----Original Message-----
From: Mark Leary [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 15, 2002 12:06 AM
To: [EMAIL PROTECTED]
Subject: Windows IPv6 Support for Java
Folks,
I am doing some prototyping work with IPv6 on Windows2K.
I am using the Sun 1.4 Standard Edition of Java (J2SE). When
I run a simple server and try to create a socket with an IPv6
address I get the following error :
C:\java>java IPv6Server fe80::250:4ff:feb6:215a 1005
IPv6 Address: /fe80:0:0:0:250:4ff:feb6:215a
java.net.SocketException Protocol fam ily not supported
I was doing some reading on this subject and came across
a URL that exclaimed that Windows IPv6 support for
J2SE 1.4 is not supported by Sun.
Is this true? Has any one else encountered this?
Is there a work around ...?
Thanks,
MarkL
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
