3 Sep
2020
3 Sep
'20
7:33 p.m.
On Thursday 03 September 2020 12:26:01 Dr. Nikolaus Klepp wrote:
Anno domini 2020 Thu, 3 Sep 10:27:43 -0700
William Morder via trinity-users scripsit:
Looks like so:
###########
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
# auto wlx00027288d1fd
allow-hotplug wlx00027288d1fd
iface wlx00027288d1fd inet dhcp
wpa-ssid myssid
wpa-psk mypassphrase
###########
The only thing changed since sometime in remote prehistory (before TDE) is the
line that used to read wlan0, which is now that ugly wlx-stuff.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thursday 03 September 2020 10:01:53 Dr.
Nikolaus Klepp wrote:
the deamon part of wicd runs as root, your gui client communicates with
that daemon. there's also a wicd-cli for pure hearted.
btw, what's in your /etc/netwok/interfaces? since beowulf/buster anything
but "lo" will give trouble.
> I am not in control of my network connection -- as proved by the fact
> that I can't go online/offline or offline/online without rebooting. This
> is what is driving me crazy.
>
> If anybody is annoyed by my complaints, and failure to resolve my own
> issues, please be patient with me, and remember that I never had any
> problems with my network itself for the past few years. I would bounce
> between
> tdenetworkmanager and wicd, it's true, but my network connection was
> stable, and I felt in control. I had other problems, yes, but this is
> different.
>
> Bill
>
> Anno domini 2020 Thu, 3 Sep 07:57:03 -0700
William Morder via trinity-users scripsit:
Yeah, that's where I think I am headed. I already spent most of the past
two years using wicd instead of tdenetworkmanager. I just keep hoping
that I will get a different answer, so I ask the fortune teller to give
me another reading, and then another ...
I would be okay with using wicd instead; no problem. But now when I go
offline, wicd doesn't offer me "options" -- that is, it looks like it
hangs on, like it's still online, and I cannot get back online without
rebooting.
Maybe I should run wicd as root? I don't like to do that. Usually wicd
doesn't behave in this manner, which I why I'm bothered. While I have Internet, of a sort, I still have a
few glitches; for
example, I cannot go offline, then go online again. Somehow, wicd
either auto-connects to my wifi network; when instead, I want to
enable wifi, then look at the available network choices, because my
local network has several nodes or access points within the building
where I live, and somehow it doesn't always choose the strongest or
closest signal. I have an access point right outside my door, yet
autoconnect seems to avoid it.
But when I try to disconnect, sometimes wicd seems to hang on, and
show me still connected, yet I can't download emails or go online for
other stuff. When I run macchanger, it keeps showing me that my mac
address changes; and I run knetstats-trinity (which is a nice simple
gui tool) and it shows my wireless is connected then disconnected,
shows activity then no activity; yet in reality, I can't go online.
So my only recourse at this point is to reboot.
When I tried to get tdenetworkmanager to run, I had those problems
already discussed earlier. I managed to download the packages and
dependencies to install network-manager-tde without systemd, so it
all *seems* like it ought to work out right, but I always end up
going back to wicd; which, again, is only sort of half-working at the
moment, and I must keep rebooting.
How would I go about pruning away the wicd stuff that I don't want,
and keeping only the tdenetworkmanager and required dependencies,
etc.? I've search apt-get, but I believe that I already have all the
dependencies and recommends. I can't think what else I might have
missed.
Bill
Just my experience: eiter use wicd (and uninstall network-manager) or
use networkmanager (and uninstall wicd).