Jump to content

MiFi 500 LTE gets public IP but appears to be firewalled


Recommended Posts

I have mine through FreedomPop but I think Sprint is the one blocking it.  Since I don't have fixed internet at home I was planning to use my device to keep tabs on various things.  I port mapped my wireless camera through the built in firewall and still cannot access it from the public IP Sprint assigns.

 

After getting a Franklin U600 for free last month I tried the same thing out on the WiMax network, and it isn't blocked, camera works great. Has anyone got the LTE network firewall lifted and how do you do it?

Link to comment
Share on other sites

  • 1 month later...

I tested with FPs other devices they sent, a Franklin U600 WiMAX/EVDO modem.  It works just fine, both 3G and 4G network IPs are public and routable!

 

I'm thinking it might be the MiFi 500's router blocking things, going to acquire a Netgear LTE modem and move the SIM to see if I'm correct.

Link to comment
Share on other sites

I doubt it is just the mifi router blocking them, unless you have a static ip or some type of business account, its very likely that sprint is blocking/filter incoming connections across lte to prevent lte from being used as a server connection.

 

wimax network is older and different and doesn't necessarily have the same filtering/network managemen rules.

 

edit;

 

I can ping my wimax hotspot public ip, but can not ping my netgear zing lte hotspot public ip.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...