how to enable wireguard service in freebsd14.2?

fff2024g

fff2024g

Dear all :
I know the wg is enabled in freebsd14.2 . but when i create wg2000.conf in /user/local/etc/wireguard/ folder, i want to start wireguard service with "service wireguard start " command in shell. "no wireguard service" output in the shell. how can i enable wg service in freebsd 14.2 ? thanks.

note : i don't install any wireguard pkg. just use the wg command to do anything. thanks.

pkg search wireguard
wireguard-go-0.0.20230223_11,1 WireGuard implementation in Go
wireguard-tools-1.0.20210914_3 Fast, modern and secure VPN Tunnel
wireguard-tools-lite-1.0.20210914_3 Fast, modern and secure VPN Tunnel (lite flavor)

i don't install any wireguard pkg , just use wg command. thanks.
 
Have you got what you need in rc.conf? (I don't use wireguard just searching the internet):

See e.g.

Sparkee

PF Thread 'Wireguard network setup'

I'm working on setting up my first wireguard server on FreeBSD 13.3.

The issue: once I start the wireguard service I can't reach the server anymore, the server still can access the internet but nothing can connect to it. The server is in the cloud.
On the same server I'm running an openvpn server, there are no issues there.
Do you have an idea what should I try? What did I miss?

rc.conf
Code: 
...
wireguard_enable="YES"
wireguard_interfaces="wg0"

wg0.conf
Code: 
[Interface]
Address = 10.9.0.1/32 # address the server will bind to
ListenPort = 51820 # listener port
PrivateKey = ***

[Peer]
AllowedIPs =...
  • Sparkee
  • nat pf conf wireguard pf wireguard server wirguard
  • Replies: 8
  • Forum: Firewalls
 
Last time I checked, there was no service script for wireguard. So you will have to copy it from wireguard-tools-lite.
So if you put this files in /usr/local/etc/rc.d/wireguard
Code: 
#!/bin/sh

# PROVIDE: wireguard
# REQUIRE: NETWORKING
# KEYWORD: shutdown
#
# wireguard_enable (bool):        Set to "YES" to enable wireguard.
#                                 (default: "NO")
#
# wireguard_interfaces (str):     List of interfaces to bring up/down
#                                 on start/stop. (eg: "wg0 wg1")
#                                 (default: "")
# wireguard_confdir (str):        Config directory that contains wg0.conf
#                                 (default: "/usr/local/etc/wireguard")
# wireguard_<iface>_ips (str):    List of IP Addresses for iface
# wireguard_<iface>_routes (str): List of Routes for this iface
# wireguard_<iface>_mtu (str):    MTU for iface (default: "1500")

. /etc/rc.subr

name=wireguard
rcvar=wireguard_enable
extra_commands="reload status"

start_cmd="${name}_start"
stop_cmd="${name}_stop"
reload_cmd="${name}_reload"
status_cmd="${name}_status"

wireguard_start()
{
	for interface in ${wireguard_interfaces}; do
		load_rc_config wireguard_${interface}

		eval wireguard_ips="\${wireguard_${interface}_ips}"
		eval wireguard_routes="\${wireguard_${interface}_routes}"
		eval wireguard_mtu="\${wireguard_${interface}_mtu}"

		ifconfig ${interface} create
		/usr/bin/wg setconf ${interface} ${wireguard_confdir}/${interface}.conf

		for ip in ${wireguard_ips}; do
			if [ "${ip#*:}" != "${ip}" ]; then
				ifconfig ${interface} inet6 ${ip} alias
			else
				ifconfig ${interface} inet ${ip} alias
			fi
		done

		if [ ! -z "${wireguard_mtu}" ]; then
			ifconfig ${interface} mtu ${wireguard_mtu}
		fi

		ifconfig ${interface} up

		for route in ${wireguard_routes}; do
			if [ "${route#*:}" != "${route}" ]; then
				route -q -n add -inet6 ${route} -interface ${interface}
			else
				route -q -n add -inet ${route} -interface ${interface}
			fi
		done
	done
}

wireguard_stop()
{
	for interface in ${wireguard_interfaces}; do
		load_rc_config wireguard_${interface}

		eval wireguard_routes="\${wireguard_${interface}_routes}"

		for route in ${wireguard_routes}; do
			if [ "${route#*:}" != "${route}" ]; then
				route -q -n delete -inet6 ${route} -interface ${interface}
			else
				route -q -n delete -inet ${route} -interface ${interface}
			fi
		done

		ifconfig ${interface} down

		ifconfig ${interface} destroy
	done
}

wireguard_reload()
{
	for interface in ${wireguard_interfaces}; do
		/usr/bin/wg syncconf ${interface} ${wireguard_confdir}/${interface}.conf
	done
}

wireguard_status()
{
	wireguard_status="0"

	for interface in ${wireguard_interfaces}; do
		/usr/bin/wg show ${interface} || wireguard_status="1"
	done

	return ${wireguard_status}
}

load_rc_config $name

: ${wireguard_enable="NO"}
: ${wireguard_interfaces=""}
: ${wireguard_confdir="/usr/local/etc/wireguard"}

run_rc_command "$1"
It should work.
 
monwarez said:
Last time I checked, there was no service script for wireguard. So you will have to copy it from wireguard-tools-lite.
So if you put this files in /usr/local/etc/rc.d/wireguard
Code: 
#!/bin/sh

# PROVIDE: wireguard
# REQUIRE: NETWORKING
# KEYWORD: shutdown
#
# wireguard_enable (bool):        Set to "YES" to enable wireguard.
#                                 (default: "NO")
#
# wireguard_interfaces (str):     List of interfaces to bring up/down
#                                 on start/stop. (eg: "wg0 wg1")
#                                 (default: "")
# wireguard_confdir (str):        Config directory that contains wg0.conf
#                                 (default: "/usr/local/etc/wireguard")
# wireguard_<iface>_ips (str):    List of IP Addresses for iface
# wireguard_<iface>_routes (str): List of Routes for this iface
# wireguard_<iface>_mtu (str):    MTU for iface (default: "1500")

. /etc/rc.subr

name=wireguard
rcvar=wireguard_enable
extra_commands="reload status"

start_cmd="${name}_start"
stop_cmd="${name}_stop"
reload_cmd="${name}_reload"
status_cmd="${name}_status"

wireguard_start()
{
    for interface in ${wireguard_interfaces}; do
        load_rc_config wireguard_${interface}

        eval wireguard_ips="\${wireguard_${interface}_ips}"
        eval wireguard_routes="\${wireguard_${interface}_routes}"
        eval wireguard_mtu="\${wireguard_${interface}_mtu}"

        ifconfig ${interface} create
        /usr/bin/wg setconf ${interface} ${wireguard_confdir}/${interface}.conf

        for ip in ${wireguard_ips}; do
            if [ "${ip#*:}" != "${ip}" ]; then
                ifconfig ${interface} inet6 ${ip} alias
            else
                ifconfig ${interface} inet ${ip} alias
            fi
        done

        if [ ! -z "${wireguard_mtu}" ]; then
            ifconfig ${interface} mtu ${wireguard_mtu}
        fi

        ifconfig ${interface} up

        for route in ${wireguard_routes}; do
            if [ "${route#*:}" != "${route}" ]; then
                route -q -n add -inet6 ${route} -interface ${interface}
            else
                route -q -n add -inet ${route} -interface ${interface}
            fi
        done
    done
}

wireguard_stop()
{
    for interface in ${wireguard_interfaces}; do
        load_rc_config wireguard_${interface}

        eval wireguard_routes="\${wireguard_${interface}_routes}"

        for route in ${wireguard_routes}; do
            if [ "${route#*:}" != "${route}" ]; then
                route -q -n delete -inet6 ${route} -interface ${interface}
            else
                route -q -n delete -inet ${route} -interface ${interface}
            fi
        done

        ifconfig ${interface} down

        ifconfig ${interface} destroy
    done
}

wireguard_reload()
{
    for interface in ${wireguard_interfaces}; do
        /usr/bin/wg syncconf ${interface} ${wireguard_confdir}/${interface}.conf
    done
}

wireguard_status()
{
    wireguard_status="0"

    for interface in ${wireguard_interfaces}; do
        /usr/bin/wg show ${interface} || wireguard_status="1"
    done

    return ${wireguard_status}
}

load_rc_config $name

: ${wireguard_enable="NO"}
: ${wireguard_interfaces=""}
: ${wireguard_confdir="/usr/local/etc/wireguard"}

run_rc_command "$1"
It should work.
Click to expand...
Dear

monwarez​

, if i don't want to use this script , just want to enable wg service , what we can do ?
 
richardtoohey2 said:
Have you got what you need in rc.conf? (I don't use wireguard just searching the internet):

See e.g.

Sparkee

PF Thread 'Wireguard network setup'

I'm working on setting up my first wireguard server on FreeBSD 13.3.

The issue: once I start the wireguard service I can't reach the server anymore, the server still can access the internet but nothing can connect to it. The server is in the cloud.
On the same server I'm running an openvpn server, there are no issues there.
Do you have an idea what should I try? What did I miss?

rc.conf
Code: 
...
wireguard_enable="YES"
wireguard_interfaces="wg0"

wg0.conf
Code: 
[Interface]
Address = 10.9.0.1/32 # address the server will bind to
ListenPort = 51820 # listener port
PrivateKey = ***

[Peer]
AllowedIPs =...
  • Sparkee
  • nat pf conf wireguard pf wireguard server wirguard
  • Replies: 8
  • Forum: Firewalls
Click to expand...
DEAr

richardtoohey2​

i don't use freebsd13. now i have used freebsd14.2 . this version have wg in the kernel. but i don't know how to active it . thanks.
 
richardtoohey2 said:
So have you got anything in rc.conf? Looks like you ned something in 14.x as well.

E.g.

Click to expand...
Dear richardtoohey2:
i can't open reddit link. our country block most website, so i want to build a vpn server . i want to use wireguard kernel mode to build server. can you show me some step. thanks.

note : if we used wireguard userland mode, we need to add below content.
#enable wireguard interface
wireguard_enable="yes"
wireguard_interfaces="wg2024"

but , if i use wireguard kernel mode, maybe we no need add it . thanks.
 
fff2024g, I use a small — just a few users — wireguard vpn server without any ports/packages. You need something like:
  1. Create wg2024 interface, sysrc cloned_interfaces+=wg2024;
  2. Add ip configuration for the interface, sysrc ifconfig_wg2024="inet vpn.server.ip.address/mask";
  3. Create /usr/local/etc/wireguard/wg2024.conf file;
  4. Create /usr/local/etc/devd/wireguard.conf with the following content:
Code: 
notify 0 {
        match "system"  "IFNET";
        match "type"    "LINK_UP";
        media-type      "unknown";

        action ". /etc/rc.subr
                . /etc/network.subr
                load_rc_config network
                if autoif $subsystem && [ -r /usr/local/etc/wireguard/$subsystem.conf ]
                then
                        /usr/bin/wg setconf $subsystem /usr/local/etc/wireguard/$subsystem.conf
                fi";
};

Should be enough to get started :cool:
 
fff2024g said:
Dear

monwarez​

, if i don't want to use this script , just want to enable wg service , what we can do ?
Click to expand...
This script is an rc.d service that run the wireguard service from base.
I am curious, did you remove all script in /etc/rc.d ? Because these are the same kind of script.

In FreeBSD, enabling a service is basically running an rc.d script that setup your service. So I really don't understand what you want here.
 
monwarez said:
In FreeBSD, enabling a service is basically running an rc.d script that setup your service. So I really don't understand what you want here.
Click to expand...
Isn't part of enabling a service also down to the /etc/rc.conf entries (which is the bit I keep asking the OP about)?

The sysrc commands you are recommending will do the /etc/rc.conf parts, won't they?

Not disagreeing with anything you've said, just asking if I'm on the right path re. /etc/rc.conf being part of the equation.

Then an rc.d script will use the settings you have put in /etc/rc.conf (or similar).

Like you, trying to understand a bit more what the OP is asking.
 
You guys, richardtoohey2, monwarez, answered in the begining on this thread how to set it up. There's no rc.d script in base, one needs to have wireguard-tools. I wonder if it's because of its GPL license (my speculation).

fff2024g wg-quick shows you what it does, example:
Code: 
[#] ifconfig wg create name wg0
[#] wg setconf wg0 /dev/stdin
[#] ifconfig wg0 inet 10.1.1.3/24 alias
[#] ifconfig wg0 mtu 1420
[#] ifconfig wg0 up
...
...

So I guess you could somehow make this into /etc/rc.conf though I'm not sure how you'd execute wg command from that (not without the helper script anyway). On top of it wg-quick calls "route monitor" and keeps it in background -- simple shell logic that keeps an eye on the connection. This you can't do without a script.

Bottom line -- you do need wireguard-tools which are not provided in base yet. Not in 14.2 as of now (Dec 10,2024).
 
richardtoohey2 said:
Isn't part of enabling a service also down to the /etc/rc.conf entries (which is the bit I keep asking the OP about)?

The sysrc commands you are recommending will do the /etc/rc.conf parts, won't they?

Not disagreeing with anything you've said, just asking if I'm on the right path re. /etc/rc.conf being part of the equation.

Then an rc.d script will use the settings you have put in /etc/rc.conf (or similar).

Like you, trying to understand a bit more what the OP is asking.
Click to expand...
Yes enabling a service require editing the /etc/rc.conf entries, but without a corresponding service files it is pointless.

The command in the /etc/rc.conf are only for setting the variables needed for the service files.
The service files itself lives in /etc/rc.d and /usr/local/etc/rc.d.

Since FreeBSD 14.2 does not ship with the rc script for wireguard, one have to write them.
To do so, I suggest taking the easier route, adapting the one from wireguard-tools-lite that does not depends on wg-quick.
The full configuration for rc.conf should looks like this (for a setup not using wg-quick)
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.2/24"

The symptoms described by the OP are
no wireguard service
Click to expand...
Which implies that there is no service files for wireguard, hence the instruction to create this service files using wireguard-tools-lite as a basis that will not require anything outside base.

On a side note, I don't understand why the service files that does not depends on wg-quick was not in base, maybe someone absolutely wanted to have a wg-quick equivalent or nothing ?

PS: maybe I was not clear enough, but the rc.d script that I presented earlier use the wireguard implementation from base.
 
dorjechang said:
fff2024g, I use a small — just a few users — wireguard vpn server without any ports/packages. You need something like:
  1. Create wg2024 interface, sysrc cloned_interfaces+=wg2024;
  2. Add ip configuration for the interface, sysrc ifconfig_wg2024="inet vpn.server.ip.address/mask";
  3. Create /usr/local/etc/wireguard/wg2024.conf file;
  4. Create /usr/local/etc/devd/wireguard.conf with the following content:
Code: 
notify 0 {
        match "system"  "IFNET";
        match "type"    "LINK_UP";
        media-type      "unknown";

        action ". /etc/rc.subr
                . /etc/network.subr
                load_rc_config network
                if autoif $subsystem && [ -r /usr/local/etc/wireguard/$subsystem.conf ]
                then
                        /usr/bin/wg setconf $subsystem /usr/local/etc/wireguard/$subsystem.conf
                fi";
};

Should be enough to get started :cool:
Click to expand...
DEar jorjechang:
it's not work for me . thanks.
 
monwarez said:
Yes enabling a service require editing the /etc/rc.conf entries, but without a corresponding service files it is pointless.

The command in the /etc/rc.conf are only for setting the variables needed for the service files.
The service files itself lives in /etc/rc.d and /usr/local/etc/rc.d.

Since FreeBSD 14.2 does not ship with the rc script for wireguard, one have to write them.
To do so, I suggest taking the easier route, adapting the one from wireguard-tools-lite that does not depends on wg-quick.
The full configuration for rc.conf should looks like this (for a setup not using wg-quick)
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.2/24"

The symptoms described by the OP are

Which implies that there is no service files for wireguard, hence the instruction to create this service files using wireguard-tools-lite as a basis that will not require anything outside base.

On a side note, I don't understand why the service files that does not depends on wg-quick was not in base, maybe someone absolutely wanted to have a wg-quick equivalent or nothing ?

PS: maybe I was not clear enough, but the rc.d script that I presented earlier use the wireguard implementation from base.
Click to expand...
DEar monwarez:
it's not work below code in freebsd14.2 .
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.2/24"

my requirement is > i don't want to install any wireguard packages in freebsd14.2 . just want to use wireguard kernel mode in freebsd14.2 . only one command we can use , just "wg" . thanks.
 
Dear all:
i don't install any wireguard packages in freebsd14.2. below is my step:
>ifconfig wg2024 create #this command will create a interface wg2024 in wg groups. and the if_wg kernel will autoload in the same time.
questions:. how to save this configure forever in freebsd14.2. where we can edit this configure file .

i try to create wg2024.conf in /usr/local/etc/wireguard/ with below code.
[Interface]
Address = 10.96.100.1/32 # address the server will bind to
ListenPort = 51820 # listener port
PrivateKey = <contents-of-server-privatekey> // 0MGukqgbg93xnsvEt6k2kv4Z7rPMYZJJRiGK3luzyUI=


[Peer]
AllowedIPs = 10.96.100.2/32
PreSharedKey = your-preshared-client-key // Zjs5LuEWl+jHu29sHowGZ24tievBkHhpdmllYujoUUs=
PublicKey = <contents-of-client-publickey> //rxMHhoCX/zzghCUBWTQ9bboTWyf0Zgur2d6lBunDJ2k=


looks like this configure file is right. but when i running wg setconf wg2024 wg2024.conf , got error in below .

root@safdasdfasdfasdf:/usr/local/etc/wireguard # wg setconf wg2024 wg2024.conf
Line unrecognized: `Address=10.96.100.1/32'
Configuration parsing error

i don;t know why ? can you help me . thanks.

note: don't add any code in /etc/rc.conf . thanks.
 
fff2024g said:
DEar monwarez:
it's not work below code in freebsd14.2 .
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.2/24"

my requirement is > i don't want to install any wireguard packages in freebsd14.2 . just want to use wireguard kernel mode in freebsd14.2 . only one command we can use , just "wg" . thanks.
Click to expand...
Again, I didn't said to install wireguard-tools-lite.
I said to create the wireguard service files in the correct location, taking inspiration from the one that came from wireguard-tools-lite.

Then you need to use the correct format for regular wireguard
Here a sample for the server (you can of course add the presharedkey too)
Code: 
[Interface]
PrivateKey = ThePrivateKey
ListenPort = PORT_WG

[Peer]
PublicKey = ThePublicKey
AllowedIPs = 10.0.0.2

[Peer]
PublicKey = ThePublicKey2
AllowedIPs = 10.0.0.3
With the following configuration on rc.conf
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.1/24"
wireguard_wg0_routes="10.0.0.0/24"
gateway_enable="YES"
And the client
Code: 
[Interface]
PrivateKey = ThePrivateKey

[Peer]
PublicKey = ThePublicKeyOfTheEndpoint
AllowedIPs = 10.0.0.0/24
Endpoint = EndpointIP:WG_PORT
PersistentKeepalive = 25
With the following configuration on rc.conf
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.2/24"
wireguard_wg0_routes="10.0.0.0/24"

Long story short: when you are not using wg-quick, you cannot tell which IP the peers gets, you have to do this in the rc.conf .

If you are not using the rc.d script, then you have to call all the required program:
Code: 
wg setconf wg0 /usr/local/etc/wireguard/wg0.conf
ifconfig wg0 inet 10.0.0.2 alias
ifconfig wg0 up
route -q -n add -inet 10.0.0.0/24 -interface wg0
 
monwarez said:
Again, I didn't said to install wireguard-tools-lite.
I said to create the wireguard service files in the correct location, taking inspiration from the one that came from wireguard-tools-lite.

Then you need to use the correct format for regular wireguard
Here a sample for the server (you can of course add the presharedkey too)
Code: 
[Interface]
PrivateKey = ThePrivateKey
ListenPort = PORT_WG

[Peer]
PublicKey = ThePublicKey
AllowedIPs = 10.0.0.2

[Peer]
PublicKey = ThePublicKey2
AllowedIPs = 10.0.0.3
With the following configuration on rc.conf
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.1/24"
wireguard_wg0_routes="10.0.0.0/24"
gateway_enable="YES"
And the client
Code: 
[Interface]
PrivateKey = ThePrivateKey

[Peer]
PublicKey = ThePublicKeyOfTheEndpoint
AllowedIPs = 10.0.0.0/24
Endpoint = EndpointIP:WG_PORT
PersistentKeepalive = 25
With the following configuration on rc.conf
Code: 
wireguard_enable="YES"
wireguard_interfaces="wg0"
wireguard_wg0_ips="10.0.0.2/24"
wireguard_wg0_routes="10.0.0.0/24"

Long story short: when you are not using wg-quick, you cannot tell which IP the peers gets, you have to do this in the rc.conf .

If you are not using the rc.d script, then you have to call all the required program:
Code: 
wg setconf wg0 /usr/local/etc/wireguard/wg0.conf
ifconfig wg0 inet 10.0.0.2 alias
ifconfig wg0 up
route -q -n add -inet 10.0.0.0/24 -interface wg0
Click to expand...
hi, monwarez :
below is my step in the VPN server .
1. add below code in /etc/rc.conf
#enable wireguard
wireguard_enable="yes"
wireguard_interfaces="wg2024"

2 . mkdir /usr/local/etc/wireguard/ and create wg2024.conf with below content.
[Interface]
Address = 192.168.200.1/24
PrivateKey = ffffffffffffffffffffY3vNddddddddddddNMnc=
ListenPort = 51820
Saveconfig = true

[Peer]
PublicKey = xxxxxxxxxxxxxxxOOdIaKfffffffffffffvCnQ=
PresharedKey = fgggggggggggggggggNYyxxxxxxxxxxxxxxxxxxxxxxx24Cg=
AllowedIPs = 192.168.200.2/24

note: if i don't reboot this server , the wg2024 interface will not appear . ok, when i reboot this server . the wg2024 interface still not appear .

so i want to do below step to enable wg2024 interface . is right ? thanks.

3. reboot this server . then active the wg2024 interface with below command
# wg setconf wg2024 /usr/local/etc/wireguard/wg2024.conf
Line unrecognized: `Address=192.168.200.1/24'
Configuration parsing error

now , i got a error when active wg2024 interface . please help me again. thanks.
 
Again, the syntax you are trying to use will not work.

Look at what monwarez showed you for the configuration file. You cannot use "Address".

You are mixing up two different configuration file formats, and it is not going to work.
 
richardtoohey2 said:
Again, the syntax you are trying to use will not work.

Look at what monwarez showed you for the configuration file. You cannot use "Address".

You are mixing up two different configuration file formats, and it is not going to work.
Click to expand...
Dear richardtoohey2:
ok. i modify my step in vpn server as below .
1. add below code in /etc/rc.conf
#enable wireguard
wireguard_enable="yes"
wireguard_interfaces="wg2024"
wireguard_wg2024_ips="192.168.200.1/24"
wireguard_wg2024_routes="192.168.200.0/24"

#enable ip packet forward
gateway_enable="yes"

2. 2 . mkdir /usr/local/etc/wireguard/ and create wg2024.conf with below content.
[Interface]
PrivateKey = fffffffffffffffffffffffffffffffffffffffffffffffMncdsd
ListenPort = 51820
#Saveconfig = true

[Peer]
PublicKey = sssssssssssssssssssssssssssssssssssssdf
PresharedKey = fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
AllowedIPs = 192.168.200.2

3. active wg2024 interface with below command .
wg setconf wg2024 /usr/local/etc/wireguard/wg2024.conf
Unable to modify interface: Device not configured

ok. i still got error , unable to modify interface : device not configured.

thanks. please help me .
 
fff2024g said:
Dear richardtoohey2:
ok. i modify my step in vpn server as below .
1. add below code in /etc/rc.conf
#enable wireguard
wireguard_enable="yes"
wireguard_interfaces="wg2024"
wireguard_wg2024_ips="192.168.200.1/24"
wireguard_wg2024_routes="192.168.200.0/24"

#enable ip packet forward
gateway_enable="yes"

...
3. active wg2024 interface with below command .
wg setconf wg2024 /usr/local/etc/wireguard/wg2024.conf
Unable to modify interface: Device not configured

ok. i still got error , unable to modify interface : device not configured.

thanks. please help me .
Click to expand...

You didn't created the interface with ifconfig, since you go with the manual route, it should be something like:
Code: 
ifconfig wg2024 create
wg setconf wg2024 /usr/local/etc/wireguard/wg2024.conf
ifconfig wg2024 inet 192.168.200.1/24 alias
ifconfig wg2024 up
route -q -n add -inet 192.168.200.0/24 -interface wg2024
 
monwarez said:
You didn't created the interface with ifconfig, since you go with the manual route, it should be something like:
Code: 
ifconfig wg2024 create
wg setconf wg2024 /usr/local/etc/wireguard/wg2024.conf
ifconfig wg2024 inet 192.168.200.1/24 alias
ifconfig wg2024 up
route -q -n add -inet 192.168.200.0/24 -interface wg2024
Click to expand...
error:
wg setconf wg2024 /usr/local/etc/wireguard/wg2024.conf
fopen: No such file or directory
 
dear all:
i have find some way to build wireguard interface , but this time . the vpn can't work . please see below information :
server :
wg
interface: wg999
public key: sssss
private key: (hidden)
listening port: 58000

peer: ccccc
allowed ips: 192.168.200.0/24


client:
wg
interface: wg222
public key: ccccc
private key: (hidden)
listening port: 41799

peer: sssss
endpoint: 47.120.21.255:58000
allowed ips: 192.168.200.0/24
transfer: 0 B received, 2.17 KiB sent


now, we can see the vpn can't handshark success , i don't know why and keep search ,study ...thanks. please help me .
 
fff2024g said:
dear all:
i have find some way to build wireguard interface , but this time . the vpn can't work . please see below information :
server :
wg
interface: wg999
public key: sssss
private key: (hidden)
listening port: 58000

peer: ccccc
allowed ips: 192.168.200.0/24

...

now, we can see the vpn can't handshark success , i don't know why and keep search ,study ...thanks. please help me .
Click to expand...
Can you show us the server configuration and the client one ?
It seems weird that the client use 192.168.200.0 ip, from the previous discussion it seems that the client was 192.168.200.2
 
You must log in or register to reply here.
Back
Top