Question (concise version):
Where in my log files would I find information regarding the networking steps executed between the time I have left the login screen and the time I have landed comfortably at my desktop screen?
Thanks in advance!
$ uname -a Linux schmo 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
Linux - Because I like banging my head against walls.
Question (longer version with more than one clause):
Who, or what daemon, or which scripts are responsible for setting up my network settings at login? I have found that several attempts to modify
/etc/network/interfaces either go ignored or end in a non-functioning setup, but that the two-line original loopback version works fine. I want to know where the action is actually happening.
bash scripts should I pepper with echo-and-dump statements, or what environment variables should I be aware of and set, if the current level of feedback in the currently-available log files is not of a resolution high enough to catch the network changes being performed during login?
Motivation (at least one of them):
How would I go about telling my computer to establish a wireless bridge after my wireless network adapter is up and running, which itself seems to occur only after I log in, sometimes completing after I have already clicked on Firefox but before I remember to look for the wifi status icon, argh.
What I've done so far:
SUCCESSFULLY added a VM running precise server i686 to my precise desktop i686 using KVM
SUCCESSFULLY updated, upgraded, and added to the packages on the VM through the bridge setup suggested at http://devilsworkshop.org/tutorial/create-virtual-machineos-ubuntu-1204-kvm/59576/, and following the course of https://help.ubuntu.com/12.04/serverguide/index.html, while ssh'd from my desktop. This implies the bridge was working, if only for one session. My guess is that between the time I set up my
/etc/network/interfacesfile and the time I no longer had internet access through my VM, the changes I (or KVM, or someone) made to my configuration files had propagated only partially through my system(s) from boot to boot and restart to restart, whatever that means.
UNSUCCESSFULLY tried to resurrect VM internet access by adding wlan0 to
/etc/network/interfacesin various forms, including installing
RECEIVED AN ERROR from
wpa_supplicantwhich I believe I was able to trace back to the fact that wpa services are mysteriously already running each time I restart networking. This led me to the discovery that...
AVAHI WILL NOT STAY DEAD due to being respawned by process #1 ;
avahithen runs other stuff, and may be responsible for the normally satisfying, but now vexing, behavior of my wireless connection coming alive each time I log in (or not doing so, if I try to modify
More details are available; just tell me what you'd like. I am playing a game of Chutes-and-Ladders with the heaps of knowledge I have learned from trying what I have so far, and the vast chasms of ignorance about even basic terms and SOP that keep me from putting things together.
PS Some other resources I have looked at:
Note the part about wireless bridging. I have my reasons for ignoring this caveat for the moment.