You can try openwrt mirror site:
China site:
sed -i 's_downloads.openwrt.org_mirrors.aliyun.com/openwrt_' /etc/opkg/distfeeds.conf
sed -i 's_downloads.openwrt.org_mirrors.cloud.tencent.com/openwrt_' /etc/opkg/distfeeds.conf
Austria site:
sed -i 's_downloads.openwrt.org_mirror.kumi.systems/openwrt_' /etc/opkg/distfeeds.conf
thanks it works now via the switch indeed 
Yes. Same issue. Thanks
Dns is rightly displaied. To work dns resolution I have to stop and start vpn policies…After a router restart or if I switch between vpn profiles…
Can you describe in detail? I haven’t reproduced here.
Vpn policies active. Exception (no vpn) for domain list.
Every time I start vpn or I change between vpn profile I have to stop and restart vpn policies to have correct resolution of names.
when I reset the router to current settings, and I fill in my mullvad credentials and after this configure something like nextdns.
then when I enable vpn, it doesn’t work and a restart is needed.
now im not sure if the order is correct, it could also be that I first started the vpn and then applied the nextdns.
I think this is what antifascista tries to say.
I seem to have the same issues with changing from repeater to wan sometimes this can also start happening but I think this is a different issue.
Could you try replicating it?
-edit-
I also have domain policies active.
Yes. This is the issue…
Having a prblem with VLANs on GL-A1300 beta 4.
When a 2nd VLAN is added to Switch (eth0), we stop recieving packets on eth1.
Out of the box we have eth1 (WAN) and eth0 LAN.
VLANs are disabled on eth0.
If I enable VLAN on eth0, 1st VLAN is fine, but when I add a 2nd VLAN, I stop recieving packets on eth1. If I remove the VLAN, I recieve the frame from the other end.
My setup:
WAN is via WWAN.
Network->Switch VLAN enabled, VLAN 16 tagged to CPU, untagged to ports.
Interface LAN 10.101.16.1/24 uses br-lan includes only eth0.16,
Interface LAN31 10.101.31.1/24 uses eth1 device.
Cisco router added on 10.101.31.2 to eth1. OSPF enabled betwee GL-A1300 and CISCO router.
All works great.
If I add VLAN 17 to the Network->Switch config, Stop recieving packets on eth1.
Zip contains
network for VLAN 17 defined (eth1 stops working).
network for no VLAN 17 (just VLAN 16), all working
Session form CISCO on 10.101.31.2 connected to eth1. Cannot ping when VLAN 17 added, but can ping when VLAN 17 is not there.
Any thoughts?
Simon
vlan problem.zip (1.9 KB)
Hi Hansome,
This did not make a difference.
I still could not ping on eth1 with VLAN 17 created. Once I deleted it, I could ping again.
Simon
Hi Hansome,
Further problems.
After removing VLAN17, I set a port forward off to another subnet via the router connected to eth1 (learnt through routing protocol). The forward was for a game, and points to the IP of my laptop on the sethernet subnet. and I have this forward, and an equivalent to the GL-A1300 LAN network (laptop connects here wirelessly).
The game works with the Wifi forward set, and the laptop on wifi, it does not connect using the wired forward, and the laptop on a subnet vrouted via eth1.
I have replaced the GL-A1300 with my GL-AXT1800, in which everything works well.
I will redeply the GL-A1300 on a test LAN, as ther are things that need to be investigated - but this needs to done “in the lab” so to say.
I’ll flatten the GL-A1300 and set it up in a lab vlan and try to recreate.
Have to say though, in the basic Repeater Mode to another Wifi SSID bridged with 3 ports of ethernet and no VLANs, the GL-A1300 seems to work pretty well for its price.
Simon
Here we go the Slate Plus new firmware v.4.0.0 release 1:
Download here: https://github.com/gl-inet/gl-infra-builder/releases/download/v4.0.0_a1300_release1/a1300.tar.gz
Could you share GL-AXT1800 network config, then I can mak it more clear how vlan traffic flows.
I moved the A1300 into a test network today. I took the opportunity to upgrade to the latest beta, and cleared the config.
Afterwards, I was able to place eth1 in a seperate interface, and have 2 x VLAN on the switch config. So I could not recreate the problem.
Simon
Hello,
I did see one problem in my testing yesterday. This is when changing LAN IP address via GL interface after setting the VLAN in switch to tagged on the CPU. In this scenario, you need to get the switch to reconfigure itself (changign the tagging on one port/vlan, then change it back.
This problem does not occur if you use luci to change the LAN IP. Given someone has already changed the switch VLAN/CPU from untagged to tagged, not sure why someone would use the GL interface to change after using LUCI for LAN config. So I do not consider this a big problem, although you can lock yourself out your router if you do not have Wifi or other way in. I suspect a reboot will also solve the problem.
Changing the IP address of the LAN via luci works fine, I just needed to disable and re-enable the PCs ethernet port to get it to refresh its IP address.
With the GL UI.
Before changing the IP address. DHCP broadcast request recieved on eth0.16.
After changing the IP address, broadcast on VLAN 16 are recieved on eth0 (untagged) by the CPU, nor eth0.16 (tagged), which is the member of br-lan.
Before and after the change, the bridged wifi interface works correctly.
Note: In default setup the problem never occurs as VLAN 1 is untagged on the CPU port in switch, so works the same before and after.
Attached the testing.
logreads.log is the logread output covering changing the ip address via both luci and then via gl ui.
2 Using luci
Changing LAN ip address from 10.101.18.1 between 10.101.20.1.
ipconfig on PC after flapping the ethernet connection.
3 Using GL iUI
3a) Change IP Address and flap the PC ethernet port. The PC shows it is connected to unidentifed interface.
Login via Wifi to regain access to UI.
Change LAN IP.zip (832.3 KB)
Step 3b Restart the LAN interface. Stll unidentified network.
ipconfig at this point supplied as step 3a. You can see in logread output attempts to get DHCP via eth0
Step c) Toggle an unused VLAN/Port to off, save and then back again. After this flap the PC interface link.
The PC now picks up an IP address via DHCP on the Ethernet.
So there is something different about GL UI LAN IP change compared to luci, which is bad when tagged VLAN are used.
Simon
[Change LAN IP.zip|attachment]
When creating the LAN IP Address Error this morning, I then discovered my eth1 had stopped working properly… again.
Reconfigured the switch from scratch again.
LAN IP 10.101.18.0/24
WAN is WWAN on 10.101.2.151
Eth1 is via CISCO30 IP address 10.101.30.1 (CISCO is at 10.101.30.2).
Starting point.
1 x vlan (16) set to cpu u, port 1 u port 2 u
Change this to cpu t port 1 u port 2 u
All works well, I can ping the CISCO at 10.101.30.2
Add VLAN 17 set cpu t port 1 u port 2 u
I can no longer ping the CISCO at 10.101.30.2
Remove the 2nd VLAN and I can ping the CISCO again.
Attached:
I have included network files for both configs.
I have included logread of changes being applied.
screenshots of switch changes.
Either I am not very good, or that switch driver is not very good 
Simon
220908 vlan err.zip (665.4 KB)
Hi Simon,
I succeed to reproduce the issue that ping eth1 interface fail when add second vlan at eth0 switch0.
and solved by add network config part:
config switch_vlan
option device 'switch0'
option vlan '31'
option vid '2'
option ports '0t 5'
Note that eth1 mapped vid must be 2, this should be switch driver quirk.
Full config attached.
network.zip (647 Bytes)
Thank you.
Today I’ve see the Slate Plus is on available on the gl-inet.com Website. Does this mean we are allowed to write public reviews? (Don’t worry, it will be a positive one 
)