That seems to solve it for me with the AnyConnect client.
$ docker run --network="host" ...
and then inside the container
output matches the host computer (as one would now expect).
- Dan Stoner
On Sat, May 9, 2020 at 10:24 AM Thad Megow <[log in to unmask]> wrote:
> Hey Dan!
> Have you tried using the docker host network driver, either on the docker daemon or in the docker run invocation?
> In the past that’s how I was able to access routes from my host computer.
> From: Platform Independent Linux List! <[log in to unmask]> on behalf of Dan Stoner <[log in to unmask]>
> Sent: Saturday, May 9, 2020 9:32:13 AM
> To: [log in to unmask] <[log in to unmask]>
> Subject: Docker container to private IP over UF VPN woes
> Is anyone successfully connecting from inside a docker container to a
> UF private IP address using a UF departmental VPN? (using
> "[log in to unmask]" as username)
> Is there a secret to getting openconnect to connect me to a departmental vpn ?
> I have tried Cisco AnyConnect as well as network-manager-openconnect
> gnome plugin.
> With AnyConnect, the host computer (my laptop) works as expected and I
> can connect to all of the internal UF resources. Inside a docker
> container, I lose all IP connectivity as soon as the UF VPN connection
> becomes active.
> With Openconnect (once I figured out I needed to check the "make
> connection available to other users box"), things work inside docker
> just as well as they work on the host computer. Unfortunately, with
> Openconnect the host computer also cannot access any internal UF
> resources, as if openconnect is having trouble getting me onto the
> departmental vpn at all.
> A few hours research hasn't led me to any solutions that work.
> Success and failure stories welcome.
> Dan Stoner