Testing wireguard config on openwrt 21.02.3

Installing and Using OpenWrt Network and Wireless Configuration
1

I have been going around in circles with my wireguard config on openwrt 21.02.3 x86. I'm using my openwrt platform as the server(i know mute in wireguard as everyone is a peer) and a ubuntu laptop as a client. I see no traffic exchanged when I bring the link up on the laptop. Basic question about testing.. I'm assuming you could test wireguard on the lan side. I realize access is already present but I should see traffic on the wireguard segment.. no? I'm on Tmobile internet and thus can't access the public ip but I thought I could simulate a real connection by putting a static ip on the openwrt wan interface and connect my laptop to the wan port with another public ip on the same segment (i.e. nothing is really connected to the internet). This doesn't work as I can't ping the wireguard ip ...

Help!

2

You can test WG with both devices in the same LAN and have a proper handshake and connection. Obviously it doesn't serve any useful purpose, but it will work.

If you want guidance on your configs, post them here:

From the OpenWrt side, post both of the files noted below. On the other peer side, post your WG config file.

Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

cat /etc/config/network
cat /etc/config/firewall
3

Appreciate the quick response ..

I started from scratch with a new openwrt 21.02.3 image. Checked the time config and made sure it was updating. Loaded wireguard-tools, kmod, luci-app and luci-proto.

I used the following reference for creating the openwrt server config

I rebooted my openwrt host

I'm going to put the complete configs out here as they are meaningless ...

keys
client
private key
+Ed8UYcjWxeEAG0Svb/JdQLaPQFgx5jfrIKFNZYtmlk=
public key
fNuo2IdRYCDVuT+K388XJKPjiOVfzIs3Y5vFvkbeQVE=

server
priavte key
WIJu2sEK5CKZheYbXtYdBlxlLsmHX2+CRNc85WAf+mI=
public key
V16qPTK7HPPAwCY9mDuL8k3gv3TSysVueKLW8bBrbjI=

Ubuntu laptop acting as client

[Interface]
PrivateKey = +Ed8UYcjWxeEAG0Svb/JdQLaPQFgx5jfrIKFNZYtmlk=
Address = 192.168.9.2/32
#DNS = 1.1.1.1

[Peer]
PublicKey = V16qPTK7HPPAwCY9mDuL8k3gv3TSysVueKLW8bBrbjI=
Endpoint = 192.168.1.1:51820
AllowedIPs = 0.0.0.0/0, ::/0

type or paste code here
openwrt
network config

NETWORK

config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fdea:14f3:e265::/48'

config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'

config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'

config interface 'wan'
option device 'eth1'
option proto 'dhcp'

config interface 'wan6'
option device 'eth1'
option proto 'dhcpv6'

config interface 'vpn'
option proto 'wireguard'
option private_key 'WIJu2sEK5CKZheYbXtYdBlxlLsmHX2+CRNc85WAf+mI='
option listen_port '51820'
list addresses '192.168.9.1/24'
list addresses 'fdf1:e8a1:8d3f:9::1/64'

config wireguard_vpn 'wgclient'
option public_key 'fNuo2IdRYCDVuT+K388XJKPjiOVfzIs3Y5vFvkbeQVE='
list allowed_ips '192.168.9.2/32'
list allowed_ips 'fdf1:e8a1:8d3f:9::2/128'

FIREWALL

config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'

config zone 'lan'
option name 'lan'
list network 'lan'
list network 'vpn'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'

config zone 'wan'
option name 'wan'
list network 'wan'
list network 'wan6'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'

config forwarding
option src 'lan'
option dest 'wan'

config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'

config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'ACCEPT'

config rule
option name 'Allow-IGMP'
option src 'wan'
option proto 'igmp'
option family 'ipv4'
option target 'ACCEPT'

config rule
option name 'Allow-DHCPv6'
option src 'wan'
option proto 'udp'
option src_ip 'fc00::/6'
option dest_ip 'fc00::/6'
option dest_port '546'
option family 'ipv6'
option target 'ACCEPT'

config rule
option name 'Allow-MLD'
option src 'wan'
option proto 'icmp'
option src_ip 'fe80::/10'
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family 'ipv6'
option target 'ACCEPT'

config rule
option name 'Allow-ICMPv6-Input'
option src 'wan'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
list icmp_type 'router-solicitation'
list icmp_type 'neighbour-solicitation'
list icmp_type 'router-advertisement'
list icmp_type 'neighbour-advertisement'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'

config rule
option name 'Allow-ICMPv6-Forward'
option src 'wan'
option dest '*'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'

config rule
option name 'Allow-IPSec-ESP'
option src 'wan'
option dest 'lan'
option proto 'esp'
option target 'ACCEPT'

config rule
option name 'Allow-ISAKMP'
option src 'wan'
option dest 'lan'
option dest_port '500'
option proto 'udp'
option target 'ACCEPT'

config rule
option name 'Support-UDP-Traceroute'
option src 'wan'
option dest_port '33434:33689'
option proto 'udp'
option family 'ipv4'
option target 'REJECT'
option enabled 'false'

config include
option path '/etc/firewall.user'

config rule 'wg'
option name 'Allow-WireGuard'
option src 'wan'
option dest_port '51820'
option proto 'udp'
option target 'ACCEPT'

4

Add the following to this stanza:

	option route_allowed_ips '1'
5

Also keep in mind that if your DNS is not specified, you probably won't get normal internet access.... you should be able to ping by IP address (such as 8.8.8.8), but I'd expect domain names to fail.

6

The route allowed ip was the issue. Isn't that a shortcoming of the example?

I'm not worried about the DNS side of things as just want to access via ip some equipment on a remote site. Many thanks

Screenshot from 2022-08-30 05-35-13

7

As expected. No, I don't think it's a shortcoming -- the route allowed IPs option is basically a simplified method of adding routes to the main routing table. If it is not enabled, you must do it manually.

With DNS, I didn't expect that to be a primary issue, but wanted to make sure that wouldn't cause the impression of a failed connection even though it was working.

Needless to say, please discard these keys and use a fresh set should you actually deploy this across the internet. I'm sure you knew that, but just worth reiterating.

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.