Network interface outgoing mess

yon 0

For example, when specifying the output to go through the wg interface, it will randomly output through an unspecified interface.

6:512:a::2 thie ip not bind JPVP interface. it s other interface's ip.

yon 0

After testing, I found that the problem was caused by a gateway error; the IPv4 gateway was affecting IPv6 routing.
After setting the IPv4 default gateway to automatic, a default gateway disappeared, causing the IPv6 router to stop working.

stephenw10

Hmm, you mean the default IPv6 gateway somehow was reset to 'none' without you actually making that change?

yon 0

@stephenw10 said in Network interface outgoing mess:

Hmm, you mean the default IPv6 gateway somehow was reset to 'none' without you actually making that change?

What I mean is that no matter which network interface I choose for traceroute, it is always incorrectly routed to the unspecified interface. For example, I selected the wg interface, but it actually uses the wg2 interface.

yon 0

stephenw10

What are you doing that triggers that error?

Selecting an interface in the gui traceroute only selects the source address. Normally on a WAN that will force traffic via that WANs gateway. But if there's no gateway set it will be routed using the system routing table like any other traffic.