Support came up empty, telling me ZTE is a terrible to sonic as they are to me,
and has not provided them with manuals. This seems a bit strange to me, since
the ZTE came pre-configured with several functions pointing to sonic.net domains.
In any event:
I run a number of services in the home, such as home automation and data
access. This requires either port forwarding
or a virtual server. I could find no port forwarding on the ZTE,
so I set up a virtual server. Unfortunately, the router seems not
to support hairpin routing.
ie, if the inside address of a security camera [for example] is, let's say,
192.168.0.66, and i've set up a virtual server to port
[let's say] 1234. Then from the outside [internet],
blahblah.dyndns.org:1234 is correctly forwarded.
From the inside, 192.168.0.66:1234 also works fine [i'd hope so].
But from the inside, blahblah.dyndns.org:1234 does not work.
Resolving this to the external IP and doing [for example]
50.0.74.166:1234 also works from outside but not inside,
so this is not related to dyndns
This is, basically, a "hairpin routing" problem. I
have had previous routers where "virtual server" configurations
fail to hairpin route but "port forwarding" succeeds. I
don't know if this router is similar, but while some of the
manuals on the internets show a port forward page for this device,
i don't see one; the GUI looks quite a bit different from what i've
seen on the manuals circulating on the intertubes.
So the question: is there any way to get hairpin routing to work?
Port forwarding, NAT, routing tables, firmware update --- anything?
Or a manual so i can figure it out myself?
Modem reports:
Firmware Version: W300V3.1.0a_DR0_OV
and has not provided them with manuals. This seems a bit strange to me, since
the ZTE came pre-configured with several functions pointing to sonic.net domains.
In any event:
I run a number of services in the home, such as home automation and data
access. This requires either port forwarding
or a virtual server. I could find no port forwarding on the ZTE,
so I set up a virtual server. Unfortunately, the router seems not
to support hairpin routing.
ie, if the inside address of a security camera [for example] is, let's say,
192.168.0.66, and i've set up a virtual server to port
[let's say] 1234. Then from the outside [internet],
blahblah.dyndns.org:1234 is correctly forwarded.
From the inside, 192.168.0.66:1234 also works fine [i'd hope so].
But from the inside, blahblah.dyndns.org:1234 does not work.
Resolving this to the external IP and doing [for example]
50.0.74.166:1234 also works from outside but not inside,
so this is not related to dyndns
This is, basically, a "hairpin routing" problem. I
have had previous routers where "virtual server" configurations
fail to hairpin route but "port forwarding" succeeds. I
don't know if this router is similar, but while some of the
manuals on the internets show a port forward page for this device,
i don't see one; the GUI looks quite a bit different from what i've
seen on the manuals circulating on the intertubes.
So the question: is there any way to get hairpin routing to work?
Port forwarding, NAT, routing tables, firmware update --- anything?
Or a manual so i can figure it out myself?
Modem reports:
Firmware Version: W300V3.1.0a_DR0_OV
