When connected to Ethernet, my server’s domain becomes inaccessible(only locally accesible), but it works when connected to Wi-Fi.
/etc/init.d/qca-nss-ecm stop
into ssh is a workaround.
When connected to Ethernet, my server’s domain becomes inaccessible(only locally accesible), but it works when connected to Wi-Fi.
/etc/init.d/qca-nss-ecm stop
into ssh is a workaround.
Hello,
I would like to clarify these:
Is the server installed on the LAN? And create rule of port forwarding and enable DDNS?
In a WAN (Internet), can not access this server through the DDNS domain?
Can WiFi client access the server through a domain? Can LAN wired client access the server through a domain?
Hi,
The server is connected to the LAN. Port forwarding is set up, and a DDNS provided by my ISP is configured.
I can access the server using the DDNS domain on my phone over mobile data.
When my laptop is connected via WiFi, I can access the domain. However, when using a wired LAN connection, I’m unable to access the server through the domain.
Hi,
Thanks for the reply.
Regarding the 3, if /etc/init.d/qca-nss-ecm stop
, the laptop which using a wired LAN connection, will be able to access the server through the domain?
Please assist us to do a compare test, laptop using a wired LAN connection:
/etc/init.d/qca-nss-ecm start
, in laptop (Win CMD or Unix Terminal):nslookup [your domain]
/etc/init.d/qca-nss-ecm stop
, in laptop (Win CMD or Unix Terminal):nslookup [your domain]
I would like to know what the difference is of this domain resolution.
I chose, in my case, Option A below which works for me (I have >1GBs WAN throughput)
Hardware GL-BE9300 (Flint 3)
Firmware 4.5.15 r22468-2004ee9 (Jun 2025)
Setup
https://<public-IP>
or the DDNS host-name hangs at TLS.With NSS disabled, WAN-LAN routing drops to ≈ 800–950 Mb/s on current firmware according to several user iperf tests; enabling NSS restores full multi-gig throughput.
# one line per domain → LAN-IP
uci add_list dhcp.@dnsmasq[0].address='/example1.ddns.net/192.168.0.56'
uci add_list dhcp.@dnsmasq[0].address='/example2.ddns.net/192.168.0.56'
uci add_list dhcp.@dnsmasq[0].address='/example3.ddns.net/192.168.0.56'
uci commit dhcp
/etc/init.d/dnsmasq restart
ipconfig /flushdns
→ nslookup example1.ddns.net
If it doesn’t work:
nslookup
shows the LAN IP./etc/init.d/dnsmasq restart
once more./etc/init.d/qca-nss-ecm stop
Reflection works immediately, but WAN throughput 'possibly' caps at ~0.9 Gb s