I have used several "how to" tutorials / instructions and still cannot figure out "who is on first" when it comes to activating wireless connection - IN GENERAL
I can do " ifconfig" , "wpa_supplicant.conf " etc.
I did use wicd and could not make the connection.
What I am missing is - <b>how does Linux starts / makes wireless connection in general.</b> . In what sequence and which files are involved.
PS I have SSH working and it was much easier to install / activate/ test.
Any pointers would be appreciated.
Please no references to RPi tutorial(s) needed, been there, done that,
Wireless is the same as wired, it is just a network connection. The decision of 'who is on first' is decided by the systems that are connected to the network. Servers listen, and clients call. But servers can also be clients, and clients can be servers. Just the same as the telephone.
If you want to optimize you will need to manually configure the connection in the /etc/wpa_supplicant/<name>.conf file. Assuming that your distro is also relatively modern (i.e. uses systemd rather than sysvinit) you should also have systemd-networkd available, which is simple to configure.
Thanks for reply.
I have been busy trying to find stable OS which actually does WiFi.
What I really need is to know how the whole communication process starts.
During my research I found this gem "wpa_supplicant is build by OS , copied to /etc/... and deleted..." When I try to simply implement "standard" WiFi I actually received "Wpa_supplicant does not exist ". Not much help there.
That is why I ask "who is on first"
Actually I like to use "bonding" so I do not have to worry which type of network I'll am using.
But I really need to hit the books first.
Yeah, all Linux distros, AFAIK, use iw and wpa_supplicant to implement wifi over WPA. Generally both will be embedded in the installer software, but not the core distribution. It (they) just needs to be installed like any other package while bootstrapping the install.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
You are correct, however in case of both Raspian Desktop and Ubuntu MATE OS one is lead to believe that "raspi-config" does the (WiFi) activation. AS you pointed out - unfortunately one cannot activate something which is not properly or not at all installed in the first place.
I need to find a REAL controller hardware "computer". I am getting frustrated with these OS for toys which are good for flashing LED at best.
Of course when I say something to that effect I get kicked out from forum.
Been there and experienced many show stopping issues.
Is I pointed out - one has to read the mail to see there are few "gotcha" which points to so far unsolved basic problems with latest release of Ubuntu WiFi.
The "problem" is , IMHO, nobody addresses the basic (WiFi) issue and people post hacks to solve THEIR issue only.
"solutions " like "remove battery and reinstall it" , reboot , reinstall etc do not solve this.
I can do
For what it's worth... I completely understand your frustration. I have many hobby boards including several RPI, Qualcomm Dragonboard and a few Allwinner based boards. It seems like I am always hacking something together when I am working with my Linux-based IoT hobby projects.
Why did the OS missed the USB Wifi on first ifconfig?
Or did it missed RPi interface?
When I did an OUI lookup on your MAC address it looks like the raspberry pi ethernet is the only interface available in your first ifconfig.
It sounds like a timing issue which is one of the most common problems I seem to face on these boards.
If I were debugging this I would first make sure that the USB device is present after booting the board: lsusb
If the USB device is listed then you probably have a timing issue where the device is not ready when your network comes up. The easiest 'hack' to fix this would be a simple network restart at the end of your init script: /etc/init.d/networking restart
I actually have this 'hack' on two of my Allwinner based boards and both of them have a USB wifi/ethernet.
I am not a Linux guru so don't listen to me. There are probably other ways to fix USB timing issues on Linux.
David, thanks for the "sympathy card".
I have switched to Linux about three / four years ago - just because.
I went thru hell for few months trying to figure out why my USB devices were just coming and going. My solution - get rid of my switched POWERED USB hub connected between two devices - PC and RPi. It is hard to believe , but the problem was and still is TWO 6 feet long USB cables connected to the switch! Any cables - it is the length and as you pointed out - the timing.
After realizing the doggy OS RPi operates with I decided to do cross-compiling...
Learn ssh and now looking at WiFi.
I do not mind learning and pasting things together IF they work as "advertised".
This WiFi is such incomplete kluge I should get my money back from the "charitable corporation ".
Yes, I am rebuilding the configuration files to make sure the booting process actually checks the presence of devices , USB included, and all the files to make WiFi fly - not just posting meaningless errors.
So - I am learning how to write bash scripts!
And I though I left "bat" files somewhere in Oregon 30 some odd years back.
You do understand that the chances of someone who knows some obscure framework seeing your message is not very high? The majority of people who answer questions here are C/C++/C# Windows or Web developers.
I realized that TCF is as obscure as assembly language to many.
The "problem" is that the authors must not had an incentive to provide much "help" to implement it. It works fine , but it is a pain to fix when it goes sideways.
I have a knack to pick wrong technology....