Intermediate node connectivity issue for JP node.
Noir16 opened this issue · 8 comments
What happened?
If fixed as a Japan exit node or intermediate node, it will not connect to nodes in other countries except for the same Japan node.
What did you expect to happen?
- Designate a relatively close node as an intermediate node.
- In privacy focus mode, intermediate nodes except the exit node will behave randomly.
How did you reproduce it?
Set the exit node option or intermediate node to JP.
Additional information
Debug-Info: https://support.safing.io/privatebin/?53472d351fca2133#GseAvyEVKvyoqvHbUxMyVgzyJxSagdr4P9i7TPWGNLRD
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
- 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
- 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.
I'm not sure I understand exactly what you mean. Please provide an example.
The Home Node or Transit Node will be pinned as shown below.
I live in an Asian country, and I think the node optimization is still a bit lacking for use in Asian countries.
For example, it would be ideal to connect through an Indonesia or an India or Singapore server, but in practice, nodes in Japan often only connect to each other.
Thanks, I now understand better.
The reason for this is that routes are (also) optimized based on speed.
In the case of the eastern Asia, connectivity between servers isn't all that great, so two servers next to each other will most of the times be the cheapest option Portmaster can calculate.
One way we can improve this, of course, is to spin up more nodes there. However, we are having difficulties finding good providers in that region that don't charge horrendous amounts for traffic. If you know any good providers, please do let us know!
We are thinking about adding a settings where users can choose to prioritize either speed, or proximity of the server to the destination (slower, also because more hops will often be involved.)
I think this could solve your issue on the client side. What do you think of this?
For now, I think it would be nice to have the ability to prioritize either speed or proximity.
Great! We might also merge it into the routing algorithm setting - we have to think this through first. It might get too complicated to understand when these are separated.
They control different aspects of the same thing, afterall.
This issue has been automatically marked as inactive because it has not had activity in the past two months.
If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.
If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.