GL-BE9300 (Flint 3) domain issue

[dusky]

When connected to Ethernet, my server’s domain becomes inaccessible(only locally accesible), but it works when connected to Wi-Fi.

GL-AX1800 (Flint) NAT hairpin/loopback troubles

I am seeing some strange behavior with respect to NAT loopback and wired vs wireless clients. It appears that the default behavior is that NAT loopback is enabled on port forwarding rules. I verified this by checking the advanced settings (LuCI) interface. Wireless clients seem to be able to reach an internal reverse proxy pointed to by a dns name that resolves to my WAN IP. (To me this indicates that NAT loopback is working to some degree.) Wired clients do not have the same success. I have…

/etc/init.d/qca-nss-ecm stop into ssh is a workaround.

[bruce]

Hello,

I would like to clarify these:

1. Is the server installed on the LAN? And create rule of port forwarding and enable DDNS?

2. In a WAN (Internet), can not access this server through the DDNS domain?

3. Can WiFi client access the server through a domain? Can LAN wired client access the server through a domain?

[dusky]

Hi,

1. The server is connected to the LAN. Port forwarding is set up, and a DDNS provided by my ISP is configured.

2. I can access the server using the DDNS domain on my phone over mobile data.

3. 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.

[bruce]

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:

1. if /etc/init.d/qca-nss-ecm start, in laptop (Win CMD or Unix Terminal):
   nslookup [your domain]
2. if /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.