Jetpack AC791L Port Forwarding
jhframe
Enthusiast - Level 1

I have a Jetpack AC791L with a static public IP address that I use to distribute correction data from a GPS receiver.  I had the Jetpack set up to forward a couple of ports to/from a static private IP (192.168.1.x) so that the data could be accessible from the Internet via the public IP address.  I hadn't used the system in some months, and when I tried to use it a few days ago I found that I wasn't able to make the connection.  At this point I don't know which part of the system is not working, but there are indications that it has to do with the Jetpack.

One thing I've noticed is that when I view Connected Devices on the Jetpack screen, it shows the GPS receiver with an IP of 0.0.0.0, even though it's configured for a fixed 192.168.1.x address.  (The DHCP client on the receiver is turned off, because its address needs to stay the same so the devices that need the correction data know where to find it.)  In contrast, when I connect to the Jetpack with a device using DHCP, the Jetpack screen displays the IP address it was assigned by the Jetpack's DHCP server.

My immediate question for AC791L users:  When you configure a device with a fixed IP address and it connects to your Jetpack, does the Jetpack display the actual IP address, or 0.0.0.0?

Thanks!

0 Likes
Reply
4 Replies
Ann154
Community Leader
Community Leader

Which type of IP address do you have? A public or private IP address?

You need a public IP address to access the Jetpack remotely. You have to purchase a public IP address from Verizon Wireless as their default IP addresses are all private and behind the NAT firewall for Jetpacks and their other 4G LTE devices.

I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.

0 Likes
Reply
jhframe
Enthusiast - Level 1

I have a public IP, for which I paid Verizon $500.  But behind the Jetpack firewall I have a static private IP, and I need a couple of ports forwarded out to the Internet.

This was all working fine a few months ago, but now -- with no known changes to any of my equipment -- it's not.  It's quite frustrating.

0 Likes
Reply
7e18n1
Specialist - Level 3

Twice, you specified 192.168.1.x.  What is the value you are using for X?

0 Likes
Reply
jhframe
Enthusiast - Level 1

I've used various values in the troubleshooting process, typically 11 or 21.  Sometimes values in the DHCP range, sometimes outside of it.

However, the problem was solved when someone noticed a misconfigured port number in a piece of equipment on the client side.  The config had gotten bollixed up by a software update, which changed settings that I hadn't ever messed with.  The problem didn't reside in the Jetpack after all.

Incidentally, I now know that the AC791L displays 0.0.0.0 in place of an internal static IP address when displaying Connected Devices on the front panel.  Why the manufacturer chose to do this is beyond me, but it did lead me down a long and tedious troubleshooting path I could have been spared had it shown the actual IP.

Thanks to all who responded!

0 Likes
Reply