WireGuard/AmneziaWG client fails to apply config with long AllowedIPs list - "Unable to parse IP address"

Router VPN, DNS, Leaks
1

Device / Firmware:

  • Model: GL-MT3000 (Beryl AX)

  • Firmware: 4.9.0 beta4

  • Component: VPN > WireGuard Client (uploaded AmneziaWG-obfuscated .conf)

Uploading a valid WireGuard/AmneziaWG client config whose [Peer] section has a long, comma-separated AllowedIPs list (~30 CIDR entries, split-tunnel style excluding RFC1918 ranges) fails to bring up the tunnel. netifd logs a parse error on a truncated fragment of one of the CIDR entries, indicating the AllowedIPs value is being cut off at a fixed length (~255–256 characters) somewhere in the config pipeline before being handed to the IP-address parser.

AllowedIPs = 0.0.0.0/5, 8.0.0.0/7, 11.0.0.0/8, 12.0.0.0/6, 16.0.0.0/4, 32.0.0.0/3, 64.0.0.0/2, 128.0.0.0/3, 160.0.0.0/5, 168.0.0.0/6, 172.0.0.0/12, 172.32.0.0/11, 172.64.0.0/10, 172.128.0.0/9, 173.0.0.0/8, 174.0.0.0/7, 176.0.0.0/4, 192.0.0.0/9, 192.128.0.0/11, 192.160.0.0/13, 192.169.0.0/16, 192.170.0.0/15, 192.172.0.0/14, 192.176.0.0/12, 192.192.0.0/10, 193.0.0.0/8, 194.0.0.0/7, 196.0.0.0/6, 200.0.0.0/5, 208.0.0.0/4, 8.8.8.8/32, 1.1.1.1/32

Logs:

Sun Jul 12 18:30:27 2026 daemon.notice netifd: wgclient1 (9588): Unable to parse IP address: `192.160.'
Sun Jul 12 18:30:27 2026 daemon.notice netifd: wgclient1 (9588): Configuration parsing error
2

Not all ranges are rfc1918 compliance.

Please refer to rfc1918 on wikipedia there is a nice table which exactly show the ranges and cidr.

192.160 is not valid, it is 192.168.xx.xx the 64.xx is also invalid, 100.x.x.x range is not officially a rfc1918 based ip but still a private ip reserved by the IETF for cgnat.

Then the cidr are also questionable, I would advise to keep with the standards :), uneven cidr like 10.0.0.0/7 may be invalid, because /8 already takes the last 3 octals, and 5 will be surpassing it.

Is there a reason why 0.0.0.0/0 does not fullfill?

6

Hi,

Thank you for providing the detailed configuration.

We were able to reproduce this behavior.
We have recorded this issue and forwarded it to our R&D team for further investigation.