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

The ability to define which WAN the proxy will use to initiate the connection? #3301

Open
vempire-ghost opened this issue Apr 19, 2024 · 5 comments
Labels

Comments

@vempire-ghost
Copy link

Currently, OMR routes all proxy traffic through the master WAN. Is it possible to configure the proxy to use another WAN to initiate connections instead of the master? This would allow keeping the master on one WAN, but having the proxy use another WAN to establish initial connections.

@Ysurac
Copy link
Owner

Ysurac commented Apr 19, 2024

I don't understand what you mean. Master define interface used for initial connection, it's the default gateway, so why using another connection and what would be master in this case ?

@vempire-ghost
Copy link
Author

I just want to direct the proxy connection to a WAN without having to define it as the default gateway. Perhaps using some firewall rule for that?

@aladdinshammr
Copy link

@vempire-ghost
What I could not understand is "What is the use of backup interface?"
It just stays idle there, and when the master connection goes down backup connection keeps sleeping.

@Ysurac
Copy link
Owner

Ysurac commented Apr 22, 2024

I don't think it's related to the subject, but backup interface is (or at least should be) used when master and interface set to "on" are down.

@vempire-ghost
Copy link
Author

vempire-ghost commented Apr 22, 2024

@vempire-ghost What I could not understand is "What is the use of backup interface?" It just stays idle there, and when the master connection goes down backup connection keeps sleeping.

The definition of "backup" in this context is for MPTCP, an interface with the "backup" flag will create a subflow but will only carry traffic if all other subflows become unavailable. This applies only to established connections; to initiate new connections, this parameter does not change anything.

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

No branches or pull requests

3 participants