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

Add option to allow specific nodes to reach the Internet over the AREDN host #1864

Open
KD4WLE opened this issue Jan 29, 2025 · 6 comments
Open
Labels
enhancement New feature or request

Comments

@KD4WLE
Copy link

KD4WLE commented Jan 29, 2025

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
A simple method in the GIU to add specific nodes to reach the Internet over the AREDN host with the ablity to use a wildcard (IE: KD4WLE* would allow any node starting with KD4WLE)

Describe alternatives you've considered
Specific instruction to add the firewall entries manualy

@KD4WLE KD4WLE added the enhancement New feature or request label Jan 29, 2025
@convolved-KY4G
Copy link

It might be pretty easy to guess a node name that would allow someone else to get the access you may be trying to exclude. Perhaps MAC addresses would be a better alternative? That wouldn't work well with the wildcards though. MACs can be cloned, but it seems like it would be harder to determine than node names.

@aanon4
Copy link
Contributor

aanon4 commented Feb 3, 2025

At a low level you are essentially asking the routing on each node to forward traffic not just based on destination but also on source. This is supported in IPv6 which we dont support, and "kind of" supported IPv4. It isn't supported by OLSR which is how we manage routes.

You could build a tunnel over the mesh (not to be confused with our current tunnels) between a gateway and the authorized node to achieve this.

But, aside from the complexity in doing this in a way to hide that complexity, you didnt provide a use case for this and I'd be interested in that.

@KD4WLE
Copy link
Author

KD4WLE commented Feb 3, 2025 via email

@aanon4
Copy link
Contributor

aanon4 commented Feb 3, 2025

But you already do that. I'm curious what this specific mechanism brings you.

@KD4WLE
Copy link
Author

KD4WLE commented Feb 3, 2025 via email

@jlp78
Copy link

jlp78 commented Feb 15, 2025

Here's a use case where it would be desirable...

Let's say I have several nodes that I control. One of them has a WAN connection to the internet. This node can easily install firmware updates or packages over the WAN. Other nodes that I control can't and I must manually download new firmware and push it to them (or run an on-mesh repository of releases and packages, which arguably is the right answer for this).

I would be satisfied with a way to allow DTD connected nodes to access the internet via my WAN connection, similarly to how I can allow my LAN connected hosts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants