forticlient

Connect to a FortiNet VPNs through docker

Run

The container uses the openfortivpn linux binary to manage ppp interface

All the container traffic is routed through the VPN, so you can in turn route host traffic through the container to access remote subnets.

With docker-compose (Default)

For run with docker compose you can use bellow steps:

Copy env/vpn/.env.example to env/vpn/.env
Fill your vpn identity on env/vpn/.env
Execute bellow command for run forticlient and http/socks5

### Without publish port
### Run two container: 1. forticlient 2.http/socks5
docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  up -d

Tip: If you use iptables legacy or old table you can fill environment variable RUNTIME_ENABLE_IPTABLES_LEGACY ( with any variable)

Also, you can run with own compose config. You can create a config compose file on docker/custom folder. This folder not tracked with source control.

Tip: You can add custom port for http/socks5 server without change in any compose file with below environment variable:

FORTI_PROXY_PORT (Default: 1080)

Other variables:

ENV Name	Service	Type	Default	Description
FORTI_PROXY_PORT	PROXY	TCP	1080	HTTP/SOCKS5 ports (multiplex port)
FORTI_DNS_PORT	DNS	TCP	1081	-
FORTI_DNS_PORT	DNS	UDP	1081	-
FORTI_SSH_PORT	SSH	TCP	1082	-

### With publish port on 127.0.0.1
### http/socks5 server: 127.0.0.1:8080
FORTI_PROXY_PORT=8080 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  up -d

With docker-compose (ssh server)

If you want to use ssh server follow bellow steps:

Copy env/vpn/.env.example to env/vpn/.env
Fill your vpn identity on env/vpn/.env
Copy env/ssh/.env.example to env/ssh/.env
Fill you ssh requirement authenticate on env/ssh/.env
Execute bellow command for run forticlient and ssh and http/socks5

### Without publish port
### Run three container: 
### 1. forticlient 
### 2. http/socks5 (Port: 1080) 
### 3. ssh (Port: 1082)
docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.ssh.yml \
  -f docker/docker-compose.ssh-env.yml \
  up -d

Also, you can run with own compose config. You can create a config compose file on docker/custom folder. This folder not tracked with source control.

Tip: You can add custom port for ssh and http/socks5 server without change in any compose file with two environment variable:

FORTI_SSH_PORT (Default: 1082)
FORTI_PROXY_PORT (Default: 1080)

### With publish port on 127.0.0.1
### http/socks5 server: 127.0.0.1:8080
FORTI_SSH_PORT=2020 FORTI_PROXY_PORT=8080 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.ssh.yml \
  -f docker/docker-compose.ssh-env.yml \
  up -d

With docker-compose (dns server)

If you want to use dns server follow bellow steps:

Copy env/vpn/.env.example to env/vpn/.env
Fill your vpn identity on env/vpn/.env 3Execute bellow command for run forticlient and dns and http/socks5

### Without publish port
### Run three container: 
### 1. forticlient 
### 2. http/socks5 (Port: 1080) 
### 3, dns (Port: 1081)
docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.dns.yml \
  up -d

Also, you can run with own compose config. You can create a config compose file on docker/custom folder. This folder not tracked with source control.

Tip: You can add custom port for dns and http/socks5 server without change in any compose file with two environment variable:

FORTI_DNS_PORT (Default: 1081)
FORTI_PROXY_PORT (Default: 1080)

### With publish port on 127.0.0.1
### http/socks5 server: 127.0.0.1:8080
### dns server: 127.0.0.1:1053
FORTI_DNS_PORT=1053 FORTI_PROXY_PORT=8080 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.dns.yml \
  up -d

With docker-compose (port forwarder)

If you want to use ssh server follow bellow steps:

Copy env/vpn/.env.example to env/vpn/.env
Fill your vpn identity on env/vpn/.env
Execute bellow command for run forticlient and http/socks5 and socat

### Without publish port
### Run three container: 1. forticlient 2.http/socks5 3, socat
FORTI_SOCAT_DEST_ADDR=remote-addr FORTI_SOCAT_DEST_PORT=3389 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.socat.yml \
  up -d

### With publish port on 127.0.0.1
### http/socks5 server: 127.0.0.1:1080
### socat server: 127.0.0.1:3389
FORTI_SOCAT_PORT=3389 FORTI_SOCAT_DEST_ADDR=remote-addr FORTI_SOCAT_DEST_PORT=3389 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.socat.yml \
  -f docker/docker-compose.socat-publish.yml \
  up -d

Also, you can run with own compose config. You can create a config compose file on docker/custom folder. This folder not tracked with source control.

Tip: You can add custom port for socat and http/socks5 server without change in any compose file with two environment variable:

FORTI_SOCAT_PORT (Default: 3389)

### With publish port on 127.0.0.1
### socat server: 127.0.0.1:3389
FORTI_SOCAT_DEST_ADDR=remote-addr FORTI_SOCAT_DEST_PORT=3389 FORTI_SOCAT_PORT=3389 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.ssh.yml \
  -f docker/docker-compose.ssh-env.yml \
  -f docker/docker-compose.ssh-publish.yml \
  up -d

With multi vpn instance

If you want using multi vpn instance with single compose file, You should follow bellow steps:

For run with docker compose you can use bellow steps:

Copy env/vpn/.env.example to env/vpn/vpn-1.env
Fill your vpn identity on env/vpn/vpn-1.env
Copy env/vpn/.env.example to env/vpn/vpn-2.env
Fill your vpn identity on env/vpn/vpn-2.env
You have to fill variable FORTI_VPN_ENV, It is path of env file you want use it
Execute bellow command for run forticlient and http/socks5

### Without publish port
### Run VPN-1
COMPOSE_PROJECT_NAME=vpn-1 FORTI_VPN_ENV=env/vpn/vpn-1.env docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  up -d

### With publish port on 127.0.0.1
### Run VPN-1 with http/socks5 publish port on port 8080
COMPOSE_PROJECT_NAME=vpn-1 FORTI_VPN_ENV=env/vpn/vpn-1.env FORTI_PROXY_PORT=8080 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  up -d
  
##############################################################

### Without publish port
### Run VPN-2
COMPOSE_PROJECT_NAME=vpn-2 FORTI_VPN_ENV=env/vpn/vpn-2.env docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  up -d

### With publish port on 127.0.0.1
### Run VPN-2 with http/socks5 publish port on port 8081
COMPOSE_PROJECT_NAME=vpn-2 FORTI_VPN_ENV=env/vpn/vpn-2.env FORTI_PROXY_PORT=8081 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  up -d

You can do same for port forwarder container:

### Run VPN-1 and forwarder RDP port to remote-server-1
### http/socks5 server: 127.0.0.1:1080
### socat server: 127.0.0.1:3389
COMPOSE_PROJECT_NAME=vpn-1 FORTI_VPN_ENV=env/vpn/vpn-1.env FORTI_PROXY_PORT=8080 FORTI_SOCAT_PORT=3389 FORTI_SOCAT_DEST_ADDR=remote-server-1 FORTI_SOCAT_DEST_PORT=3389 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.socat.yml \
  -f docker/docker-compose.socat-publish.yml \
  up -d
  
### Run VPN-2 and forwarder RDP port to remote-server-2
### http/socks5 server: 127.0.0.1:1081
### socat server: 127.0.0.1:3390
COMPOSE_PROJECT_NAME=vpn-2 FORTI_VPN_ENV=env/vpn/vpn-2.env FORTI_PROXY_PORT=1081 FORTI_SOCAT_PORT=3390 FORTI_SOCAT_DEST_ADDR=remote-server-2 FORTI_SOCAT_DEST_PORT=3389 docker-compose \
  -f docker-compose.yml \
  -f docker/docker-compose.env.yml \
  -f docker/docker-compose.socat.yml \
  -f docker/docker-compose.socat-publish.yml \
  up -d

Run forti client container

docker run -it \
  --device /dev/net/tun:/dev/net/tun \
  --device /dev/ppp:/dev/ppp \
  --cap-add NET_ADMIN \
  -e VPN_ADDR=host:port \
  -e VPN_USER=me@domain \
  -e VPN_PASS=secret \
  poyaz/forticlient:latest

Run forti client container (With port forwarder)

docker run -it \
  --name your-vpn-container-name \
  --device /dev/net/tun:/dev/net/tun \
  --device /dev/ppp:/dev/ppp \
  --cap-add NET_ADMIN \
  -p 3389:3389 \
  -e VPN_ADDR=host:port \
  -e VPN_USER=me@domain \
  -e VPN_PASS=secret \
  poyaz/forticlient:latest

### RDP port forwarder
docker run -it \
  --name your-forwarder-container-name \
  --network container:your-vpn-container-name \
  alpine/socat:latest tcp4-listen:3389,reuseaddr,fork tcp:your-rdp-destination-addr:3389

Two-factor authentication

This image now support two-factor authentication. List of support 2Fa in below:

Manual 2Fa (With a file)

The code listen the file and after write OTP on file you authenticate processed. Because we are on a container and don't have GUI

If your server using 2Fa, after the vpn authenticated successfully create lock file on storage/docker/2fa directory with name storage/docker/2fa/2fa.txt (If you use default variable for 2Fa), then you should put your OTP in this file, After you write your OTP in this file your authenticate has continued. if your OTP code is correct you vpn connect successfully.

Tip: You can change volume with below variable if you want to use another directory or file on a container, Then you should mount this folder on docker-compose file or docker run command

VPN_2FA_DIR (Default: /tmp/2fa/)
VPN_2FA_FILE (Default: /tmp/2fa/2fa.txt)

docker run -it \
  --device /dev/net/tun:/dev/net/tun \
  --device /dev/ppp:/dev/ppp \
  --cap-add NET_ADMIN \
  -v /tmp/my-custom-dir:/app
  -e VPN_ADDR=host:port \
  -e VPN_USER=me@domain \
  -e VPN_PASS=secret \
  -e VPN_2FA_DIR=/app \
  -e VPN_2FA_DIR=/app/my-2fa.txt
  poyaz/forticlient:latest

Usage

With ssh jump

If you want to connect another server you can use ssh jump with below sample:

ssh -o ProxyCommand="ssh -W %h:%p -p 1082 [email protected]" <username>@<target-host>

If your ssh server has been removed, and you create new ssh server (or recreated). You have Error: forwarding disabled due to host key check failure error and can fix with two way:

You have to remove previous host key from ~/.ssh/known_hosts
You can use bellow command for a skip ssh host key (Because we trust to this server)

ssh -o ProxyCommand="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -W %h:%p -p 1082 [email protected]" <username>@<target-host>

With http/socks5 tunnel

Another way we can use is http/socks5 tunnel. We can use this feature for connect to server or use for http/https request to server

ssh -oProxyCommand="nc -X 5 -x 127.0.0.1:1080 %h %p" <username>@<target-host>

With ip route

If you want to use ip route at first you should find container ip

### First find container ip
docker inspect --format '{{ .NetworkSettings.IPAddress }}' <container>

ip route add 10.201.0.0/16 via <container-ip>

ssh 10.201.8.1

With ip route (Own network)

# Create a docker network, to be able to control addresses
docker network create --subnet=172.20.0.0/16 fortinet

docker run -it \
  --device /dev/net/tun:/dev/net/tun \
  --device /dev/ppp:/dev/ppp \
  --cap-add NET_ADMIN \
  --net your-network-name --ip 172.20.0.2 \
  -e VPN_ADDR=host:port \
  -e VPN_USER=me@domain \
  -e VPN_PASS=secret \
  poyaz/forticlient:latest

# Add route for you remote subnet (ex. 10.201.0.0/16)
ip route add 10.201.0.0/16 via 172.20.0.2

# Access remote host from the subnet
ssh 10.201.8.1

Misc

If you don't want to use a docker network, you can find out the container ip once it is started with:

# Find out the container IP (You should get container with name "vpn")
docker inspect --format '{{ .NetworkSettings.IPAddress }}' <container>

Name		Name	Last commit message	Last commit date
Latest commit History 47 Commits
docker		docker
env		env
storage/docker		storage/docker
.config.yaml		.config.yaml
.env.example		.env.example
.gitignore		.gitignore
CHANGELOG.md		CHANGELOG.md
LICENSE.md		LICENSE.md
README.md		README.md
build.sh		build.sh
docker-compose.yml		docker-compose.yml

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

forticlient

Run

With docker-compose (Default)

With docker-compose (ssh server)

With docker-compose (dns server)

With docker-compose (port forwarder)

With multi vpn instance

Run forti client container

Run forti client container (With port forwarder)

Two-factor authentication

Manual 2Fa (With a file)

Usage

With ssh jump

With http/socks5 tunnel

With ip route

With ip route (Own network)

Misc

About

Releases

Packages

Languages

License

poyaz/docker-forticlient

Folders and files

Latest commit

History

Repository files navigation

forticlient

Run

With docker-compose (Default)

With docker-compose (ssh server)

With docker-compose (dns server)

With docker-compose (port forwarder)

With multi vpn instance

Run forti client container

Run forti client container (With port forwarder)

Two-factor authentication

Manual 2Fa (With a file)

Usage

With ssh jump

With http/socks5 tunnel

With ip route

With ip route (Own network)

Misc

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages