What's new

Verizon 4G LTE Network extender

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ZemTyrion

New Around Here
I'm sorry, I'm assuredly posting in the wrong place. Unfortunately, searching "network extender" returns all sorts of wireless network extender.

I have been running ASUSWRT-MERLIN for quite a while without any issues. However, Verizon is sucking lately in my area, and they sent me a network extender to make up for it. It works for outgoing calls and maybe 10% of incoming calls. 90% of incoming calls just go straight to voicemail while on the extender.

I have reset everything there is to set on my phone, and Verizon has been basically useless. Finally they said it may be a router issue. First thing says to put the router into the DMZ. I found where to do that, but everything I've seen basically says that only a moron would enable DMZ on a home router.

Then it says to unblock ports/IP addresses. Here is the content, and I'm not sure what to do with this information. I'd appreciate any help (from "If ANY calls get through then it's not the router" to "Use DMZ, you'll be fine" to "Piss off", though the last one seems a little mean).

  • The following ports and IP addresses must be unblocked for the Network Extender to work properly.
  • It is necessary to enable Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) (incoming and outgoing) for specific ports and/or unblock specific IP addresses on the modem/router.
  • Refer to the Internet Service Provider (ISP), Network Admin, or equipment manufacturer for assistance with these settings. Examples of router setup are provided here; however, Verizon Wireless doesn't support 3rd-party routers.

4G LTE Network Extender
Ports:

  • TCP
    • 53
    • 80
    • 443
  • UDP
    • 53
    • 67
    • 68
    • 80
    • 123
    • 443
    • 500
    • 4500
    • 52428
    • 20906
IP Addresses:

  • Security Gateway IP addresses (sg.vzwfemto.com)
    • 141.207.245.235
    • 141.207.143.235
    • 141.207.129.235
    • 141.207.243.235
    • 141.207.137.235
    • 141.207.249.235
    • 141.207.209.235
    • 141.207.231.235
    • 141.207.225.235
    • 141.207.213.235
    • 141.207.233.235
    • 141.207.197.235
    • 141.207.200.235
    • 141.207.193.235
    • 141.207.145.235
    • 141.207.155.235
    • 141.207.151.235
    • 141.207.177.235
    • 141.207.165.235
    • 141.207.173.235
    • 141.207.181.235
    • 141.207.161.235
  • The following eight Security Gateway IP addresses are retired as of 8/31/2018:
    • 69.78.34.151
    • 69.78.34.154
    • 69.78.82.87
    • 69.78.82.90
    • 69.78.145.119
    • 69.78.145.122
    • 69.78.226.55
    • 69.78.226.58
  • Global Positioning Satellite Server
    • 209.210.15.73 GPS server (gps.vzwfemto.com)
    • 216.221.129.99 GPS server (gps.vzwfemto.com)
  • Private DNS
    • 108.61.73.243 GPS server (0.north-america.pool.ntp.org)
    • 192.95.20.208 GPS server (1.north-america.pool.ntp.org)
 
All outgoing ports on the router are open by default so that shouldn't be a problem. If you suspect there might be a problem with incoming ports you could try putting the extender in the router's DMZ for a period of time and see if things improve. I suspect not.

Is the router running with non-standard settings or third-party software that might interfere with internet access, e.g. ad-blockers or firewalls? If so try disabling them.

Femtocells usually require an accurate time source (i.e. NTP). Merlin's 384.11 introduced an option to redirect NTP requests to its own internal NTP server. Try experimenting with that setting.
 
There's nothing on it except for the firmware. I tried the NTP settings and it didn't make a difference. For a few minutes I disabled the firewall, and within the limited testing I can do, it seemed good. I guess the next step is the DMZ.
 
Further testing shows that disabling the firewall was a fluke. It doesn't do anything, and neither does directing the DMZ to the IP of the extender. I might be on AT&T soon.
 
It doesn't do anything, and neither does directing the DMZ to the IP of the extender.
I expected that to be the case but it was worth trying just in case. As you speculated yourself, if this was a configuration issue you'd expect it to work all the time or not at all.

Make sure that L2TP and IPSec Passthrough are enabled at WAN > NAT Passthrough.

EDIT: What is your router connected to? A cable modem? Is it in "bridge mode", i.e. does your router have a public IP address?
 
Last edited:

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top