Mini IP Interface
Mini IP Interface
The Mini supports IP via the Iridium Certus 9770 module (WAN) allowing LAN device IP data to be be forwarded via the WAN interface.
The default LAN configuration on the Mini is 192.168.250.0/24
with the Mini having the static IPv4 of 192.168.250.1
. The Mini does have a DHCP server on the LAN but disabled by default, therefore all LAN devices need to be configured with a static IPv4 of 192.168.250.2
to 192.168.250.99
and netmask of 255.255.255.0
the gateway should be configured to 192.168.250.1
Confirm the IP connection with ICMP Pings
- Connect the Certus antenna to the Mini.
- Power up the Mini.
- Configure a LAN device IPv4 configuration to the settings below. Preferable the LAN device should be a test PC so it has access to IP utilities like
ping
.- IPv4 Address:
192.168.250.2
to192.168.250.99
- IPv4 Netmask:
255.255.255.0
- IPv4 Gateway:
192.168.250.1
- IPv4 Address:
- If possible isolate traffic on the LAN device to prevent unwanted IP forwarding.
- To confirm there is a LAN connection, ping Mini address from the LAN device, all pings should get a response. If this does not happen follow the steps above again, verifying the IPv4 configuration. An example command response is below.
root@test:~ $ ping 192.168.250.1
PING 192.168.250.1 (192.168.250.1) 56(84) bytes of data.
64 bytes from 192.168.250.1: icmp_seq=1 ttl=64 time=0.593 ms
64 bytes from 192.168.250.1: icmp_seq=2 ttl=64 time=0.526 ms
64 bytes from 192.168.250.1: icmp_seq=3 ttl=64 time=0.521 ms
64 bytes from 192.168.250.1: icmp_seq=4 ttl=64 time=0.514 ms
--- 192.168.250.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3050ms
rtt min/avg/max/mdev = 0.514/0.538/0.593/0.031 ms
- To confirm the Mini's WAN connection you could open an internet browser and connect to http://192.168.250.1. The Mini Home page should load indicating its current state. To confirm the LAN is up by checking the
PPP Status
. This should reportUP
if connected. IfDOWN
is reported confirm a antenna is connected and Mini is provisioned, if this is the case theSignal Quality
will not be0,0
andProvisioning
will reportMessaging,Packet Data
- If
PPP Status
is reported asUP
, the Mini is ready for ICMP pings over the internet. Run a ping to a known server which has a static IPv4. Usually a ping to8.8.8.8
(dns.google.com) is ideal. You may observe a few losses to begin-with as it takes some time Iridium Certus to ramp up the radios for IP transmission, once the pings start getting responses the ping response time will decrease down to about 400 - 600 ms. An example of of this is below.
root@test:~ $ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=112 time=8630 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=112 time=7699 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=112 time=6855 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=112 time=5921 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=112 time=4987 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=112 time=4053 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=112 time=3119 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=112 time=2185 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=112 time=1251 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=112 time=612 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=112 time=601 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=112 time=591 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=112 time=491 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=112 time=480 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=112 time=559 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=112 time=459 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=112 time=448 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=112 time=437 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=112 time=606 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=112 time=595 ms
--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19194ms
rtt min/avg/max/mdev = 437.244/2529.122/8630.026/2724.318 ms, pipe 9
Testing TCP and UDP Connections with Netcat
Prerequisites
- Perform the ICMP ping test as explained above to verify the Iridium Certus connection is up.
- Ensure netcat (or nc) is installed on both the client (test PC) and the server.
- For Linux/Mac, install via package manager if not already installed.
- Ubuntu/Debian: sudo apt-get install netcat
- CentOS/RHEL: sudo yum install nc
- Mac: brew install netcat
- For Windows, download netcat nmap and add it to the system PATH.
- For Linux/Mac, install via package manager if not already installed.
Testing TCP Connection
On the Server
- Open a terminal on the server.
- Start a netcat listener on the desired port (e.g., port 12345):
nc -vl -p 12345
On the Client (Test PC)
- Open a terminal or command prompt.
- Connect to the server’s IP address on the specified port:
nc -v <server-ip> 12345
- Type a message and press Enter. If the connection is successful, you should see the message appear on the server’s terminal.
Testing UDP Connection
On the Server
- Open a terminal on the server.
- Start a netcat listener on the desired port (e.g., port 12345):
nc -vul -p 12345
On the Client (Test PC)
- Open a terminal or command prompt.
- Connect to the server’s IP address on the specified port:
nc -vu <server-ip> 12345
- Type a message and press Enter. If the connection is successful, you should see the message appear on the server’s terminal.
Troubleshooting
- Ensure
Provisioning
isMessaging, Packet Data
. - Ensure
PPP Status
isUP
. - Ensure the server’s firewall is configured to allow traffic on the specified port.
- Verify the server’s IP address and port number.
- Ensure there are no network issues by performing the ICMP ping test first.
SMTP
This functionality is only supported from Firmware V0.12
The RR-Mini supports an SMTP server designed specifically for sending attachments.
While the SMTP server is accessible over LAN, it uses IMT to transmit the attachments to Cloudloop Data. From there, the files can be forwarded to your specified email destination without incurring additional charges.
The server handles the attached file by compressing it and transmitting it via one or more IMT messages, depending on its size. Once received by Cloudloop Data, the file is automatically decompressed and delivered as intended.
Prerequisites
- The SMTP Server must be enabled in the User configuration
- The device connecting to the RockREMOTE Mini must be connected via Ethernet and on a Private IPv4 within the Mini's range (By default
192.168.250.0/24
) - An Email Destination within Cloudloop Data must be set up with an attached group where the RockREMOTE Mini utilising SMTP is a part of
Payload
,Plaintext
andAssume Destination from Source
must be chosen for SMTP
Supported SMTP Options
- AUTH:
NONE
- Port:
25
- Max Attachment Size:
165KB
- Recipients: One
To
field and twoCC
fields - Compression: All files are compressed before sending and decompressed in Cloudloop Data
RRMini: 220 RockREMOTE Mini Server Ready
Client: ehlo localhost
RRMini: 250-Hello
RRMini: 250 AUTH PLAIN
Client: Mail FROM: FROM@example.com
RRMini: 250 OK
Client: Rcpt TO: TO@example.com
RRMini: 250 OK
Client: Rcpt TO: CC1@example.com
RRMini: 250 OK
Client: Rcpt TO: CC2@example.com
RRMini: 250 OK
Client: DATA
RRMini: 354 Start mail input; end with CRLF.CRLF
Client: 'Content-Type: multipart/mixed; boundary="===============7430458958744601375=="\r\nMIME-Version: 1.0\r\nFrom: FROM@example.com\r\nTo: TO@example.com\r\nCc: CC1@example.com, CC2@example.com\r\nSubject: Example Subject\r\n\r\n--===============7430458958744601375==\r\nContent-Type: image/webp\r\nMIME-Version: 1.0\r\nContent-Transfer-Encoding: base64\r\nContent-Disposition: attachment; filename="image.webp"\r\n\r\nAAAAAAAAAAAAAA==\r\n\r\n--===============7430458958744601375==--\r\n.\r\n'
RRMini: 250 OK
Client: QUIT
RRMini: 221 OK
Currently the SMTP Server does not support any authentication AUTH
method.
Support for AUTH PLAIN
is currently under development.
Testing SMTP
It's possible to test SMTP before use on Linux
Swiss Army Knife SMTP is a command-line tool that can be used to test and debug SMTP servers.
- Install with
sudo apt install swaks
- If not using DHCP - Static the IP of the network interface the RR-Mini is connected to, eg if connected to
eth0
usesudo ifconfig eth0 192.168.250.10
- Use an existing attachment or create a dummy attachment with
truncate -s 10000 10KB.txt
where 10000 is the size in bytes and 10KB.txt is the name of the file - Adjust and run the following command:
swaks --to to@example.com --to cc1@example.com --to cc2@example.com --from from@example.com --server 192.168.250.1 --header "Subject: Test Text File" --attach @10KB.txt
LAN
The RockREMOTE Mini can have a number of Local Devices connected to its Local Area Network (LAN). For example:
- A single device plugged into the wired ethernet port
- Multiple devices plugged into a network switch, which is plugged into the wired ethernet port
Be careful not to choose a subnet that overlaps with the WAN interfaces. Some subnets will be rejected because they are used internally. For example the Iridium WAN interfaces uses 192.168.2.0/24
internally, which means the LAN IP range of 192.168.2.0/24
can not bet used.
As supplied the user.cfg rules enable all outbound and ICMP traffic.
Further details and instructions for configuration of the RockREMOTE Mini's IP address and DHCP server (etc) can be found here: User configuration