Re: how to use different network(adapter/interface) to tunnel VPN server and client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jun 15, 2020 at 10:07 PM 江廷振 <r03a21033@xxxxxxxxxx> wrote:
>
> Hello
>
> I got two adapters. Each of them connect to a different network.
> I've configured Network A to have a higher priority by giving it a
> lower metric, and the other network(Network B) vice versa.
> I've established a static route to VPN server(ocserv) through network B.
> However, after I connect to VPN server by Openconnect(GUI-Windows),
> the default route to still seems to be through Network A.
> I do not know how to change it.

I don't understand the problem description sufficiently. Can you show
what your routing tables look like (`netstat -r` on Windows, I think)
look like before and after connecting to the VPN? Include both IPv6
and IPv4, if relevant.

> I've tried to add argument -i to assigning a different interface for
> Openconnect, but in vain.

Why do you think this will make a difference? In normal usage, the -i
/ --interface option only affects the *name* of the tunnel interface
*created* by OpenConnect; it does not affect prioritization of routes
through previously-existing network interfaces in any way.

Dan

_______________________________________________
openconnect-devel mailing list
openconnect-devel@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/openconnect-devel




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux