Issue with mobile networks and ipv6 about yojimbo HOT 5 CLOSED

Well, it looks like I was not setting the client to have an ipv6 address. Which makes sense that it has to have that, if connecting to an ipv6 server.

Follow up question 1: Are connect tokens able to have one ipv4 and one ipv6 address in them?

Follow up question 2: I haven't seen any mechanism to switch a client from ipv4 to ipv6. Would you suggest just destroying the client and creating a new one with ipv6?

from yojimbo.

And, also when I attempt to generate an ipv6 address using the matcher it comes out with every other byte reversed.

from yojimbo.

Ahh, I see why the address is 'scrambled', the htons takes care of network byte order?

Well I've whittled it down to the netcode_socket_send_packet() function. It seems that sendto fails with the errno: invalid argument.

Alittle more info, I'm running OSX.

from yojimbo.

Yes, tokens can have an IPv4 address and IPv6 address in them. They support multiple addresses. You can see the spec for connect tokens on the netcode.io project.

It has been a while since I've worked with this library, so I don't remember. But the point at which you pass the client an address, eg. "0.0.0.0" or "::0" to bind to, is where it picks IPv4 vs. IPv6.

I don't remember if this is start/stop, but if it is, then that's all you need to do.

If it's in the CTOR, then yes, you need to destroy the client and recreate it to switch addresses.

As a feature request in the future, it seems reasonable to support a dual-stack server, such that it has a socket for IPv6, and a socket for IPv4 connections simultaneously.

from yojimbo.

I see. Thank you for the reply.

from yojimbo.