HooToo for local network and gateway to Wifi

[Michael Wimble]

I have a HooToo Nano

I have the following local devices:

Pi3a (Raspberry Pi 3), gigabit USB->Ethernet dongle on eth1

Pi3b (Raspberry Pi 3), gigabit USB->Ethernet dongle on eth1

Jetson (Jetson TK1)

Gigabit switch connecting Pi3a, Pi3b, Jetson, HooToo and external ethernet connector

I'm trying to get all the devices to talk to each other via 10.10.10.xx addresses, which works. And if I connect my laptop to the built-in ethernet connector, I can access all the devices at greater than 400 M bits/sec.

I want the HooToo to open up that local network so I can access it via the WiFi transceiver built into the HooToo.

I set the HooToo as a Wireless access point and point it to my local Wifi Network on 10.0.1.xx, and it connects fine.

I can set my laptop to use the "TripMate Nano XXXX" as my wifi router, and the laptop connects fine and can still see e.g., google.com since the HooToo is routing through my home network. 

The HooToo has the DNS Server set up to hand out 10.10.10.xx address. My laptop, e.g., is handed 10.10.10.1

I have yet to get my robot CPUs to talk to the Nano. 

I cannot even see the nano, even though they are connected via the switch to the ethernet port on the nano. E.g., using Pi3b, which is assigned 10.10.10.4:

pi@pi3bEth:~ $ sudo arp-scan --interface=eth1 --localnet

Interface: eth1, datalink type: EN10MB (Ethernet)

Starting arp-scan 1.8.1 with 256 hosts (http://www.nta-monitor.com/tools/arp-scan/)

10.10.10.2 00:04:4b:48:ff:60 NVIDIA

10.10.10.3 00:e6:4c:68:01:0e (Unknown)

10.10.10.10 ac:87:a3:03:1e:b4 (Unknown)

There is some device at 10.10.10.10, which doesn't ping. But I don't see the HooToo. I've tried lost of combinations of in /etc/network/interfaces to get eth1 to use DHCP from the HooToo, but without being able to even see the HooToo, that just doesn't work.

Has someone figured out how to build a LAN of CPUs in a robot and then have them gateway/route out to an external Wifi network. I want to be able to run rviz on my laptop and observe the robot without having to hard-wire an ethernet cable. And using all WiFi among the robot CPUs is too slow.

[Marco Walther]

On 07/18/2016 01:54 PM, Michael Wimble wrote:
> I have a HooToo Nano
>
> I have the following local devices:
> Pi3a (Raspberry Pi 3), gigabit USB->Ethernet dongle on eth1
> Pi3b (Raspberry Pi 3), gigabit USB->Ethernet dongle on eth1
> Jetson (Jetson TK1)
> Gigabit switch connecting Pi3a, Pi3b, Jetson, HooToo and external
> ethernet connector
>
> I'm trying to get all the devices to talk to each other via 10.10.10.xx
> addresses, which works. And if I connect my laptop to the built-in
> ethernet connector, I can access all the devices at greater than 400 M
> bits/sec.
>
> I want the HooToo to open up that local network so I can access it via
> the WiFi transceiver built into the HooToo.

From the little I learned quickly, the HooToo seems to be doing exactly
the opposite of what you want. So, I guess, your best bet would be a
very customized openwrt installation. You probably want to make the
ethernet port the `LAN' and the WiFi the WAN and do NAT between the two.

-- Marco

>
> I set the HooToo as a Wireless access point and point it to my local
> Wifi Network on 10.0.1.xx, and it connects fine.
>
> I can set my laptop to use the "TripMate Nano XXXX" as my wifi router,
> and the laptop connects fine and can still see e.g., google.com since
> the HooToo is routing through my home network.
>
> The HooToo has the DNS Server set up to hand out 10.10.10.xx address. My
> laptop, e.g., is handed 10.10.10.1
>
> I have yet to get my robot CPUs to talk to the Nano.
>
> I cannot even see the nano, even though they are connected via the
> switch to the ethernet port on the nano. E.g., using Pi3b, which is
> assigned 10.10.10.4:
>

> pi@pi3bEth:~ $sudo arp-scan --interface=eth1 --localnet

>
> Interface: eth1, datalink type: EN10MB (Ethernet)
>
> Starting arp-scan 1.8.1 with 256 hosts
> (http://www.nta-monitor.com/tools/arp-scan/)
>
> 10.10.10.200:04:4b:48:ff:60NVIDIA
>
> 10.10.10.300:e6:4c:68:01:0e(Unknown)
>
> 10.10.10.10ac:87:a3:03:1e:b4(Unknown)
>
>
>
> There is some device at 10.10.10.10, which doesn't ping. But I don't see
> the HooToo. I've tried lost of combinations of in
> /etc/network/interfaces to get eth1 to use DHCP from the HooToo, but
> without being able to even see the HooToo, that just doesn't work.
>
> Has someone figured out how to build a LAN of CPUs in a robot and then
> have them gateway/route out to an external Wifi network. I want to be
> able to run rviz on my laptop and observe the robot without having to
> hard-wire an ethernet cable. And using all WiFi among the robot CPUs is
> too slow.
>

> --
> You received this message because you are subscribed to the Google
> Groups "HomeBrew Robotics Club" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hbrobotics+...@googlegroups.com
> <mailto:hbrobotics+...@googlegroups.com>.
> To post to this group, send email to hbrob...@googlegroups.com
> <mailto:hbrob...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/hbrobotics.
> For more options, visit https://groups.google.com/d/optout.