On Mon, Feb 10, 2020 at 12:00:32 +0100, Reto Schneider wrote:
> addresses it never should. The devices it is running on are Yocto based,
> embedded, 32bit MIPS and deployed in remote networks which are not under
> my control.
[...]
> 5) Optional: Wifi comes up again, interface gets IP address and
Hi,
On 11/02/20 12:06, Reto Schneider wrote:
On 2/10/20 5:23 PM, Jan Just Keijser wrote:
the line
push "dhcp-option DNS 10.176.0.1"
is the main suspect here... my guess as to what happens is this:
1) VPN is started
2) that line causes the local /etc/resolv.conf file to be overwritten
with t
Hi Jan,
Thanks for your answer.
On 2/10/20 5:23 PM, Jan Just Keijser wrote:
>
> the line
> push "dhcp-option DNS 10.176.0.1"
> is the main suspect here... my guess as to what happens is this:
>
> 1) VPN is started
> 2) that line causes the local /etc/resolv.conf file to be overwritten
> with
Hi,
On 10/02/20 12:00, Reto Schneider wrote:
Hello,
I am observing the behavior of OpenVPN 2.4.7 trying to connect to IP
addresses it never should. The devices it is running on are Yocto based,
embedded, 32bit MIPS and deployed in remote networks which are not under
my control.
1) OpenVPN conn
Hello,
I am observing the behavior of OpenVPN 2.4.7 trying to connect to IP
addresses it never should. The devices it is running on are Yocto based,
embedded, 32bit MIPS and deployed in remote networks which are not under
my control.
1) OpenVPN connects successfully to server (example.com, TCP, P