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

How is this different from n2n? #7

Closed
YCJDWCJI opened this issue Jan 1, 2024 · 7 comments
Closed

How is this different from n2n? #7

YCJDWCJI opened this issue Jan 1, 2024 · 7 comments

Comments

@YCJDWCJI
Copy link

YCJDWCJI commented Jan 1, 2024

Does it mean that n2n stops updating?

@hamishcoleman
Copy link
Contributor

There have been recent changes to the licensing arrangements in the n2n project that make some of the contributors uncomfortable.

It is hoped that discussions can change the license for the original n2n repo to address those concerns. This repository is a fork from immediately prior to those changes, that allows further development and improvements without being affected by the license changes.

@YCJDWCJI YCJDWCJI closed this as completed Jan 2, 2024
@eebssk1
Copy link

eebssk1 commented Apr 6, 2024

Are there any milestone or future plan on implementing highly demanding new features like p2p-via-ipv6 and FEC?

@hamishcoleman
Copy link
Contributor

Hi @eebssk1 , yes, there are definitely future plans. However work has been focused on getting the API changes stable and ready for the first release.

The IPv6 support is waiting for me to get a native IPv6 connection to test things with. Evaluating adding FEC requires some metrics to determine how often packets are being lost (and why) - if the packets are not being lost then FEC adds no value and if the packets are being lost due to minor issues with the protocol then fixing the protocol would provide better value than adding FEC

@eebssk1
Copy link

eebssk1 commented Apr 6, 2024

Hi @eebssk1 , yes, there are definitely future plans. However work has been focused on getting the API changes stable and ready for the first release.

The IPv6 support is waiting for me to get a native IPv6 connection to test things with. Evaluating adding FEC requires some metrics to determine how often packets are being lost (and why) - if the packets are not being lost then FEC adds no value and if the packets are being lost due to minor issues with the protocol then fixing the protocol would provide better value than adding FEC

It's good to hear that.

BTW pls check ntop/n2n#1165
Though I'm not having the problem now,seems like a edge case.

@hamishcoleman
Copy link
Contributor

There have been significant code changes since your debugging, so if you can reproduce it with the n3n code, then that would make investigations possible.

@eebssk1
Copy link

eebssk1 commented Apr 7, 2024

There have been significant code changes since your debugging, so if you can reproduce it with the n3n code, then that would make investigations possible.

I will check later. But I suppose the GUI does not support N3N since there are comandline handling changes?

@hamishcoleman
Copy link
Contributor

I've never used that GUI or looked at their code, so I'm not the right person to ask.

However - yes, the CLI has been almost completely changed (To improve consistency and simplify things for users - so if they were building their GUI again today, they would probably find it easier to do)

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

3 participants