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

Assing multiple IP addresses to an n2n edge node #1166

Open
MurzNN opened this issue Mar 7, 2024 · 2 comments
Open

Assing multiple IP addresses to an n2n edge node #1166

MurzNN opened this issue Mar 7, 2024 · 2 comments

Comments

@MurzNN
Copy link

MurzNN commented Mar 7, 2024

Will be good to have the ability to assign multiple IP addresses to an edge node. Sometimes we need to make available the same port from the edge node but on different IP addresses.

For example:

192.168.100.1:443 - ip forwarding to localhost:443
192.168.100.2:443 - ip forwarding to 172.17.0.1:443

Yes, I can make this work by using a different port for the second service, but the services want to have them on the 443 port only, so this workaround doesn't work.

So, will be good to have something like this:

$ sudo edge -c mynetwork -k mysecretpass -a 192.168.100.1 -a 192.168.100.2 -f -l supernode.ntop.org:7777

If it's already possible, please describe me how to do this. Thanks!

@MurzNN
Copy link
Author

MurzNN commented Mar 7, 2024

I found a similar issue #743 but the suggested workaround from there doesn't work.
After executing this command:

ip addr add 192.168.100.2/24 dev edge0
ip route add 192.168.100.2 dev edge0

I can ping the 192.168.100.2 from the same node, but not from other nodes in the virtual network.

@hamishcoleman
Copy link
Collaborator

Are you able to retest this against the recently released fork n3n and raise a ticket there if you still cannot get it working? We would be happy to investigate it further as part of that new project.

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

No branches or pull requests

2 participants