Hello Sean,
no,I use the second one. But until now I am not able to get my previous result. I am a lot to learn in the world of Linux and Tinycore ans I leanr slowly. I put below the results of lsub and ifconfig on Tinypilot to give you some informations on my research.
tc@pypilot:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0bda:8153
tc@pypilot:~$ ifconfig
eth0 Link encap:Ethernet HWaddr B8:27:EB:59:A8:6F
inet addr:192.168.14.1 Bcast:192.168.14.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe59:a86f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:602 errors:0 dropped:1 overruns:0 frame:0
TX packets:475 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:55874 (54.5 KiB) TX bytes:336113 (328.2 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:14473 errors:0 dropped:0 overruns:0 frame:0
TX packets:14473 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:929469 (907.6 KiB) TX bytes:929469 (907.6 KiB)
wlan0 Link encap:Ethernet HWaddr B8:27:EB:59:A8:6F
inet addr:10.10.10.10 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::ba27:ebff:fe59:a86f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3301 errors:0 dropped:0 overruns:0 frame:0
TX packets:3222 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:194013 (189.4 KiB) TX bytes:392303 (383.1 KiB)
Despite to get eth0 with an adress 192.168.14.1, when I stop wlan9 I loose the link, even If it is configured on this adress.
Thank you for your help,
Eric
By the way, I operate Tinypilot with the Pypilot version 0.32. I have tried to update to version 0.36 with the help of the marcobergman workbook without success. Did you consider usefull to update to this last version, and if yes what is the best way to install it on Tinypilot?
Many thanks again!
As I said, I learn slowly. The eth0 I looked on ifconfig was just a change of naming due to my modification in networking.sh. The actual device was still wlan1. I have to dig again!
no,I use the second one. But until now I am not able to get my previous result. I am a lot to learn in the world of Linux and Tinycore ans I leanr slowly. I put below the results of lsub and ifconfig on Tinypilot to give you some informations on my research.
tc@pypilot:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0bda:8153
tc@pypilot:~$ ifconfig
eth0 Link encap:Ethernet HWaddr B8:27:EB:59:A8:6F
inet addr:192.168.14.1 Bcast:192.168.14.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe59:a86f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:602 errors:0 dropped:1 overruns:0 frame:0
TX packets:475 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:55874 (54.5 KiB) TX bytes:336113 (328.2 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:14473 errors:0 dropped:0 overruns:0 frame:0
TX packets:14473 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:929469 (907.6 KiB) TX bytes:929469 (907.6 KiB)
wlan0 Link encap:Ethernet HWaddr B8:27:EB:59:A8:6F
inet addr:10.10.10.10 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::ba27:ebff:fe59:a86f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3301 errors:0 dropped:0 overruns:0 frame:0
TX packets:3222 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:194013 (189.4 KiB) TX bytes:392303 (383.1 KiB)
Despite to get eth0 with an adress 192.168.14.1, when I stop wlan9 I loose the link, even If it is configured on this adress.
Thank you for your help,
Eric
By the way, I operate Tinypilot with the Pypilot version 0.32. I have tried to update to version 0.36 with the help of the marcobergman workbook without success. Did you consider usefull to update to this last version, and if yes what is the best way to install it on Tinypilot?
Many thanks again!
As I said, I learn slowly. The eth0 I looked on ifconfig was just a change of naming due to my modification in networking.sh. The actual device was still wlan1. I have to dig again!