On Tue, 2 May 2017 19:08:10 +0200
"Jason A. Donenfeld" <[email protected]> wrote:
> DNS is solved using the PostUp line. See the man page example -- `man
> wg-quick`.
OK, I'm gonna see that.
> For your down error, can you send precise command line output?
Here's the startup:
# ./SERVER_WG_UP.sh
Démarrage du SERVEUR VPN WireGuard
[#] ip link add vpnserver type wireguard
[#] wg setconf vpnserver /dev/fd/63
[#] ip address add 10.11.12.1/24 dev vpnserver
[#] ip link set vpnserver up
[#] wg set vpnserver fwmark 51820
[#] ip -4 route add 0.0.0.0/0 dev vpnserver table 51820
[#] ip -4 rule add not fwmark 51820 table 51820
[#] ip -4 rule add table main suppress_prefixlength 0
SERVEUR VPN WireGuard démarré
The ifconfig output:
vpnserver Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.11.12.1
P-t-P:10.11.12.1 Mask:255.255.255.0 UP POINTOPOINT RUNNING NOARP
MTU:1420 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:4 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
The wg show vpnserver command output:
# wg show vpnserver
interface: vpnserver
public key: …
private key: (hidden)
preshared key: (hidden)
listening port: 1194
fwmark: 0xca6c
peer: …
allowed ips: 0.0.0.0/0
And finally the down command output:
# wg-quick down vpnserver
wg-quick: `vpnserver' is not a WireGuard interface
Jean-Yves
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard
