Hot answers tagged

4

I am accessing my home network with a VPN running in a docker container in my home server. That sounds similar to what you want to do. Here's how I configured it (using this docker image - note that the documentation of the docker image should be enough) Use a “convenience” environment variable to store the path to your persistent storage location that will ...


3

First, etcd is a core component in Kubernetes clusters. It is based on the Raft Consensus Algorithm and a weaker point with it is when the latency between the members (e.g. in the distribued etcd database) in the cluster is larger and vary more. It might work to deploy it with longer latency between the nodes (e.g. regions as in cross-region) but it might ...


3

I think that it's very difficult, if not impossible, to achieve something like this. The reason is that once the machine running Jenkins is connected to the VPN it is also effectively disconnected from the original network it was connected to, which means Jenkins on that machine will loose connection with the rest of your Jenkins setup. The only way that ...


3

Depending on your use-case, you should look either: Establishing a persistent VPN connection to the AWS VPC using the Site-To-Site VPN as described here: https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html Using an OpenVPN client via the build jobs using the client VPN service as described here https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/...


2

Is it possible to query Amazon DNS server from our corporate network trough the VPN tunnel? Directly? No. The recursive resolver available by default when you create a VPC can only be accessed by an IP address in that VPC. This is a restriction that Amazon imposes. What you can do is create a forwarder using the Route 53 Resolver service or software like ...


2

solutions is: OpenConnect Plugin See here: https://wiki.jenkins.io/display/JENKINS/OpenConnect+Plugin OR also you can use below method: On Linux (Debian based) sudo apt-get install openconnect Add the following lines to the bottom of /etc/sudoers (ubuntu configuration) jenkins ALL=NOPASSWD:/usr/sbin/openconnect* jenkins ALL=NOPASSWD:/bin/kill* Then ...


2

If you want to VPN for a jenkins task you would want to use the OpenConnect plugin as you mentioned. Here are the steps to do that: On linux (debian based) sudo apt-get install openconnect Add the following lines to the bottom of /etc/sudoers (ubuntu configuration) jenkins ALL=NOPASSWD:/usr/sbin/openconnect* jenkins ALL=NOPASSWD:/bin/kill* The you will ...


2

If you run docker run --rm -it alpine:3.7 /bin/sh, created docker container will use default bridge network. You can see the properties of this network using the following command: docker network inspect bridge. You can see there to which host interface (usually docker0) the network is associated and also what is the subnet for this network (usually 172.17....


1

It could be due to a "VPC DNS throttling", you can find more information on the official documentation. https://aws.amazon.com/premiumsupport/knowledge-center/vpc-find-cause-of-failed-dns-queries/


1

The githubixx wireguard ansible role might be what you are looking for. The author of the role says: I use WireGuard to setup a fully meshed VPN (every host can directly connect to every other host) and run my Kubernetes (K8s) cluster at Hetzner Cloud (but you should be able to use any hoster you want). So the important components like the K8s controller ...


1

You can use a ssh reverse proxy from any terminal (that has the ssh bin) to communicate with your applications. For instance try this on the client side: ssh -NL 3000:localhost:3000 root@10.10.10.1 This command won't print anything (except prompting for ssh key's password) and won't stop by itself. To kill the reverse proxy you can do ctrl + C Now you ...


1

For me it looks to be tunnel misconfigured - "there is a message about protocol mismatch" Regarding the limitations quick google took me here: [strongSwan] strongswan limits


1

I have fixed this partially by updating the routes.txt file in the installation folder for the client app by adding an entry for the subnet used by the gateway to assign IP address to new logins. While this now routes to the correct PC when RDPing, unfortunately a new IP is assigned to the PC every time it connects to the VPN, making it difficult to know ...


1

Yes, this is possible. You can create a private DNS zone for example.io using AWS route53 in the AWS VPC where your openvpn server is running. Then you can point server.example.io to the private IP of the instance. By default in AWS VPC, if a private DNS zone is present, it gets the preference. If the DNS record is not present, then it goes out of VPC for ...


1

VPC peering does not support transit traffic. Unsupported VPC Peering Configurations described several scenarious that are not supported. This case is not specifically mentioned, but is implicit from the other limitations. Note also that it is impossible to fully configure the setup you are attempting, because when you route a given destination towards ...


Only top voted, non community-wiki answers of a minimum length are eligible