I used the smartphone app to configure strongvpn wireguard.
I used mac based policy and add my pc to use vpn or do not use vpn.
All works as expected and dns can be resolved.
What could be the possible reason?
I use vpn policies ip/domain and no dns resolution if dns servers are on vpn network, all is ok if I set an e ternai dns server.
On Slate ax and Slate plus, old or new kernel…
I take some time to study this issue and it does seems a bug.
Submitted internally.
2 Likes
Another issue on slate ax is that on router restart no dns resolution if vpn policies are active. I have to stop and start vpn policies to solve issue. Issue is present on old and new kernel. Slate plus is not affected.
My domain/ip list is very long…
Thanks
1 Like
Maybe the same problem. Will fix both.
1 Like
if ones uses adguard then he/she can/should define a custom dns server for a client using vpn as explained in the following post:
https://forum.gl-inet.com/t/slate-axt1800-openvpn-adguard-home/23173
Yes. Can you try the snapshot? It should have fixed that.
Great! I just tested it, and it’s working!
It’s working now!
Thanks
Another issue is blue led not working.
On kernel 5.4 blue led is working and showing wan activity.
LED status:
- Blue: System booting
- Blue flashing: No Internet
- White: Normal Internet
Hi alzhao,
I refer to small blue led in the left. On kernel 5.4 it’s blinking by wan activity…
It should not. Otherwise it is not configured well.
Strange for me too but in kernel 5.4 firmware small blue led blinks by wan activity like luci configuration.
A little offtopic, but I’m too tired to create a new post, right now.
I’ve tried Kernel 5.4 the first time, today. And my Slate AX is happily blinking with the beat of my WAN traffic … I can’t say if it is blue or white, but is is blinking.
I do agree: I think it is configured in the image. I haven’t kept my settings while downgrading from 4.0.2 (I don’t think it is a downgrade, but the ‘Update dialog’ says so).
1 Like
same problem noticed on slate ax running latests 4.0.2 release
Do you have more details? Because the other guys said it is fixed.
It’s working however it does not seem stable over time: for unexplained reasons (happened again last evening) VPN traffic will no more go through without clear reasons and device will become unstable / unresponsive. It does not happen with Brume with the very same config in terms of vpn config, policies.
Only way to solve it is to reboot (unplug) the router as GUI or Luci access is no more possible either. My internet line (500 Mbps fibre) & ISP is of good quality and not causing the VPN to stall.
I have even put a script in etc/config directory call from the crontab (lucid “scheduled tasks”) to test the VPN traffic availability and if I cannot ping google through the vpn interface (“wgclient” on slate ax), I will retry again and then trigger a reboot.
script:
if [ “$(ping -I wgclient -q -c 3 -W 1 8.8.8.8 | grep ‘100% packet loss’ )” != “” ]; then
logger -t WIREGUARD_Reconnect WIREGUARD Tunnel has got NO internet connection, RETRYING IN 60S
sleep 60
if [ “$(ping -I wgclient -q -c 3 -W 1 8.8.8.8 | grep ‘100% packet loss’ )” != “” ]; then
logger -t WIREGUARD_Reconnect WIREGUARD Tunnel has got NO internet connection, REBOOTING IN 20S
sleep 20
reboot
else
logger -t WIREGUARD_KeepAlive WIREGUARD Tunnel is alive, Google ping OK
fi
else
logger -t WIREGUARD_KeepAlive WIREGUARD Tunnel is alive, Google ping OK
fi