[Techtalk] Basic connection questions

[mgmonza at sdf.lonestar.org]

Thanks, EEva.

<sigh> I'm afraid you're right.  When I can manage a second laptop or else 
find some absolutely reliable way to back this one up, I'll try either 
tackling wpa-supplicant or putting a different distro on this one.

It helps a lot to have a knowlegeable person confirm what I suspected: 
this is one of those brick walls no amount of head-banging is going 
to even dent.

MG

  On Mon, 27 May 2013, Eeva Järvinen wrote:

> Date: Mon, 27 May 2013 10:40:23 +0300
> From: "[ISO-8859-1] Eeva Järvinen" <ejarvinen at gmail.com>
> To: Techtalk <techtalk at linuxchix.org>
> Subject: Re: [Techtalk] Basic connection questions
> 
> Don't know squat about .deb-based distros, but my experience of NM has been
> that you really need to let it run the whole show, and after you've got it
> running, then tweak the bits to more of your liking (say, making a
> connection go up at boot instead of login). Configuring NM is best done,
> IME, via the distro-given utilities.
>
> NM is one ornery piece of kit but it's (probably) the only way these days
> if you don't feel like tackling wpa-supplicant yourself. FWIW, my laptop
> runs F18 with NM and starts the wlan at boot via rc.local - I couldn't make
> NM do it all by itself with any reliability, probably due to systemd+nfs
> conflicts (don't ask).
>
>
> hth,
> Eeva
>
>
> 2013/5/27 <mgmonza at sdf.lonestar.org>
>
>> I know this isn't a really good place to ask this, but this time sponge
>> has gotten out of hand.
>>
>> I know I shouldn't be using Windows-lite aka Ubuntu, but I haven't the $$
>> to spend on an upgraded laptop and Ubuntu is what's on this one.
>>
>> On all my Debian desktops, I hacked, slashed and configured my way through
>> getting inernet connections working using /etc/network/interfaces, mainly,
>> plus a variety of utilities depending on the connection device.  All I did
>> thereafter was ifup, ifdown, and ifconfig.
>>
>> Now with nm-applet, aka networking-manager, none of this works.  I gave in
>> to the point of only asking that I be allowed to bring up the wired
>> connection myself, eth0, and even that works only randomly and usually not
>> at all.
>>
>> I've put the eth0 stanza in the interfaces file, and the network manager
>> ignores it as requested but eth0 still won't connect to anything. I get the
>> infuriating repetetive dhcpdiscover then sleep, with no other diagnostics,
>> and no connection.  Then an untterly random connection -will- happen, work
>> for a time, then drop.  I'd do without network manager altogether if
>> wpa-supplicant didn't add a whole other layer of incoherent complexity.  I
>> live in a too low a rent and too prone to hacking area to risk wep.
>>
>> I'm putting this question out on this list because I hate the
>> Windowsesques, Simon Says, do this random illogical sequence of events and
>> it -might- work nature of this problem.  Does anyone know or can anyone
>> point me to an explanation of what's going on?
>>
>> MG
>> ______________________________**_________________
>> Techtalk mailing list
>> Techtalk at linuxchix.org
>> http://mailman.linuxchix.org/**mailman/listinfo/techtalk<http://mailman.linuxchix.org/mailman/listinfo/techtalk>
>>
> _______________________________________________
> Techtalk mailing list
> Techtalk at linuxchix.org
> http://mailman.linuxchix.org/mailman/listinfo/techtalk
>