Cradlepoint E300EU APN Settings
This guide outlines how to setup a Cradlepoint E300EU for OmniSIM
Cradlepoint E300EU
Advice
To get OmniSIM working optimally with Cradlepoint routers, we have compiled the following guide, as there are some challenges in how SIMs are configured in the device. The following tasks should be undertaken:
Ensuring that the correct APN is manually pre-configured in the connection manager prior to use. This is a basic task, but it prevents the device from being considered truly “plug and play”.
When using the device in Dual-SIM Configuration (2 SIMs at once), IMSI switching for OmniSIM Reach may take longer than 90 seconds, which is not fast enough to cater for the reboot timer.
Therefore use of OmniSIM Reach in this Dual-SIM configuration is not recommended.
Super SIM and OmniSIM Rush however do successfully switch in time, so we may recommend these products for Dual-SIM use.
Connecting to router
Connect your PC to Ethernet port of the router
By default router will assign you the IP address in 192.168.0.0/24
$ ipconfig
Windows IP Configuration
Ethernet adapter Ethernet 3:
Connection-specific DNS Suffix . : local.tld
Link-local IPv6 Address . . . . . : fe80::edd7:bfa0:4515:fbea%16
IPv4 Address. . . . . . . . . . . : 192.168.0.138
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
Open any modern browser and try to open http://192.168.0.1

Finally login to console with the default username admin and the password stored on the sticker on the bottom of the device
Setting of OmniSIM APN for Cradlepoint
In Connection Manager select the correct modem profile, and then the SIM card (notice how APN is wrongly set)

Click on Edit, in the WAN Interface Profile screen that is displayed select SIM/APN/Auth on the left hand side.
Set the following as shown in the image below.
Authentication Protocol: PAP
Access Point Name 01: data.apn.name (IPV4)

Save the new settings (grey button on bottom of previous image)
Below shows the router trying to connect with the correct APN settings (data.apn.name)

Successfully registered to the VPLMN

Test the Internet connectivity through the router
$ NETSTAT.EXE -nr
===========================================================================
Interface List
16...d0 8e 79 fa 34 c4 ......Intel(R) Ethernet Connection (16) I219-LM
21...00 a5 54 95 e8 78 ......Microsoft Wi-Fi Direct Virtual Adapter
24...02 a5 54 95 e8 77 ......Microsoft Wi-Fi Direct Virtual Adapter #2
11...00 09 0f fe 00 01 ......Fortinet Virtual Ethernet Adapter (NDIS 6.30)
6...00 a5 54 95 e8 77 ......Intel(R) Wi-Fi 6E AX211 160MHz
1...........................Software Loopback Interface 1
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.94 50
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.0.0 255.255.255.0 On-link 192.168.0.94 306
192.168.0.94 255.255.255.255 On-link 192.168.0.94 306
192.168.0.255 255.255.255.255 On-link 192.168.0.94 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.0.94 306
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.0.94 306
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 331 ::1/128 On-link
6 306 fe80::/64 On-link
6 306 fe80::2ec7:9ca3:bf5c:6293/128
On-link
1 331 ff00::/8 On-link
6 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
Check the internet connection with Ping
$ ping google.com
Pinging google.com [172.253.63.139] with 32 bytes of data:
Reply from 172.253.63.139: bytes=32 time=151ms TTL=54
Reply from 172.253.63.139: bytes=32 time=146ms TTL=54
Reply from 172.253.63.139: bytes=32 time=152ms TTL=54
Reply from 172.253.63.139: bytes=32 time=154ms TTL=54
Ping statistics for 172.253.63.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 146ms, Maximum = 154ms, Average = 150ms
$ ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=96ms TTL=113
Reply from 8.8.8.8: bytes=32 time=57ms TTL=113
Reply from 8.8.8.8: bytes=32 time=60ms TTL=113
Reply from 8.8.8.8: bytes=32 time=62ms TTL=113
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 96ms, Average = 68ms
Last updated
Was this helpful?