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 route
> assigned (dhcpcd logs):
[...]
> 6) OpenVPN suddenly tries to connect to a faulty IP:
[...]
> In this case there seems to be a correlation to the router IP address in
> 5), but I have many more examples of unexplicable IP addresses (e.g.
> 1.1.1.11, 212.27.38.252, 192.168.246.123, ...), all of which are
> definitely not assigned to example.com.
How much do you know about the remote (Wifi) networks these clients are
connecting to? Is there a correlation between the different
inexplicable IP addresses used and the particular remote network for
that client?
In particular I'm wondering if these are networks where when you first
connect all traffic is directed to an "accept our terms of service"
page.... (In this case, it would seem to involve overriding DNS
responses from the networks local DNS server(s) so all domain names
point to the local IP of the system hosting that page.)
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
