There is a function inside network stack which is designed to solve the question of what network interface to use to reach a certain ipv4 address. (ipv4_route)
Unfortunately, it's implementation is incomplete, and is causing issues when more then one network interface is available.
In practice, most issues arise because default exit route (towards the internet) is hard coded to device 1.
There is a function inside network stack which is designed to solve the question of what network interface to use to reach a certain ipv4 address. (ipv4_route)
Unfortunately, it's implementation is incomplete, and is causing issues when more then one network interface is available.
In practice, most issues arise because default exit route (towards the internet) is hard coded to device 1.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There is a function inside network stack which is designed to solve the question of what network interface to use to reach a certain ipv4 address. (ipv4_route)
Unfortunately, it's implementation is incomplete, and is causing issues when more then one network interface is available.
In practice, most issues arise because default exit route (towards the internet) is hard coded to device 1.
Needs more testing (shouldn't we have a label for this?)
Lets close for now as we have a working intermediate solution