Hi,
has anybody an example how to successfully use open-tcp-server or open-tcp-client with IPv6 addresses? Once I tried and failed, now I forgot that I reported it already[1] and failed again.
(Note: I'm using gambit 0.9.2 - but it looks to me as if there is no related change since,.)
thanks so much
Jörg
Afficher les réponses par date
Hi all,
looks like things are a bit more strange. Maybe this issue is with lambdanative configuration.
I compiled another gambit and this does not segfault. However now I get an error: "address family not supported by protocol".
Am Tue, 14 Jul 2020 13:46:13 +0200 schrieb "Jörg F. Wittenberger" Joerg.Wittenberger@softeyes.net:
Hi,
has anybody an example how to successfully use open-tcp-server or open-tcp-client with IPv6 addresses? Once I tried and failed, now I forgot that I reported it already[1] and failed again.
(Note: I'm using gambit 0.9.2 - but it looks to me as if there is no related change since,.)
thanks so much
Jörg
I justed pushed a fix. For some reason the socket was always created with an address family of AF_INET, which is for IPv4. But I remember testing this in the past… mysterious!
Marc
On Jul 14, 2020, at 9:35 AM, Jörg F. Wittenberger Joerg.Wittenberger@softeyes.net wrote:
Hi all,
looks like things are a bit more strange. Maybe this issue is with lambdanative configuration.
I compiled another gambit and this does not segfault. However now I get an error: "address family not supported by protocol".
Am Tue, 14 Jul 2020 13:46:13 +0200 schrieb "Jörg F. Wittenberger" Joerg.Wittenberger@softeyes.net:
Hi,
has anybody an example how to successfully use open-tcp-server or open-tcp-client with IPv6 addresses? Once I tried and failed, now I forgot that I reported it already[1] and failed again.
(Note: I'm using gambit 0.9.2 - but it looks to me as if there is no related change since,.)
thanks so much
Jörg
Gambit-list mailing list Gambit-list@iro.umontreal.ca https://mailman.iro.umontreal.ca/cgi-bin/mailman/listinfo/gambit-list
Am Tue, 14 Jul 2020 12:56:20 -0400 schrieb Marc Feeley feeley@iro.umontreal.ca:
I justed pushed a fix. For some reason the socket was always created with an address family of AF_INET, which is for IPv4. But I remember testing this in the past… mysterious!
As you beat me with approximately 15'' wrt. the pull request (unbelievable; just the time it took me to dig out the issue number again) --- I wonder: is there a syntax to pass ipv6 addresses plus port numbers as a single string? Like "[::1]:80" ?
Thanks
Jörg
Hello Marc,
yesterdays patch works for open-tcp-server and friends.
However open-tcp-client still does not work for me.
I figured out that by supplying just a destination address like so:
(open-tcp-client '(address: '#16(0 0 0 0 0 0 0 1) port-number: 80))
the code would still try to set up the local address to AF_INET.
Supplying a local-address: component to the settings seems a bit wierd from a usability perspective, but at least it gets me past this point. But if I do, like so:
(open-tcp-client '(address: '#16(0 0 0 0 0 0 0 1) port-number: 80 local-address: '#16(0 0 0 0 0 0 0 1) port-number: 0))
I get an error "Cannot assign requested address". Likely this calls for an improvement of ##open-tcp-client in _io.scm. But I must admit that I don't grok this codes logic.
Best
Jörg
Am Tue, 14 Jul 2020 12:56:20 -0400 schrieb Marc Feeley feeley@iro.umontreal.ca:
I justed pushed a fix. For some reason the socket was always created with an address family of AF_INET, which is for IPv4. But I remember testing this in the past… mysterious!
Marc
On Jul 14, 2020, at 9:35 AM, Jörg F. Wittenberger Joerg.Wittenberger@softeyes.net wrote:
Hi all,
looks like things are a bit more strange. Maybe this issue is with lambdanative configuration.
I compiled another gambit and this does not segfault. However now I get an error: "address family not supported by protocol".
Am Tue, 14 Jul 2020 13:46:13 +0200 schrieb "Jörg F. Wittenberger" Joerg.Wittenberger@softeyes.net:
Hi,
has anybody an example how to successfully use open-tcp-server or open-tcp-client with IPv6 addresses? Once I tried and failed, now I forgot that I reported it already[1] and failed again.
(Note: I'm using gambit 0.9.2 - but it looks to me as if there is no related change since,.)
thanks so much
Jörg