Centralized services that enable you to actually use your product are problematic at best.
The reliability here has not been great. To achieve "5 nines" uptime, would require that FRS
place several different smartlink servers in geographically different locations, with auto-round-robin
DNS to make sure a user can connect with whatever one is still online. This is how many large
corp high-volume web servers are done; they have two or three regional servers, with automatic
routing when you try to connect from your web browser.
I will explore the personal VPN articles that people were playing with before SmartLink.
Ken - NM9P
Anything that improves remote reliability is a good move. With the Flex capability remote operation of our stations will be widely used. As a hobby we are involved with developing our capability at a very fast pace. I think there are alternatives to networks that are private and may meet more stringent users. VPN. There are a lot of smart hams in the Flex community and I am impressed with the ideas and dynamics of the exchanges.
Our Cable networks from Comcast, AT&T and others are not without their down time and service interruptions. For an antenna farm maybe dedicated lines would be appropriate.
This is an exciting time in amateur radio.
- Ping your ISP's hand-off from a device on the same subnet. (Confirms that there are no L2 problems between you and your ISP).
- Ping your ISP's hand-off from a device on one of your internal subnets. (Confirms that you have no routing/security issues between your internal network and your ISP)
- Ping an IP in your provider's network. If you can't find one that's publicly listed, or the helpdesk won't give you one, do a traceroute to something in the internet, and use the second or third hop. This confirms that routing between you and your ISP is configured correctly.
- Ping an internet IP. I normally use 188.8.131.52 or 184.108.40.206 Quad- Nine secure DNS servers. This confirms that routing from your ISP to the specific IP you've pinged is correctly configured.
- Ping an internet domain name. This verifies your/your provider's DNS configuration is correct.
If steps 1 or 2 fail, it's most likely a problem on your internal network.
If step 3 fails, there would appear to be a problem in your provider's network. Note, though, that if you get no response at all then your ISP may have simply blocked ICMP to/from their infrastructure addresses.
Step 4 failing indicates a potential problem between your ISP and one of their upstream providers.
Step 5 failing indicates issues with name resolution.
Cant wait for the "invisible yagi and tower" to hit the market so I can have a station at home again. ;->
Turns out I had to power cycle the 6400.
Moral of the story: I don't know why the 6400 got confused, but I sure am glad I installed an IP relay/remote power device so I could do it from 20 miles away.
Global Cache iTach IP2CC, totally worth the money, requires just a little bit of manual reading (sorry).