This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
TinyPilot as client instead of Access Point
#1
Has anyone tried to run TP as a client to OP instead of an Access point? 

I can see there are settings that can be adjusted for this but I just cannot seem to get my head around what it means and how it works...


Once TP is a client that would mean it would join the OpenPlotter network ( I would set a static IP for TP)
Then in OpenCPN under the pypilot plugin config I would change the IP address to the new TPs address
Then in settings I would change the 20220 to point to the new TP address

Is that all there is to it?

Am I missing some glaringly obvious reason why it should not work?

Also, if Openplotter is connected as a client to my main home network, and TP is connected as a client to OpenPlotter, would that mean that I can connect to TP from any computer that is on either network via ssh or via opencpn pypilot plugin? 
This would certainly make testing much easier?!
  Reply
#2
(09-10-2019, 09:06 AM)rastam4n Wrote: Has anyone tried to run TP as a client to OP instead of an Access point? 

I can see there are settings that can be adjusted for this but I just cannot seem to get my head around what it means and how it works...


Once TP is a client that would mean it would join the OpenPlotter network ( I would set a static IP for TP)
Then in OpenCPN under the pypilot plugin config I would change the IP address to the new TPs address
Then in settings I would change the 20220 to point to the new TP address

Is that all there is to it?
Yes. outside

Am I missing some glaringly obvious reason why it should not work?
[/quote]
If you want to use a second tinypilot as a client and control a remote tinypilot using it's local gpio over wifi it's something different but covered in the wiki.
Quote:Also, if Openplotter is connected as a client to my main home network, and TP is connected as a client to OpenPlotter, would that mean that I can connect to TP from any computer that is on either network via ssh or via opencpn pypilot plugin? 
This would certainly make testing much easier?!

you should have internet from the TP, but if you want to ssh in from the outside,
you need to do port forwarding to make this work, or ssh tunneling.
  Reply
#3
(09-10-2019, 09:06 AM)rastam4n Wrote: Has anyone tried to run TP as a client to OP instead of an Access point? 

I can see there are settings that can be adjusted for this but I just cannot seem to get my head around what it means and how it works...


Once TP is a client that would mean it would join the OpenPlotter network ( I would set a static IP for TP)
Then in OpenCPN under the pypilot plugin config I would change the IP address to the new TPs address
Then in settings I would change the 20220 to point to the new TP address

Is that all there is to it?

Am I missing some glaringly obvious reason why it should not work?

Also, if Openplotter is connected as a client to my main home network, and TP is connected as a client to OpenPlotter, would that mean that I can connect to TP from any computer that is on either network via ssh or via opencpn pypilot plugin? 
This would certainly make testing much easier?!

I tested this configuration:
Openplotter on Rasp PI with 2 wifi interfaces:
        Int. 1 as client connected to router (actually my phone as hotspot)
        Int. 2 as AP

Tinypilot connected as client to openplotter AP interface:
        Normally It assumes a dynamic IP but is reachable via hostname ‘box’ 
        Once connected via ssh, tinypilot can reach the Internet, and thus is updatable conecting to GIT
  Reply
#4
(09-10-2019, 04:51 PM)webber63 Wrote:
(09-10-2019, 09:06 AM)rastam4n Wrote: Has anyone tried to run TP as a client to OP instead of an Access point? 

I can see there are settings that can be adjusted for this but I just cannot seem to get my head around what it means and how it works...


Once TP is a client that would mean it would join the OpenPlotter network ( I would set a static IP for TP)
Then in OpenCPN under the pypilot plugin config I would change the IP address to the new TPs address
Then in settings I would change the 20220 to point to the new TP address

Is that all there is to it?

Am I missing some glaringly obvious reason why it should not work?

Also, if Openplotter is connected as a client to my main home network, and TP is connected as a client to OpenPlotter, would that mean that I can connect to TP from any computer that is on either network via ssh or via opencpn pypilot plugin? 
This would certainly make testing much easier?!

I tested this configuration:
Openplotter on Rasp PI with 2 wifi interfaces:
        Int. 1 as client connected to router (actually my phone as hotspot)
        Int. 2 as AP

Tinypilot connected as client to openplotter AP interface:
        Normally It assumes a dynamic IP but is reachable via hostname ‘box’ 
        Once connected via ssh, tinypilot can reach the Internet, and thus is updatable conecting to GIT

Thanks Webber

I have it set and connected as a client now, can you show me an example of how you would connect using the hostname box? Do I just replace eg 192.168.14.1 with the word "box"?

actually....

Nevermind! I just tried it and it works fine... We need a how to for this shit, stuff so simple you gotta bother people asking.

Anyhow Thanks again! ..... box ffs....
  Reply
#5
(09-10-2019, 06:05 PM)rastam4n Wrote:
(09-10-2019, 04:51 PM)webber63 Wrote:
(09-10-2019, 09:06 AM)rastam4n Wrote: Has anyone tried to run TP as a client to OP instead of an Access point? 

I can see there are settings that can be adjusted for this but I just cannot seem to get my head around what it means and how it works...


Once TP is a client that would mean it would join the OpenPlotter network ( I would set a static IP for TP)
Then in OpenCPN under the pypilot plugin config I would change the IP address to the new TPs address
Then in settings I would change the 20220 to point to the new TP address

Is that all there is to it?

Am I missing some glaringly obvious reason why it should not work?

Also, if Openplotter is connected as a client to my main home network, and TP is connected as a client to OpenPlotter, would that mean that I can connect to TP from any computer that is on either network via ssh or via opencpn pypilot plugin? 
This would certainly make testing much easier?!

I tested this configuration:
Openplotter on Rasp PI with 2 wifi interfaces:
        Int. 1 as client connected to router (actually my phone as hotspot)
        Int. 2 as AP

Tinypilot connected as client to openplotter AP interface:
        Normally It assumes a dynamic IP but is reachable via hostname ‘box’ 
        Once connected via ssh, tinypilot can reach the Internet, and thus is updatable conecting to GIT

Thanks Webber

I have it set and connected as a client now, can you show me an example of how you would connect using the hostname box? Do I just replace eg 192.168.14.1 with the word "box"?

Yes:
ssh box

To try to find the actual address assigned by dhcp to tinypilot, give a:
ping -b 10.10.10.255

Interrupt it with ctrl-c after a few seconds and then:
arp -a -n

(you will get a list of active IPs on the network, one of these is your tinypilot)

This will work, of course, if tinypilot manages to connect to Openplotter WiFi



Inviato dal mio iPhone utilizzando Tapatalk
  Reply
#6
(09-10-2019, 06:13 PM)webber63 Wrote: Yes:
ssh box

To try to find the actual address assigned by dhcp to tinypilot, give a:
ping -b  10.10.10.255

Interrupt it with ctrl-c after a few seconds and then:
arp -a -n

(you will get a list of active IPs on the network, one of these is your tinypilot)

This will work, of course, if tinypilot manages to connect to Openplotter WiFi



Inviato dal mio iPhone utilizzando Tapatalk

actually this worked within opencpn connections tab and within the opencpn pypilot config tab... I just replaced the ip address with "box" and it worked! Maybe I should reboot to be sure....

Okay so reboot went okay everything is still connected to "box"


Attached Files Thumbnail(s)
   
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)