On Thursday 21 June 2018 12:20:21 Slávek Banko wrote:
On Thursday 21 of June 2018 11:35:47 William Morder wrote:
On Wed June 20 2018 07:23:07 William Morder wrote:
I recently migrated from Debian Jessie to the Devuan Jessie-Beowulf merged version. My problem is, now I cannot turn off my network, nor control the connection at all. I was using the network-manager-tde package, which has always worked just fine for me. I've tried all the other network managers, and don't like how they behave. In particular, I want to set my network so that it never connects automatically, and will only connect manually.
Devuan Jessie works well but is based on Debian Jessie which is moving into LTS.
Devuan Ascii works well and is based on Debian Stretch and is well supported.
Devuan Beowulf is in development based on Debian Buster in development.
I don't know what you mean by "Devuan Jessie-Beowulf merged version". I would not recommend Jessie as it is moving to LTS. I would not recommend Beowulf at this time except to bleeding edge users who are comfortable fixing any problems they might encounter. I would suggest you start with a working Devuan Ascii before thinking about TDE PSB.
--Mike
Sorry, that's totally my mistake.
I've been running Debian for about a year now, but I've only been running Devuan for about a week. I am not familiar with what Devuan names correspond to the naming in Debian. I know that Devuan Ascii corresponds to Debian Stretch, and somewhere I thought I remembered that Beowulf corresponded to Jessie. Apparently they did not change the name for Jessie?
At the time I was only sporadically online, had no list at hand to check, and no browsers installed so that I could look it up online.
In any case, I believe I have solved my network issues (or at least found a workaround). There are some deeper issues that I will bring up in another thread.
Bill
For Devuan Jessie, the name was identical to Debian, but with another meaning - it means minor planet Jessie (nr.10464).
https://devuan.org/os/releases https://minorplanetcenter.net/iau/lists/MPNames.html
Cheers
A-ha! Slavek enlightens us all.
Bill
"A-ha! Slavek enlightens us all."
Slavek = Gnu Yoda
Kate
On Thursday 21 June 2018 18:23:55 Kate Draven wrote:
On Thursday 21 June 2018 12:20:21 Slávek Banko wrote:
On Thursday 21 of June 2018 11:35:47 William Morder wrote:
On Wed June 20 2018 07:23:07 William Morder wrote:
I recently migrated from Debian Jessie to the Devuan Jessie merged version. My problem is, now I cannot turn off my network, nor control the connection at all. I was using the network-manager-tde package, which has always worked just fine for me. I've tried all the other network managers, and don't like how they behave. In particular, I want to set my network so that it never connects automatically, and will only connect manually.
Devuan Jessie works well but is based on Debian Jessie which is moving into LTS.
Devuan Ascii works well and is based on Debian Stretch and is well supported.
Devuan Beowulf is in development based on Debian Buster in development.
[*snip]
In any case, I believe I have solved my network issues (or at least found a workaround). There are some deeper issues that I will bring up in another thread.
Bill
Okay, just because I am an insufferable pedant, I would like to point out that if we diverge from the question asked - even if we are vaguely talking about computers - then this is still technically "off-topic"!
But to return to our muttons! (I beg my Francophone and Francophile readers to forgive me; I know this is a mistranslation of the original.)
So here's the problem: I got my network working reasonably well, except for one glitch, that it automatically connects at startup. I've tried wicd and tdenetworkmanager, as well as the knetworkmanager. Also I've dabbled with pretty much every other network management tool, and nothing changes. I set the manager so that it does not connect automatically (which worked fine for me in Debian Jessie), but now it keeps resetting the configuration, and automatically connects on startup.
After I am up and running, I am able to connect and disconnect with few problems, but this is really annoying.
Is it better to change the configuration file in one of these locations? /etc/network/interfaces /etc/NetworkManager/NetworkManager.conf I didn't have a problem like this before; never in Kubuntu, nor in Debian Jessie; this is new only since I started running Devuan.
Aside from a few glitches, by the way, Devuan does run better than Debian. In particular, Debian with systemd used to hang when I tried to reboot, but this doesn't happen in Devuan.
I appreciate any help, suggestions or observations.
Bill
Am Freitag 22 Juni 2018 schrieb William Morder:
So here's the problem: I got my network working reasonably well, except for one glitch, that it automatically connects at startup. I've tried wicd and tdenetworkmanager, as well as the knetworkmanager. Also I've dabbled with pretty much every other network management tool, and nothing changes. I set the manager so that it does not connect automatically (which worked fine for me in Debian Jessie), but now it keeps resetting the configuration, and automatically connects on startup.
After I am up and running, I am able to connect and disconnect with few problems, but this is really annoying.
Is it better to change the configuration file in one of these locations? /etc/network/interfaces /etc/NetworkManager/NetworkManager.conf
Hello Bill,
in case I understood correctly and you don't want to connect to the internet at boot time, have you tried this in "/etc/default/networking"?:
# Set to 'no' to skip interfaces configuration on boot #CONFIGURE_INTERFACES=yes
Regards, Stefan
On Friday 22 June 2018 09:30:24 Stefan Krusche wrote:
Am Freitag 22 Juni 2018 schrieb William Morder:
So here's the problem: I got my network working reasonably well, except for one glitch, that it automatically connects at startup. I've tried wicd and tdenetworkmanager, as well as the knetworkmanager. Also I've dabbled with pretty much every other network management tool, and nothing changes. I set the manager so that it does not connect automatically (which worked fine for me in Debian Jessie), but now it keeps resetting the configuration, and automatically connects on startup.
After I am up and running, I am able to connect and disconnect with few problems, but this is really annoying.
Is it better to change the configuration file in one of these locations? /etc/network/interfaces /etc/NetworkManager/NetworkManager.conf
Hello Bill,
in case I understood correctly and you don't want to connect to the internet at boot time, have you tried this in "/etc/default/networking"?:
# Set to 'no' to skip interfaces configuration on boot #CONFIGURE_INTERFACES=yes
Regards, Stefan
That may be what I was looking for. I overlooked the folder, I suppose, because it had the nondescript name "default" ... but there's a lot of other interesting stuff in there. I might get lost, and may wish to experiment with modifications of some other programs and services.
All the web pages I searched pointed to those other two locations, but they didn't solve the problem. I'll report on my results.
Thanks much!
Bill
On Fri, 22 Jun 2018 18:30:24 +0200 Stefan Krusche linux@stefan-krusche.de wrote:
Am Freitag 22 Juni 2018 schrieb William Morder:
So here's the problem: I got my network working reasonably well, except for one glitch, that it automatically connects at startup. I've tried wicd and tdenetworkmanager, as well as the knetworkmanager. Also I've dabbled with pretty much every other network management tool, and nothing changes. I set the manager so that it does not connect automatically (which worked fine for me in Debian Jessie), but now it keeps resetting the configuration, and automatically connects on startup.
After I am up and running, I am able to connect and disconnect with few problems, but this is really annoying.
Is it better to change the configuration file in one of these locations? /etc/network/interfaces /etc/NetworkManager/NetworkManager.conf
Hello Bill,
in case I understood correctly and you don't want to connect to the internet at boot time, have you tried this in "/etc/default/networking"?:
# Set to 'no' to skip interfaces configuration on boot #CONFIGURE_INTERFACES=yes
This is bad idea. It would cause ALL interfaces not to come up at boot, including lo, which can cause some deamons not to start and other to behave weirdly.
Removing auto clause from wlan0 (or whatever you wifi interface name is) in /etc/network/interfaces should be enough for stopping auto connect at startup if you are not also autostarting some gui misconfiguration program.
Am Samstag 23 Juni 2018 schrieb Nick Koretsky:
On Fri, 22 Jun 2018 18:30:24 +0200 Stefan Krusche linux@stefan-krusche.de wrote:
in case I understood correctly and you don't want to connect to the internet at boot time, have you tried this in "/etc/default/networking"?:
# Set to 'no' to skip interfaces configuration on boot #CONFIGURE_INTERFACES=yes
This is bad idea. It would cause ALL interfaces not to come up at boot, including lo, which can cause some deamons not to start and other to behave weirdly.
Oh, I didn't know that, it was just a guess. I should have said that I hadn't tried that out.
Removing auto clause from wlan0 (or whatever you wifi interface name is) in /etc/network/interfaces should be enough for stopping auto connect at startup if you are not also autostarting some gui misconfiguration program.
Thank you, Stefan
On Saturday 23 June 2018 02:09:20 Stefan Krusche wrote:
Am Samstag 23 Juni 2018 schrieb Nick Koretsky:
On Fri, 22 Jun 2018 18:30:24 +0200
Stefan Krusche linux@stefan-krusche.de wrote:
in case I understood correctly and you don't want to connect to the internet at boot time, have you tried this in "/etc/default/networking"?:
# Set to 'no' to skip interfaces configuration on boot #CONFIGURE_INTERFACES=yes
This is bad idea. It would cause ALL interfaces not to come up at boot, including lo, which can cause some deamons not to start and other to behave weirdly.
Oh, I didn't know that, it was just a guess. I should have said that I hadn't tried that out.
Removing auto clause from wlan0 (or whatever you wifi interface name is) in /etc/network/interfaces should be enough for stopping auto connect at startup if you are not also autostarting some gui misconfiguration program.
Thank you, Stefan
Not to worry. I am usually pretty cautious; and if I screw up something based on other people's suggestions, it is only lost time, as I always back up everything.
Bill
On Friday 22 June 2018 23:12:58 Nick Koretsky wrote:
On Fri, 22 Jun 2018 18:30:24 +0200
Stefan Krusche linux@stefan-krusche.de wrote:
Am Freitag 22 Juni 2018 schrieb William Morder:
So here's the problem: I got my network working reasonably well, except for one glitch, that it automatically connects at startup. I've tried wicd and tdenetworkmanager, as well as the knetworkmanager. Also I've dabbled with pretty much every other network management tool, and nothing changes. I set the manager so that it does not connect automatically (which worked fine for me in Debian Jessie), but now it keeps resetting the configuration, and automatically connects on startup.
After I am up and running, I am able to connect and disconnect with few problems, but this is really annoying.
Is it better to change the configuration file in one of these locations? /etc/network/interfaces /etc/NetworkManager/NetworkManager.conf
Hello Bill,
in case I understood correctly and you don't want to connect to the internet at boot time, have you tried this in "/etc/default/networking"?:
# Set to 'no' to skip interfaces configuration on boot #CONFIGURE_INTERFACES=yes
This is bad idea. It would cause ALL interfaces not to come up at boot, including lo, which can cause some deamons not to start and other to behave weirdly.
Removing auto clause from wlan0 (or whatever you wifi interface name is) in /etc/network/interfaces should be enough for stopping auto connect at startup if you are not also autostarting some gui misconfiguration program.
Yes, I was intending to try those places I mentioned above. This other suggestion was a last resort, and I was sort of thinking the same thing. I only want wlan0 not to connect until I do so manually.
Bill
-
Kate Draven -
Nick Koretsky -
Stefan Krusche -
William Morder