Ping can resolve the IP address of the modem but it does not get a reply. As such I am not able to access my data logger using the modem. See ping result below.
Also, from the modem webpage on Admin/Advanced/Ping I am able to ping a Host such as google.com and get a reply. I have no clue why I cannot access the modem remotely. I have good signal strength -79 and sometimes better -69.
Remote access via ping:
C:\Users\dossantoss>ping JP52940200001010.eairlink.com
Pinging JP52940200001010.eairlink.com [181.178.226.59] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 181.178.226.59:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Google.com ping from the modem webpage
The IP address returning shows that the modem was able to establish an outgoing connection to the eairlink server.
Possibly, the pings to the modem are being blocked by a firewall.
I have tried it from a network connection where I am able turn off the firewall but I still get the same "Request time out" message.
Any other ideas?
Thanks,
Sergio
The firewall could be on the cellular network. Any layer of a network could have a firewall.
I am having very similar problems.
I have both Sierra RavenXT (2) and MicroHard IPn3Gb (3) cellular modems with the same inability to communicate with any of them. Very frustrating.
I am using Rogers (Canada).
All of the modems will indicate they are connected to the cellular network and are given an IP address (Typically 25.xxx.xxx.xxx). However I cannot connect via loggernet or anything else via that IP address.
I get the same results with PING atempts as Sergio posted. Additionally none of the modems ever update themselves at their respective DDNS hosts (eairlink.com for the RavenXTs and freedns.afraid.org for the IPn3Gbs).
The IPn3Gb modem have an ethernet port and if I connect a computer directly to the modem I can surf the internet on the computer and it assigns that computer an IP address (24.xxx.xxx.xxx) so the sim and modem seem to be functioning somewhat but just cannot be connected to remotely via an IP address.
I have disabled the firewall completely on the IPn3Gb and tried connecting from work (heavily firewalled) and home networks (full access) to rule out those.
JDavis mentioned the possibility of another layer of firewall at the cellular provider level. Considering what I have outlined does it sound like that is the most likely source of the problem?
What you are seeing is not atypical of many European networks where dynamic IP addresses are behind a NAT firewall and are usually from a private IP range.
I quickly scanned the internet and can see reports that Rogers are now doing the same for some of their cheaper data contracts and in some cases are allocating recycled IP addresses which are not from a private range but, luckily, are behind a NAT firewall. One sign of this is to go to a site like WhatsmyIP and check what IP it reports and check if it matches what the modem reports.
Reading some of the forums it seems you now need to pay extra to guarantee a public IP address or at least make sure it is guaranteed on the airtime contract.
A solution in case you are unable to get a public IP address without firewall issues for the modem is to make to modem initiate an outgoing connection. Provided you can get a public IP address for Loggernet, Loggernet may be configured to listen for incoming connections.
Customers have found success with some particular cellular providers by using a modem for the same network for the PC that is running Loggernet. Some cellular networks don't have NAT issues for mobile to mobile communications, but you would have to verify this with your cellular provider.
It is also possible to have the datalogger and Loggernet both connect to another Pakbus device that has a public address, and route through it. Both Campbell Scientific Canada and Konect GDS offer Pakbus routing services.
Persistent, outgoing connections from a datalogger can easily be configured using the Pakbus TCP Client settings.
Thanks for the tips. Making the datalogger initiate the transfer of data via emailsend seems to work great (using gmx.com as mailserver).
I first tried outlook.com and had no success as they required additional security response checks as they deemed a login from an 'unknown device' was suspicious. Since the CR1000 couldn't respond to these requests the account was frozen rather quick.