I know that we should be patient but when can expect this ?
I recently tried a v3 firmware on the MT300N V2 which was temporarily on the firmware web site and it worked well as a Wireguard server (unfortunately Wifi didn’t work).
I haven’t posted any comments or bug reports (as I subsequently read that until the v3 firmware is formally released it is not suitable for end user testing) but this this firmware looks really exciting !
MT300A has http://download.gl-inet.com/firmware/mt300a/testing/
MT300N-V2 does not. We did put the firmware there but there is problems so we withdraw. But we will test and put there soon.
Thanks Alzhao is the MT300A V3 firmware ready for end-user testing ?
I think so. If you have MT300A pls try.
I have both MT300N V2 and MT300A so will do thanks
Just an update trying the V3 firmware on my MT300A.
It is working well as both a Wireguard and Open VPN client via Wifi, USB tethering to a mobile phone and as an AP via Ethernet.
However it is impossible to change the Wireless channel and modes using the GLi interface - however you can change these parameters using the Luci GUI.
Please keep up development !
Thanks for your feedback. Will investigate it.
Hi alzhao, desperate for v3 for mt300a-v2 firmware as I’m completely lost with trying to get Wireguard running on terminal command lines.
Could you please let me know when you are going to release the update?
Thanks
M
Just an update I tried the Shadowsocks Client (using the 750S install instructions) on my MT300A and it works very well with my home Shadowsocks server.
Latency with Shadowsocks is very high 1000mS compared with less than 100ms with Wireguard on the same route. Is this just due to the protocol ?
Looking forward to further updates to V3
Thanks,
Pseudonoise
Hi @kyson-lok I apologise for being stupid to start with.
My setup: 2 x M300N-v2 routers
1 connected to home LAN - router named MiniServer
1 connected by Wi-fi to an android phone with data hotspot - router named Mini Client
Both routers have internet connections.
I set up MiniServer as the server and is attached to lan via cable.
I set up MiniClient as the client that I want to be able to travel with.
I’ve followed the instructions on v3 for the installation of Wireguard and I think I get it however I only get a yellow/orange status button and an Abort button. I don’t seem to be able to make the connection.
Could you please confirm that I’ve got these the right way round - server and home, client to travel? I’ve tried both ways and the same result.
I have not made any other changes,
Interface IP is 10.0.0.2/32
Peer allowed IPs are 0.0.0.0/0
DNS is blank
Could you please tell me what I’m doing wrong? Really frustrating.
Many thanks
Marcus
Just updated to the latest V3 MT300N-V2 testing firmware.
With the MT300N-V2 as a wireguard server i have dns leaks - whatever setting I select in the MT300N-V2 Custom dns server menus .
I have enabled the following -
DNS Rebinding Attack Protection
Override DNS Settings for All Clients Help
DNS over TLS from Cloudflare
and still my mobile network’s DNSs are shown on http://ipx.ac/ and dnsleak when a wireguard tunnel is operating.
Any ideas ?
thanks,
Pseudonoise
Does your miniserver has internet IP and can be accessed in the rest of the world?
Ensure it can be accessed from internet. If it is not main router pls set up port forward in your main router.
Check in the client router if the IP info is correct.
You can also use wireguard app on smartphones to check if server is enabled.
I had the 3.0 beta firmware loaded on MT300N-V2 in order to run VPN. I tried to test WireGuard on this v3.0 too since I failed the DIY process on v2.27 firmware. The 3.0 interface is much better for the CS beginner like me.
I managed to run WireGuard on remote server build on Google Cloud. However, only my PC on LAN connection works but not over WiFi.
Is it supposed to like this, or is it still under development?
Thanks,
What’s up? Cannot connect wifi?
@kyson-lok
Sorry been away for a while.
So I have port forwarded and put the miniserver into DMZ on main router. Can access internet by connecting via Wi-fi to miniserver. Cannot ping local DHCP IP assigned by main router from outside internet. Don’t k ow if this is an issue with main router or something I’ve not set correctly on miniserver.
Is the IP address in Wireguard supposed to be changed or left at 10.0.0.0?
Do I have to change ANY settings in Wireguard other than leaving as default and making sure confit is copied to miniclient?
Thanks!
M
Sorry, port forward just forward your traffic with the specified port, you can’t ping an intranet from the Internet.
Do you mean WireGuard server?
Do you mean Allowed-ips on WireGuard setting?
Just updated gl-mt300a-3.005-1024.bin and a a couple of comments -
1, I’ve configured the switch to toggle Wireguard on and off. Unfortunately it is not very reliable - if I have the switched to ON and I power up the MT300A the Wireguard client fails to start. I have to start the wireguard client from the web interface. Once I’ve have started the client the switch appears to work properly.
2, Very minor but the client/server list ordering in the UI is different for Shadowsocks compared to the other VPNs available.
The Internal SD-card and external USB storage status and file list used to be shown on the Gl-Inet UI but is no longer there. The devices are found via Samba on my connected Linux pc though.
The problem of my mobile network’s DNSs leaking on Wireguard is fixable by defining the desired DNS (1.1.1.1 for me) in the Wireguard configure file for the client on my Android 'phone (see WireGuard on Kali | Kali Linux Blog).
Hope this is of use looking - forward to 3.005 for my companion MT300N V2.
Pseudonoise
Nevermind, I managed to use the free trial version of mullvad vpn using the build-in feature in firmward 3.0. It seemed working very well; even though I am not going to subscribe the service due to the hight rate.
Now I need to figure out how to build a working visual server on google cloud.
‘Again, the toggle does not work always as pseudonoise said above sometimes we need to login the UI to manually connect the WireGuard server.’
