search

felixge / node-ar-drone

A node.js client for controlling Parrot AR Drone 2.0 quad-copters.
http://nodecopter.com/
MIT License
1.76k stars 428 forks source link

multiple network adapters/interfaces #127

Closed bno1 closed 9 years ago

bno1 commented 9 years ago

My pc has 2 network interfaces, one being the onboard network card connected to the internet and the other begin the wireless adapter that is connected to the drone.

I want all my applications to connect through the onboard adapter and my drone client to connect through the wireless adapter, but the library does not support this very well.

I managed to do this easily for the control and navigation connections by creating 2 custom UDP sockets and creating a new UdpControl and UdpNavdataStream using them. But for the video stream it's not that easy. The only way to bind a TCP socket to a local address is through net.connect/net.createConnection which don't play nice with the way TcpVideoStream uses the socket.

wiseman commented 9 years ago

Just so I understand, are both network interfaces trying to route the drone's 192.168.1.1 default address? Because in general it shouldn't be the application deciding which network interface to use, it should be the kernel's network routing. If you can keep the networks separate, everything should "just work". For example, my home network is 192.168.100.x, and when I connect my ethernet interface to that and connect my wifi adapter to the drone's network, everything works as you described: Browsers, etc. are able to connect to the internet while the drone client talks to the drone.

Or have I misunderstood what the issue is that you're running into? (I'm not a networking expert :smiley:)

bno1 commented 9 years ago

I found the problem. Because I don't haven an wifi adapter I use android's tethering to connect my pc to the drone. Problem is that android's dhcp gives the network interface an 192.168.42.x ip, so the operating system doesn't know that 192.168.1.1 is actually on the 192.168.42.x network.

bno1 commented 9 years ago

I solved it by running

route add 192.168.1.0 mask 255.255.255.0 192.168.42.129

This routes all the traffic send to network 192.168.1.x through android's gateway

Thanks for the insights @wiseman

wiseman commented 9 years ago

Excellent, glad you were able to figure out the solution.