These things are a bit rubbish. At least tonight it is. I bought one today. I can see that it establishes a VPN connection with nat tunneling. But stlll the fourth light doesn't come up, which means it's ready for use (Vodafone sure signal, UK). I did see it flash the fourth light, implying it is updating the software, then it went through a phase akin to a reboot. But not it mostly exchanges lots of ESP encapsulated packets and tons of NTP transfers and no availability. I'll see what it does in a day, but I'm not impressed so far. I've opened up all ports and protocols to their hosts and still no joy. Their website implies it's a plug in and do nothing job.
22:54:09.162908 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.164499 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.182893 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.183166 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.202757 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.203910 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.222751 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.223883 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.242865 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.243886 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.262707 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.265433 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.282735 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.283813 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.302710 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.304002 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.322902 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.323122 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.342755 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.344840 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.362831 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.363099 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.382895 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.384310 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.402768 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.405886 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.422748 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.423775 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.442726 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.445048 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.462864 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.463121 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.482912 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.484296 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.502712 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.506479 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.522733 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.523870 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.542893 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.546560 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.562728 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.563871 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 48
22:54:09.582766 IP 192.168.14.91.123 > 212.183.133.181.123: NTPv4, Client, length 48
22:54:09.583871 IP 212.183.133.181.123 > 192.168.14.91.123: NTPv4, Server, length 4
.
.
.
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
22:54:32.957641 IP 192.168.14.91.4500 > 212.183.133.179.4500: isakmp-nat-keep-alive
.
.
.
root# tcpdump -nn -i eth1 ip host 192.168.14.91
22:54:38.537487 IP 192.168.14.91.4500 > 212.183.133.179.4500: NONESP-encap: isakmp: phase 2/others ? #37[]
22:54:38.651023 IP 212.183.133.179.4500 > 192.168.14.91.4500: NONESP-encap: isakmp: phase 2/others ? #37[]
22:54:42.031076 IP 192.168.14.91.4500 > 212.183.133.179.4500: UDP-encap: ESP(spi=0x1633adf1,seq=0x257), length 100
22:54:42.053769 IP 212.183.133.179.4500 > 192.168.14.91.4500: UDP-encap: ESP(spi=0xc5588a43,seq=0x1cf), length 100
22:54:44.074197 IP 192.168.14.91.4500 > 212.183.133.179.4500: UDP-encap: ESP(spi=0x1633adf1,seq=0x258), length 132
22:54:44.097949 IP 212.183.133.179.4500 > 192.168.14.91.4500: UDP-encap: ESP(spi=0xc5588a43,seq=0x1d0), length 132
22:54:45.527801 IP 212.183.133.179.4500 > 192.168.14.91.4500: UDP-encap: ESP(spi=0xc5588a43,seq=0x1d1), length 132
22:54:45.533046 IP 192.168.14.91.4500 > 212.183.133.179.4500: UDP-encap: ESP(spi=0x1633adf1,seq=0x259), length 132
So it seems to get a working-established vpn all night long but still doesn't progress to the ready state. I've received the sms that says that it's ready for use.
I don't want to use their forums because to do that automatically turns off the sending of paper billing to you as a side effect, a necessary thing for a company, and you have to call them to get paper billing re-instated. You would have thought that would have thought of a thing called "preferences", fuckers. To turn off you paper billing, required by HMRC, as an un-notified side effect of logging into their website is just plain dirty. And the support staff know it, they don't waste any time on it, they just tell you that you can call them and they'll turn it back on.
I tried to call them, but of course my phone dropped out several times and none of them called me back. Duh! I'm calling about a device that helps overcome signal problems. If, it drops out call me back, I'm sick of wading through the menu options each time.
Still doesn't work, a whole evening later. Maybe the ntp queries relate to a QOS test, but then they should tell you that it would need to burn in for a day or two. If that's the problem in any case. As I *can* establish a working VPN, I don't know what else could be the problem. No packets are being dropped.
The latest forum posting for the device is June 27, I don't know what's going on there.