https://netmaker.org logo
Powered by
```root@vpn:~# docker ps CONTAINER ID IMAGE ...
# install
f
Copy code
root@vpn:~# docker ps
CONTAINER ID   IMAGE                              COMMAND                  CREATED          STATUS          PORTS                                                                             NAMES
8dfc68ab6a19   coredns/coredns                    "/coredns -conf /roo…"   53 minutes ago   Up 53 minutes   53/tcp, 53/udp                                                                    coredns
0611a7a20db2   gravitl/netmaker-ui:v0.16.0        "/docker-entrypoint.…"   53 minutes ago   Up 53 minutes   80/tcp                                                                            netmaker-ui
1a0a1c002e7b   eclipse-mosquitto:2.0.11-openssl   "/docker-entrypoint.…"   53 minutes ago   Up 53 minutes   1883/tcp, 8883/tcp                                                                mq
6c8838965bad   traefik:v2.6                       "/entrypoint.sh --ce…"   53 minutes ago   Up 53 minutes   80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp                                     traefik
c05bcf487d2b   gravitl/netmaker:v0.16.0           "./netmaker"             53 minutes ago   Up 53 minutes   8081/tcp, 0.0.0.0:51821-51830->51821-51830/udp, :::51821-51830->51821-51830/udp   netmaker
root@vpn:~# docker exec -it netmaker /bin/bash
bash-5.1# wg show
bash-5.1#
j
how long ago? this was a bug in 0.15.2 that we fixed in 0.16.0
f
this is in 0.16 deployed about an hour ago
Removing the egress gateway fixed it
j
was this an upgraded server or a new server?
f
brand new
j
hmmmm ok
@bored-island-21407 can you take a look into this?
f
I deployed ubuntu 20.04 on a vultr vps this morning
I did set it up as a vpn using the ui vice cli options
b
if you try to recreate the egress does the problem come back
f
i can try
i tried using eth0 (what's in the container) and enp1s0 which is what the VPS has
b
and? same error?
f
yes
just tried again using eth0
b
can you exec into your container and post the contents /etc/netclient/config/nm-.conf
f
Copy code
bash-5.1# ls -l /etc/netmaker/
total 24
-rw-r--r--    1 1883     1883           119 Sep 26 15:46 root.key
-rw-r--r--    1 1883     1883           542 Sep 26 15:46 root.pem
-rw-r--r--    1 1883     1883           119 Sep 26 15:46 server.key
-rw-r--r--    1 1883     1883           587 Sep 26 15:46 server.pem
-rw-r--r--    1 1883     1883           119 Sep 26 15:46 serverclient.key
-rw-r--r--    1 1883     1883           554 Sep 26 15:46 serverclient.pem
no config directory
b
/etc/netclient
f
sorry
b
np
only interested in postup/postdown lines
f
Copy code
bash-5.1# cat /etc/netclient/config/nm-netmaker.conf 
[Interface]
PrivateKey = <redacted>
ListenPort = 51821
Address    = 10.101.255.254
PostUp     = `iptables -A FORWARD -i nm-netmaker -j ACCEPT ; iptables -A FORWARD -o nm-netmaker -j ACCEPT ; iptables -t nat -A POSTROUTING -o nm-netmaker -j MASQUERADE ;  ; iptables -A FORWARD -i nm-netmaker -j ACCEPT ; iptables -A FORWARD -o nm-netmaker -j ACCEPT ; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE ; `
PostDown   = `iptables -D FORWARD -i nm-netmaker -j ACCEPT ; iptables -D FORWARD -o nm-netmaker -j ACCEPT ; iptables -t nat -D POSTROUTING -o nm-netmaker -j MASQUERADE ;  ; iptables -D FORWARD -i nm-netmaker -j ACCEPT ; iptables -D FORWARD -o nm-netmaker -j ACCEPT ; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE ; `
MTU        = 1280

[Peer]
PublicKey  = DDa6DHmOc4V/TmLmt4+gKvYY7p5TiTDf3ujJsRwX5hU=
AllowedIps = 10.101.0.1/32
b
is there an ingress on the server as well?
f
ingress for what? Only thing ont he server it netmaker via the quickstart script
b
an ingress gateway
f
ah yes
there is
I thought it was required for external clients
b
it is, just trying to get a handle on what your network is
f
i just deployed it using the script to test out and made it an ingress and egress gateway
and created an external client for my phone to test
b
gotcha
f
Eventually I want to do somthing more complicated but my first attempt failed similarly to this
b
as a workaround you can delete the extra ; in the postup and postdown commands in /etc/netclient/config/nm-netmaker.conf and then run wg-quick up /etc/netclient/config/nm-netmaker.conf
f
So I tried to do something simpler (and started from scratch)
b
you have to do this inside the netmaker container
f
understood
b
and I found the actual bug
f
Thanks now it works as I expected
b
if you create the egress gateway and ingress second, you should not have and an issue but it you create the ingress first and then the egress this bug will show up
f
ok thanks. I'll probably tear it down and start again if you need me to check anything else
before I do
j
is this an easy fix we could get in the next release?
b
yes, two line change
2 Views
PreviousNext
Powered by