# Beryl (GL-MT1300) bug on firmware 3.211, WireGuard Client configuration **URL:** \ **Category:** Router\ **Created:** [June 15, 2022, 6:41am UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297 "2022-06-15T06:41:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![sta](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/s/77aa72/32.png) [@sta](https://forum.gl-inet.com/u/sta)\ **Post date:** [June 15, 2022, 6:41am UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/1 "2022-06-15T06:41:59Z")
Hello Technical Support, I am using the Beryl (GL-MT1300) router and encountered an issue with manually adding a WireGuard Client on firmware 3.211. I have successfully reproduced the behaviour and found a workaround. What happens is that when I manually added a WireGuard Client by copy/paste in the config, it is able to save and is accepted. Then when I click on the Mangement tab to view the tunnel’s configuration, I see in the Interface IP Address field, it has put my IP address (from the copy/paste) and added “,MTU”. What it looks like is: Interface IP Address 10.6.0.3/24,MTU I discovered this by trying to troubleshoot why the tunnel wasn’t coming up and clicking modify to look at the config. After not changing anything, I clicked Apply and it gave me a message that the IP Address was invalid. That was when I noticed the extra “,MTU” in the IP Address field. By manually removing “,MTU”, it solved the problem right away and my tunnel came up. Let me know if you need more detail. Thanks, S ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [June 15, 2022, 9:15am UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/2 "2022-06-15T09:15:10Z")
Can you post the wireguard content? Just mark your keys. Maybe it is because of format differences. ---
**Author:** ![sta](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/s/77aa72/32.png) [@sta](https://forum.gl-inet.com/u/sta)\ **Post date:** [June 15, 2022, 3:10pm UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/3 "2022-06-15T15:10:22Z")
Hello @alzhao, Here is my WireGuard content from the .conf file. I used Windows notepad to view and copy the data into the WireGuard setup screen. I am using Chrome Version 102.0.5005.63 (Official Build) (64-bit). [Interface] PrivateKey = _ **REMOVED** _ Address = 10.6.0.3/24 MTU = 1420 DNS = 10.6.0.1 [Peer] PublicKey = _ **REMOVED** _ PresharedKey = _ **REMOVED** _ Endpoint = _ **REMOVED** _:51820 AllowedIPs = 0.0.0.0/0, ::0/0 ---
**Author:** ![wcs2228](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/wcs2228/32/6112_2.png) [@wcs2228](https://forum.gl-inet.com/u/wcs2228)\ **Post date:** [June 15, 2022, 5:02pm UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/4 "2022-06-15T17:02:11Z")
This looks like a variation of previously-reported WireGuard config parsing problems, where the “_MTU =_” line gets partially appended to the previously line (the “_MTU_” characters): > [@GL-MV1000 Brume 3.211 beta4: Wireguard IPv6 broken](https://forum.gl-inet.com/t/gl-mv1000-brume-3-211-beta4-wireguard-ipv6-broken/19472): > > Two issues I [encountered in 3.203](https://forum.gl-inet.com/t/mv1000-wireguard-ipv6-traffic-routing/16396/23) and wanted to test if they are resolved in 3.211 beta4: Pasting in a Wireguard client .conf That has an MTU= line, it will parse it wrong and instead of filtering it out or using the value, it puts it into the DNS server field instead If a Wireguard .conf has IPv6 GUA it will do bad input validation and claim the address is not valid. These are valid, working profiles that are fine in Android, Linux, Windows, MacOS wg client. Example config with docum… > [@GL-AR300M Wireguard Client](https://forum.gl-inet.com/t/gl-ar300m-wireguard-client/10564/9): > > GL-AR300M Firmware Version 3.201 My pivpn config looked like [Interface] PrivateKey = xxx Address = 10.6.0.3/24 MTU = 1420 [Peer] PublicKey = xxx PresharedKey = xxx Endpoint = xxx:51820 AllowedIPs = 0.0.0.0/0, ::0/0 I had to enter a „new line“ after line „ Address =“ and before „MTU =“. With this minor change, I was able to import config file in the text-field! As a workaround, you can try adding a newline before the “_MTU =_” line in the config file, so the setting is preserved. _I do not work for and I am not directly associated with GL.iNet_ ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [June 16, 2022, 4:30am UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/5 "2022-06-16T04:30:08Z")
I think it is a bug in old firmware. The current 3.215 beta has fixed that. I used your fortmat and it parse OK. ---
**Author:** ![sta](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/s/77aa72/32.png) [@sta](https://forum.gl-inet.com/u/sta)\ **Post date:** [June 17, 2022, 5:10am UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/6 "2022-06-17T05:10:30Z")
Thanks @alzhao. Do you recommend running the beta firmware then? Is it stable enough to be considered “stable”? ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [June 17, 2022, 7:23am UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/7 "2022-06-17T07:23:41Z")
Cannot sure 100% stable before it is released. But I tested and the format can be parsed correctly in snapshot. ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [October 29, 2025, 4:17am UTC](https://forum.gl-inet.com/t/beryl-gl-mt1300-bug-on-firmware-3-211-wireguard-client-configuration/22297/8 "2025-10-29T04:17:44Z")