Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce function to determine if ZT comms channel to peer is relayed #6447

Merged
merged 1 commit into from
Aug 12, 2023

Conversation

StephenCWills
Copy link
Member

@StephenCWills StephenCWills commented Aug 11, 2023

Step 3 for retrieving route information for players in your game session. The NDP protocol is used to look up the virtual MAC address of the peer based on their virtual IPv6 address. That MAC address is passed into the ZT core function we added in diasurgical/libzt#12 to get their peer info. The peer ID can then be cross-checked against the ZT event messages we receive in our callback function to determine the status of the connection between peers.

Based on some of the testing I've done so far, the connection is typically relayed for the first few seconds after you join someone's game, after which it gets updated to a direct route. I had been hoping it would be good enough to just display a message when the player joins a game regarding whether the connection to their peers is relayed, but it seems like that wouldn't work. Probably it would be better to display this on demand, like maybe in response to a textcmd entry.

@AJenbo AJenbo added this to the 1.6.0 milestone Aug 11, 2023
@AJenbo AJenbo changed the base branch from master to development August 12, 2023 15:41
@AJenbo AJenbo merged commit 663c334 into diasurgical:development Aug 12, 2023
@StephenCWills StephenCWills deleted the libzt-peer-info branch August 12, 2023 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants