Getting the Shark to Work

Post Reply
wb8ldw
Posts: 4
Joined: Wed Aug 09, 2017 2:16 pm

Getting the Shark to Work

Post by wb8ldw »

All, I see where there have been some concerns about getting the Shark to work. I received one from a friend who said it worked once at his mothers but not up here. I tried firing it up and logging in - no joy. I used a utility on my phone to check the IP address and sure enough it was there. Used the boot loader reset and could get in directly with the IP address exactly once. Next time no joy again. Back to the boot loader. Into the box exactly one time with the IP address. Okay, the work around that worked for me was found in the trouble shooting area, and should be made a permanent sticky in the trouble shooting -- http://192.168.1.116/openspot.html_gz#login. I made a short cut and can get there any time now.
Here is where I think the problem is - When the Shark appears on the network, it gets its DHCP Dynamic Host Control Protocol from your local router. This includes the lease time, IP address and MAC to Hostname translation. The problem comes in when you try to use "Openspot" which is host name and needs to be translated to an IP address. In the case of Comcast users, the router is the third DNS after two Comcast DNS Servers. The Comcast servers will return a result but not the result you want. Since they are operational, the request never drops through to your local router (DNS). Hopefully this explanation is technically correct. If it aint, http://192.168.1.116/openspot.html_gz#login works.
I got on the air after a couple days and got a great report. Already in love with the box and hate to have to give it back to my friend.

-tom wb8ldw
wd7f
Posts: 2
Joined: Wed Sep 26, 2018 8:13 pm

Re: Getting the Shark to Work

Post by wd7f »

Did anyone ever reply to this? This is the link that's supposed to get you in there: 192.168.1.116/main.html_gz
k9agr
Posts: 24
Joined: Sun Jun 10, 2018 8:59 pm

Re: Getting the Shark to Work

Post by k9agr »

the use of http://openspot/ on windows takes advantage of the netbios naming built into windows. That isn't always enabled on all windows machines though. The direct IP address is the most reliable way to connect.

Also, many home routers (not all) run a DNS cache internally, and are the only DNS server the computers are assigned via DHCP. This means they have the ability to decide how resolution happens. If your router works this way, you can usually assign (reserve) the IP for the openspot and add your own dns override entry in that nameserver.

For http://openspot.local/ to work, you need a multicast dns client on your network that is configured to understand the .local domain. Mac has this enabled by default, and most linux distributions also have it.

Again, directly by IP is most reliable.

jim
Post Reply