**** BEGIN LOGGING AT Sat Jul 14 03:00:00 2018
Jul 14 16:40:33 <ravikp7> abhishek_, jkridner: I'm using this module https://github.com/mscdex/cap for sending and receiving ethernet packets. I've tested it on Linux and Windows, I'm able to ping google nameserver from board, so internet access through this approach is working good so far.
Jul 14 16:40:50 <ravikp7> I just had to set default gateway 192.168.6.1 from board
Jul 14 16:42:28 <ravikp7> I made the proxy change the source ip to some ip in the host's subnet and mac address same as that of host
Jul 14 16:46:17 <ravikp7> I tried using the host's default gateway as board's gateway too, making the board think (through proxy arp) that the host's router has got the 192.168.6.1
Jul 14 16:47:34 <ravikp7> But this just works partially, board can ping other devices in host's subnet and can access internet
Jul 14 16:48:00 <ravikp7> But other devices in the host's subnet can't reach the board through ping
Jul 14 16:48:40 <ravikp7> As the board sends the reply to the default gateway as it is unaware of the host's subnet
Jul 14 16:50:33 <ravikp7> So, now I'm implementing a proper proxy gateway which talks to board with ip and mac address provided by board. And talks to host's network with host's subnet ip and host's mac
Jul 14 17:03:22 <ravikp7> jkridner: we need the default debian image to set default gateway of usb0 in case eth0 isn't available and also nameserver as names can't be resolved by default on usb0 interface
Jul 14 17:06:07 <jkridner[m]> can we issue a command to do it ourselves?
Jul 14 17:35:44 <ravikp7> jkridner: default gw can be set, but it resets after reboot
Jul 14 17:36:28 <ravikp7> name server setup isn't also reliable, there's symlink in /etc/resolv.conf
Jul 14 17:41:56 <ravikp7> setting it manually everytime will depricate the purpose of automatic internet access on just plugging the device..
**** ENDING LOGGING AT Sun Jul 15 03:00:01 2018