If the author has said the same thing like you just did I would have done it in a heartbeat. It perfectly fits those in situation like mine now, why waste another sd card when the usb can be on its own? When I read about it, it was like reading a bible to me. Everything was like foreign language, too much info to absorb in a short period of time and I have only 1 pi to mess around with. At any rate, it would definitely be on the list of things to do for the next week.
For now, the only thing that I have used is /etc/dhcpcd.conf. It is more reliable and straightforward than the /etc/network/interfaces. I have spent so much time to research about it, but at the end of the day I still come up empty-handed about how to use /etc/network/interfaces correctly. Every time it hits I have no choice but to literally pull the plug on my headless pi, that is not a good thing to do.
Yesterday I am stuck with this scenario, I disable the internal Wifi through blacklist and plug in the pi with the usb dongle TL-WN722N v1. Just like I said earlier, I left the /etc/network/interfaces untouched. The content of my /etc/dhcpcd.conf is like this:
static domain_name_servers=192.168.1.1 184.108.40.206
The pi booted up fine however wlan0 (TL-WN722N) was listed but NOT associated with any address when it should be with 192.168.2.1. I then ran "sudo ifconfig wlan0 192.168.2.1" and it accepted it. Reboot the pi and wlan0 still behaved the same way.
I ran "lsusb" and this is the output of it:
I then ran "lsmod" and this is the output of it:
Based on what I have read from other people they said:
Bus 001 Device 005: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n is the WN722N in lsusb output.
ath9k_htc is the name of the WN722N driver according to the lsmod output.
I needed wlan0 to associate itself with 192.168.2.1 automatically every time the pi reboot because I am trying to make an AP out of the pi from this tutorial: https://learn.adafruit.com/setting-up-a ... t?view=all
Every time when the wlan0 is blank the isc-dhcp-server would fail. At this point, I don't know what to do to make it accepted 192.168.2.1 so I tried to add "sudo ifconfig wlan0 192.168.2.1" to /etc/rc.local. Here is how it looks:
To my expectation wlan0 did associate itself with 192.168.2.1 after reboot. The isc-dhcp-server is up and running. Hostapd is also up and running. However, the pi was not showing any sign that the AP is working at all.
I then edited driver=ath9k_htc in the /etc/hostapd/hostapd.conf file like this:
And the AP is still not functioning at all. I tried the same method with the internal Wifi by commented out the driver in hostapd.conf and the AP worked fine.
In linux what do I need to do to find the right driver name of the usb device and how do I know if the right driver is loaded into the kernel at reboot? And last but not least what step did I miss to make this AP work?
Thank you very much.