SatoriNet + SatoriNetLR

I’m a software engineer and architect by trade and am currently developing new platforms for Walt Disney Company. In order to do my job I need a reliable internet service at home so I can work part time from the boat. Since the concept of working from the boat came around, I have dreamed of connecting to the internet while at anchor in some far off place in the middle of nowhere. Perhaps close to a waist high surf break and somewhere to restock my supply of water and beer. Somewhere I can swim down and scrub the hull on occasion or sit in the shade in a hammock and hack away on the laptop. Not too much to ask for really…. I started the boat network by simply joining the NMEA wifi client to my router so I could connect to one network for using navigation software on my iPhone and iPad, eventually adding other network clients over time to do more. The ultimate would be to use a cellular or satellite hotspot as a source of internet and then allow any device connected to the boat network be able to also have internet. Today this happened on Satori.

Satori coming home from Port Madison
Satori coming home from Port Madison

 

It’s not as simple as you would think. First of all, I really wanted to be able to connect to the boat network on shore. I also wanted to be able to switch from one hotspot to another, yet while at the dock connect to a land based internet service. This way I can have internet so I can work from the boat pretty much anywhere there is a strong cellular signal. Last weekend I finally got around to also adding the long range wifi antenna to the network so I could be on shore and connect to the boat network, possibly even my own internet. This way I can set an anchor drag alarm, monitor the depth, wind speed, wind direction or even use the internet whenever I’m near Satori. One would think that sailing would be a better endeavor without all of the gadgets and savvy technology but my livelihood depends on it so I can work and get paid. I am able to work as long as a week without having to go into the office and later in my career will find a way to work remotely. If I want to take a couple of days off near a weekend right now, it would allow for sailing into the San Juan Islands during this summer for at least half of the summer. It’s just a matter of learning how to find suitable anchorages with enough proximity of a cellular tower to do my job. Satori is doing great keeping herself charged without shore power for days even with the refrigerator running nonstop.

SatoriNet network diagram
SatoriNet network diagram

 

So you’re wondering how this all works? I think it’s a great discovery that few have been able to achieve so please allow me to break it down for you. There are network links from your computer/tablet/smartphone out to the internet and each of them communicates via TCP or transmission control protocol, and uses an IP or internet protocol to move data from link to link securely. When my smartphone wants to connect to the boat network, it has two options. The first option is the wifi router, which is inside of the cabin and is the hub and main communicator for all of the other links. The wifi signal can barely reach to the bow of the boat because of the thickness of the hull, and in some cases loses connection when I’m not inside of the cockpit. The second and primary choice is the Ubiquiti wifi antenna. It is connected to the boom gallows frame, stands about three and a half feet long, and sits about ten feet above the waterline. The Ubiquiti Bullet is meant to broadcast or receive wifi so theoretically if I wanted to, I could scan wifi signals on shore and use it for my internet as long as I can connect to land based wifi network. Since I will be providing my own wifi, I will use it to broadcast my own network away from the boat for as far as a quarter mile line of sight. The bullet antenna has a wire that goes into the ‘network’ locker, which is where the wifi router and main network components are located. The antenna is powered by 12 volt and I have a switch to turn it off when I do not need it. Then I can simply connect to the Dlink network router. The Dlink router is also receiving wifi from the Vesper Marine XB-8000 client. This little blue box will take my NMEA data and convert it to TCP via wifi so my navigation software can use it. The Dlink router has a dedicated (static) IP so the Vesper XB will always remain connected. If either become disconnected, the VesperXB will keep looking for the router and trying to connect to it and does as soon as it is back online. Also, the Vesper XB-8000 wifi is hidden so people cannot see it’s own wifi transmission. I suppose I could leave it on but that would be three wifi networks broadcasting and five if I did not hide the ones not being used. Finally for the Dlink router to receive internet it uses two options. The first one is simply a combined cable modem and wifi router, which would normally be Comcast or other land based provider. It receives internet from coaxial cable that comes from outside of the boat next to the shore power connection, and sends internet to the Dlink router via ethernet cable. If the cable modem has wifi, that is also hidden in favor of limiting the available wifi connections to the ones I want.

Linksys network wifi router
WAN shows that I am connected to the internet, LAN shows that it is hosting under IP 192.168.0.1, which is the router’s home address

 

The Dlink wifi router serves three purposes for me; First it will receive internet from a dedicated Cat5 cable port. Second it will receive the Ubiquity antenna and can send my boat sensor data and internet to any device in the network. Third it will receive the NEMA via an automatic wifi connection from the VesperXB unit. Finally it can act as a host so I can connect directly to it via wifi in case I want to turn the Ubiquity antenna off and save energy.

DHCP IP address range for hosting connected devices. Each device is assigned an IP from 192168.0.100 to  192168.0.199. Always broadcast enables smartphone and tablet compatibility.
DHCP IP address range for hosting connected devices. Each device is assigned an IP from 192168.0.100 to 192168.0.199. Always broadcast enables smartphone and tablet compatibility.

 

When I am away from the dock I will connect to the internet via a Verizon mobile hotspot. It has the best coverage of LTE networks and can also provide more limited coverage in remote areas where TMobile or Sprint may not be available. This is great for working over a VPN. I do not need a very fast connection for work since I’m just sending small bits of data to our code repository, browsing web pages, and chatting with my co-workers via Skype and email. In order to connect the mobile hotspot to the Dlink router, I use the Asus WL-330N wireless mobile router. It is a very small and low energy device that can work in a number of configurations. For my purpose, I am using it for wifi account sharing from the mobile hotspot through the Asus mobile router through ethernet to the Dlink router, and finally out through the Ubiquity Bullet which is connected to my computer to smart-device. Once they all connected, I still had issues with the mobile hotspot not providing internet to the smart-devices. The laptop worked well though. I figured it had something to the with the NetBios and so I set it to always broadcast, which extended the compatibility to iOS devices and other smartphones.

The Asus device connects a cellular hotspot device to the Linksys router to serve WAN (wide area network) which is the internet as we know it. Use the 'wifi account sharing' option to connect a cellular hotspot to the network. The ip address of this device varies and can be either 192.168.1.1 or 192.168.220.1, which was difficult to figure out.
The Asus device connects a cellular hotspot device to the Dlink router to serve WAN (wide area network) which is the internet as we know it. Use the ‘wifi account sharing’ option to connect a cellular hotspot to the network. The ip address of this device varies and can be either 192.168.1.1 or 192.168.220.1, which was difficult to figure out.

 

Now when I leave on a trip, I can stay connected without having to do anything new. One I am settled into my anchorage with sufficient cellular service, I can stay there and work completely off the grid. The energy cost is about .8 amps to run all five components. So that is my network in a nutshell. Five networking devices which allows me to connect to a single network from far away or allow me to connect the network to the internet via mobile hotspot. You’d think it would be simple to configure this but it took my background in engineering and networking to figure it out and it was not easy. The good news is that it works very well and is quite stable. If there is a glitch (lets not kid ourselves) I just reboot the network components at the breaker panel. Feel free to ask any question if you’re planning on doing a similar network. It’s confusing and time consuming at first but once you decide what you need you shouldn’t have too much trouble deciding what you need and how to connect it to the network.

 

6 Replies to “SatoriNet + SatoriNetLR”

  1. Great description of your network! Could be improved by including a bill of materials or list of manufacturers and model numbers of equipemnt in one file, rather than searching through the blog – but that’s O.K. because it is all there, you just have to look for it! Also, screen grabs of configuration files or the web pages for setup would be good, too.

  2. Thanks for the writeup! The description of your use cases gave me a few ideas. You mention total power consumption of 0.8A, but do you have figures for any of the individual components?

    1. Hi Nathan,

      I don’t have any real data about the draw of each component. I’m sure you could do the calculation for each one just by looking at the type of charger each one uses. I suspect they all probably draw close to the same thing. Listing the components: VHF antenna splitter, NMEA multiplexer, AIS transponder/receiver, cellular wifi hotspot, LAN router, hotspot to router bridge, and wifi base station. My guess would be approximately .1 amp each with maybe one having slightly more and another having slightly less. Since none of them do very much data processing, I suspect they are all no more than .1amp each except perhaps the Ubiquiti bullet.

  3. Your Ubiquity link goes the to the 5GHz model. You’re using a 2.4GHz model though right? Also, are you using the 110 POE adapter or did you mod it to 12v?

    1. Thor! Yes you are correct. I will fix the link. I did the 12 volt mod instead of paying for a POE adapter. Since POE is already 12 volt, you only need to add an inline fuse to protect it. It only means splicing the negative and positive from an ethernet cable. I do suggest getting an outdoor cable, which provides a better insulator. Hit me up if you need any more info. Cheers.

  4. Dude, great write up. Your setup is way more complex than mine but I see some new ideas. I have a Ubiquiti bullet and a TP Link wireless router. I can see them individually but not together. I don’t know what I’m missing. I cannot access the internet with the Bullet alone. Can you help me with configuring this mess?
    I had never thought about using the system to transmit data to myself while off the boat. I have some dogs I’d like to keep an eye on via a camera setup too see which of the two is my problem child. LOL
    How do you set it up to transmit instead of receive?
    How do you join your NEMA data in all of this? My MFD has wifi. Would that be an avenue?
    This is the setup I was following but I have a 110 volt Poe which will work for now.
    https://sailingyachtamalia.wordpress.com/2015/05/11/wifi-internet-access-on-board/
    Thanks for letting me pick your brain.
    Donna

Leave a Reply

Your email address will not be published. Required fields are marked *