LR77 v2
•
In a private APN it is not recommended to get the DNS settings from operator (on
"Mobile WAN" page)
•
Go to "System Log" page in "Status" section and observe where the error occurs.
-
I cannot connect from the Internet to the device behind the router. I have NAT
enabled.
•
The device’s gateway has to be configured so it points to the router.
-
I can’t access my Web server placed behind the router over NAT.
•
The remote HTTP access to the router has to be disabled on "NAT Configuration"
page in the router. Also enable "Send all remaining incoming packets to default
server" feature and fill in the IP address of your Web server. On the Web server,
the default gateway has to be the IP address of the router.
-
DynDNS doesn’t work.
•
With private APN this will not work.
•
If the same IP address is recorded in your canonic name as a dynamically assigned
address, it means that the operator is using NAT or a firewall.
•
You can verify NAT using ping to your server with static address and then compare
with router’s IP address.
•
You can verify a Firewall by accessing remotely to the router’s Web interface.
•
The operator may not provide the address of DNS server and without DNS server’s
address it is impossible to connect to the dyndns.org server. The following mes-
sages will be shown in the System Log:
–
DynDNS daemon started
–
Error resolving hostname: no such file or directory
–
Connect to DynDNS server failed
-
L2TP or IPSec isn’t establishing.
•
Check the "System Log" page for error messages.
-
IPSec tunnel establishes but the communication does not run.
•
Probably there are bad routing rules defined in the connected devices, or the default
gateway.
-
I switched the router to offline mode by SMS message, but the router is in online
mode after reboot.
•
SMS messages do not change the router configuration. They remain in effect only
until the router is rebooted.
38
04-09-19
LUCOM GmbH — Flößaustr. 22a — 90763 Fürth — Tel.: +49 911/ 957 606 00 — E-Mail: [email protected] — www.lucom.de
www
.lucom.de
