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

applying phantom ipv4 address from the reg response #276

Closed

Conversation

0x90-n
Copy link
Contributor

@0x90-n 0x90-n commented Jul 11, 2024

Instead of having the station derive the phantom IPv4 for a given bidirectional registration that the station is informed about, let the station apply the IPv4 it receives from the reg server (inside the reg response).
This allows clients to dial phantoms that are not necessarily in the ClientConf subnets, given that they registered using the bidirectional api.

@0x90-n 0x90-n requested review from ewust and mingyech July 11, 2024 19:16
Copy link
Member

@ewust ewust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add support for IPv6?

@@ -429,14 +434,25 @@ func (rm *RegistrationManager) NewRegistrationC2SWrapper(c2sw *pb.C2SWrapper, in
c2s.TransportParams = rr.GetTransportParams()
}

// TODO: future, apply the ip addresses from the Registration response (rr.IPv4Addr, rr.IPv6Addr)
// apply the ip addresses from the registration response, if the Ipv4Addr is not empty
if rr.Ipv4Addr != nil && *rr.Ipv4Addr != 0 {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also allow override for IPv6, not just v4.

@0x90-n 0x90-n closed this Jul 11, 2024
@0x90-n 0x90-n deleted the apply_ipv4_overrides branch July 11, 2024 21:28
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