Archived

This forum has been archived. Please start a new discussion on GitHub.

IPv6 and ssl

Hi,there

I have a question about the new feature Ipv6. I try the demo to test and find that IPv6 can not afford ssl protocol. Can you tell the detail ,or there is something I missing ?

cheers,
sober

Comments

  • benoit
    benoit Rennes, France
    Hi,

    IPv6 should work with IceSSL, if you're having some issues with getting it to work, please provide more information on your environment (OS, compiler, language, if you compiled Ice from sources or used a binary distribution) and more details on the issue (error/exception message, stack trace if available, etc).

    Cheers,
    Benoit.
  • Hi,

    In Ice-3.3b-VC90\demo\Ice\hello example, I made such changes:

    1. in Client.cpp
    HelloPrx twoway = HelloPrx::checkedCast(
    communicator()->propertyToProxy("Hello.Proxy")->ice_twoway()->ice_timeout(-1)->ice_secure(false));
    to
    HelloPrx twoway = HelloPrx::checkedCast(communicator()->stringToProxy("hello:ssl -p 8339 -h \"1030::c9b4:ff12:48aa:1a2b\""));

    2.config.client
    I uncomment this
    #Hello.Proxy=hello:tcp -p 10000:udp -p 10000:ssl -p 10001 -h "1030::c9b4:ff12:48aa:1a2b"

    3.config.server
    Hello.Endpoints=tcp -p 10000:udp -p 10000:ssl -p 10001 -h "1030::c9b4:ff12:48aa:1a2b"
    to
    Hello.Endpoints=ssl -p 8339 -h "1030::c9b4:ff12:48aa:1a2b"

    then I run it , the server shows;
    04/18/08 18:48:21.218 server: warning: connection exception:
    TransceiverI.cpp:229: Ice::ConnectionLostException:
    connection lost: recv() returned zero
    local address = 1030::c9b4:ff12:48aa:1a2b:8339
    remote address = 1030::c9b4:ff12:48aa:1a2b:1681
    04/18/08 18:48:21.281 server: warning: connection exception:
    TransceiverI.cpp:229: Ice::ConnectionLostException:
    connection lost: recv() returned zero
    local address = 1030::c9b4:ff12:48aa:1a2b:8339
    remote address = 1030::c9b4:ff12:48aa:1a2b:1682

    the client shows:
    client: Util.cpp:492: Ice::SocketException:
    socket exception: WSAENOTCONN

    4.in both config file
    I add Ice.IPv6=1


    I can see why .thanks.

    sober
  • benoit
    benoit Rennes, France
    I don't understand why the client is throwing this exception. I haven't been able to reproduce it on Windows Server 2003 R2.

    Which Windows version do you use? Did you try to see if it worked with the loopback interface IPv6 address or with tcp? Does the demo work with ssl & IPv4? Can you run the client & server with both tcp and ssl using IPv6 and with Ice.Trace.Network=2 and post the traces here?

    Also, could you describe a little more your network setup? Is the 1030::c9b4:ff12:48aa:1a2b address the address of an ethernet interface? Is it configured manually/automatically? Thanks.

    Cheers,
    Benoit.
  • 3x

    Hi,

    Things are like these:

    I use Windows xp sp2 ,the demo works well with IPv4 and IPv6 with tcp .

    And I configure the 1030::c9b4:ff12:48aa:1a2b address manually . The ethernet has two ip addresses ,and the other one is 192.168.1.128.

    I use ipconfig in command line:
    it shows:
    Windows IP Configuration


    Ethernet adapter Local Area Connection::

    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 192.168.1.128
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 1030::c9b4:ff12:48aa:1a2b
    IP Address. . . . . . . . . . . . : fe80::214:22ff:fe47:150d%4
    Default Gateway . . . . . . . . . : 192.168.1.1

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
    Default Gateway . . . . . . . . . :

    Tunnel adapter Automatic Tunneling Pseudo-Interface:

    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.128%2
    Default Gateway . . . . . . . . . :

    I do this to test if IPv6 works and for further use.

    Thank you !

    sober
  • benoit
    benoit Rennes, France
    Hi,

    Ok, I'm able to reproduce this issue on Windows XP SP2. We'll investigate.

    Thanks for the report.

    Cheers,
    Benoit.