Re: debian12: something destroys /etc/network/interfaces at boot

Thank you for your mail. On Wed, Mar 27, 2024 at 12:42 AM Andy Smith wrote: > On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote: > > I changed a gateway on a remote site using /etc/network/interfaces by > > changing gateway. However, at reboot some old gateway IP

Re: debian12: something destroys /etc/network/interfaces at boot

Thank you for your quick reply. On Wed, Mar 27, 2024 at 12:22 AM Henning Follmann wrote: > On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote: > > I changed a gateway on a remote site using /etc/network/interfaces by > > changing gateway. However, at reboot some

Re: debian12: something destroys /etc/network/interfaces at boot

On Tue, Mar 26, 2024 at 11:27 PM Dustin Jenkins wrote: > On my Debian 12 system, the connman service was helping itself to interfaces, > including my bridge interfaces that I wanted left alone. Maybe try disabling > or removing it? > > sudo systemctl stop connman > sudo systemctl disable

Re: debian12: something destroys /etc/network/interfaces at boot

Thank your for your quick and detailed reply. On Tue, Mar 26, 2024 at 7:01 PM Greg Wooledge wrote: > On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote: > > I changed a gateway on a remote site using /etc/network/interfaces by > > changing gateway. However, at

Re: debian12: something destroys /etc/network/interfaces at boot

On Tue, Mar 26, 2024 at 7:18 PM Pierre-Elliott Bécue wrote: > As it's a PVE kernel I guess you rely on Proxmox. > *Theoretically*, Proxmox VE uses /etc/network/interfaces.new to apply THIS! (OMG why didn't I see this! Thank you!!) ohh thanks so much for your quick reply, my "machine" indeed is

debian12: something destroys /etc/network/interfaces at boot

Hi, I changed a gateway on a remote site using /etc/network/interfaces by changing gateway. However, at reboot some old gateway IP reappears. I really hate when some magic knows better than an explicitly set value. What happens here? How can I get rid of this? It is 100% reproducible. I have no

Re: Debian 8 how to install and run init.d scripts?

Hi, thanks for your reply. On Tue, Oct 22, 2019 at 5:45 AM Peter Wiersig wrote: > Steffen Dettmer writes: > > So you propose not to use init.d scripts. I usually prefer a simple shell > > script that is easy to test, systemd is just way to complex. > > Like Gre

Re: Debian 8 how to install and run init.d scripts?

On Mon, Oct 21, 2019 at 9:32 PM Greg Wooledge wrote: > On Mon, Oct 21, 2019 at 09:26:57PM +0200, Steffen Dettmer wrote: > > On Mon, Oct 21, 2019 at 3:27 PM Greg Wooledge > wrote: > > > This is not correct. Debian's systemd will use init.d scripts in > > > c

Re: Debian 8 how to install and run init.d scripts?

Hi, thanks for your reply. On Mon, Oct 21, 2019 at 3:27 PM Greg Wooledge wrote: > > But probably > > for Debian you are right, if I understood correctly, newer versions do > not > > even support init.d / LSB anymore, so using systemd units seems to be > > required there. > > This is not

Re: Debian 8 how to install and run init.d scripts?

Hi, thanks for your reply. On Sun, Oct 20, 2019 at 10:26 PM Peter Wiersig wrote: > 5.) > Instead of init.d scripts create systemd units. > https://wiki.debian.org/systemd#Creating_or_altering_services https://freedesktop.org/wiki/Software/systemd/ So you propose not to use init.d scripts. I

Re: Debian 8 how to install and run init.d scripts?

Hi, thank you for your reply. On Fri, Oct 18, 2019 at 3:34 PM Jonas Smedegaard wrote: > Quoting Steffen Dettmer (2019-10-18 15:17:10) > > in short: how to use "init.d" scripts on Debian? > > In short: > > service $SERVICE stop > Thanks for the tip. man i

Debian 8 how to install and run init.d scripts?

Hi, in short: how to use "init.d" scripts on Debian? in detail: On one server a init.d script with LSB header does not work, at least when started by command line. I traced down the following: #1 init.d/script sources /lib/lsb/init-functions #2 /lib/lsb/init-functions has support for hooks:

Re: Why do UID values of system users matter?

Hi, thanks for your quick reply. I see, multiboot with different /etc but shared /usr or /local could invite a lot of trouble if using different UIDs, indeed! Thanks for the quick explanation. > (Apparently man used uid 13 in Debian 8 / Jessi but 6 in Debian 9 / > > Stretch). > > AFAICS, user

Re: Debian Wiki and LSB (https://wiki.debian.org/LSB)

. Steffen On Fri, Aug 16, 2019 at 11:19 PM Roberto C. Sánchez wrote: > On Fri, Aug 16, 2019 at 11:15:32PM +0200, Steffen Dettmer wrote: > >Hi, > >is the "Debian Wiki" at [1]https://wiki.debian.org/ "official"? If > so, I > >hope her

Why do UID values of system users matter?

Hi, just for my curiosity I wonder why the numeric UID values matter at all, for example: update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages

Debian Wiki and LSB (https://wiki.debian.org/LSB)

Hi, is the "Debian Wiki" at https://wiki.debian.org/ "official"? If so, I hope here is the right place to ask. The wiki at e.g. https://wiki.debian.org/LSB tells "Currently all major distributions comply with the LSB" and https://wiki.debian.org/DebianLsb tells "Debian strives to follow and

Re: Static IP not working ("connmand" problem)?

Hi, On Sun, Aug 20, 2017 at 8:09 PM, Sven Hartge wrote: >> How to configure static IP? network/interfaces as in [1] seem not to >> work because of a "connmand". > > connmand? The package "connman" is not contained in the default > installation of Debian. Thank you for your

Re: Static IP not working ("connmand" problem)?

On Sun, Aug 20, 2017 at 8:09 PM, Sven Hartge wrote: >> How to configure static IP? network/interfaces as in [1] seem not to >> work because of a "connmand". > > connmand? The package "connman" is not contained in the default > installation of Debian. > >> What is "connmand",

Static IP not working ("connmand" problem)?

Hi, in short: How to configure static IP? network/interfaces as in [1] seem not to work because of a "connmand". in detail: I had a failure of my DHCP server and was unable to connect to my statically configured Debian 8 server. Or at least I intended to configure static IP. The setup is very

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue, Jan 10, 2017 at 12:51 PM, Dominique Dumont <d...@debian.org> wrote: > On Monday, 9 January 2017 22:49:02 CET Steffen Dettmer wrote: >> I'm looking at Jessie (Debian 8) man fsck. I found no refernce >> to systemd. I think this is some compatiblity feature of systemd. &

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote: >>> I'd rather keep it as simple as possible >> >> you can still use sysvinit as init I read that trying to use sysvinit causes trouble and several things depend on systemd at the moment. > The shell scripts used by

Re: Systemd: no error but "maintenance mode"

On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote: >> What happened before: >> I had issue with a Debian server SATA bus [1]. I noticed because >> apt-get upgrade hung, because initramfs updater calls "sync" which >> hang because of [1]. All operations accessing a certain (backup)

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

Hi, thank you for your quick reply. On Mon, Jan 9, 2017 at 1:38 AM, David Wright <deb...@lionunicorn.co.uk> wrote: > On Sun 08 Jan 2017 at 15:56:36 (+0100), Steffen Dettmer wrote: >> apparently is ignored and "1" is assumed instead, BUT systemd does not >>

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

rtant bugs? Probably not, because the issues seem to be known already? Steffen On Sun, Jan 8, 2017 at 2:56 PM, Steffen Dettmer <steffen.dett...@gmail.com> wrote: > Hi, > > I think I found some more information. > > In short: > "Failed at step exec spawning /bin

systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

Hi, I think I found some more information. In short: "Failed at step exec spawning /bin/plymouth: no such file or directory" but I have no clue why it is suddenly missing or suddenly required. I found postings in the internet that simply installing plymouth seems not to solve this issue. What

Systemd: no error but "maintenance mode"

Hi, What happened before: I had issue with a Debian server SATA bus [1]. I noticed because apt-get upgrade hung, because initramfs updater calls "sync" which hang because of [1]. All operations accessing a certain (backup) disk blocked. Shutdown over network. It was reported server power LED

Re: bridges with multiple static IPs or DHPC - how to configure?

Hi, thanks for your mail! On Thu, Jun 5, 2014 at 5:03 PM, Curt cu...@free.fr wrote: On 2014-06-05, Steffen Dettmer steffen.dett...@gmail.com wrote: Do you - or anyone else - know the ip replacement for brctl show? ip link show br1 is too brief, no information about the slave devices or STP

Re: bridges with multiple static IPs or DHPC - how to configure?

Hi all, thanks for all your answers! I think I found the solution: all bridge parameters must go into the first iface stanza. Subsequent stanzas configure IPs and/or DHCP. Using allow-hotplug instead of auto, the bridge is not bought up at boot and can be started asynchrously by some script.

Re: bridges with multiple static IPs or DHPC - how to configure?

when using VLAN). On Wed, Jun 4, 2014 at 11:59 PM, Tom H tomh0...@gmail.com wrote: On Wed, Jun 4, 2014 at 2:00 PM, Steffen Dettmer: Of course everything works as expected when configuring manually with ip, brctl etc. (By the way, you don't need brctl; ip link can create bridges.) Ohh, I see

bridges with multiple static IPs or DHPC - how to configure?

Hi, how to configure a bridge with multiple static IPs and/or DHPC via /etc/network/interfaces? I tried many combinations, but I didn't find any working one. Of course everything works as expected when configuring manually with ip, brctl etc. Any working example would be great! The rest of

Re: persistent-net.rules for fixed ethX names and VLANs

Hi, this is a reply to an very old posting just to tell the solution to the mailing list archives. Problem was that Micrel Driver does net set DRIVER name. Here a patch. On Tue, Nov 26, 2013, Steffen Dettmer steffen.dett...@gmail.com wrote: On Tue, Nov 19, 2013, Pascal Hambourg pas

udevd and persistent network rules for USB NICs

Hi, I have a device with several internal mini PCIe card slots usable for PCI Express mini modem cards (UMTS, LTE...). These cards normally are USB cards and get some ethX device name assigned by Linux, which I don't like. Instead, they should get another name, for example usb-ethX. Is it

Debian 7.5 fails with kernel.org backports

Hi, after upgrading to Debian 7.5 (linux-headers-3.2.0-4-common), backports 3.10.2 [1] does not compile anymore [2]. Without it, I have issues with Antheros WLAN cards. Does Debian 7.5 include another backported versions? Can it be removed and replaced by official backports 3.10.2 from [1]? It

Re: dpkg -i first.dep second.dep: installs but does not configure one?

, Steffen Dettmer a écrit : $ dpkg -i first.dep second.dep pre-dependency problem: nd-second pre-depends on nd-first nd-first is unpacked, but has never been configured. dpkg is smart enough to figure out the order in which packages need to be configured. Isn't it a bug

dpkg -i first.dep second.dep: installs but does not configure one?

Hi, I have two packages, first and second. Package second depend on package first. I have to use dpkg (I don't use apt, because there is no package server / no online link etc). When I run $ dpkg -i first.dep second.dep I get the error: dpkg: regarding .../nd-second_5.0.02_i386.deb containing

How to migrate multiple *.dep package files into one?

Hi, two (or more) *.deb packages now become one. All files that were in any of the packages now are in one and the same, which supersedes them all. I dont think it is the best idea to call some dpkg -r oldpackage from the postinst script of the only remaining package. How to do this right?

Re: How to migrate multiple *.dep package files into one?

On Thu, Mar 27, 2014 at 6:03 PM, steffen.dett...@gmail.com wrote: I dont think it is the best idea to call some dpkg -r oldpackage from the postinst script of the only remaining package. ps: I tried Replaces: oldpackage Conflicts: oldpackage in control file, but the old package remains

How to use logrotate postrotate *bash* script

Hi, logrotate seems to execute postrotate scripts using /bin/sh and I found no way where to specify which script interpreter to use. Starting with a she-bang line seem to have no effect. Even if I manually run logrotate as root who has /bin/bash as login shell, /bin/sh is used. How to make

Re: persistent-net.rules for fixed ethX names and VLANs

Hi, sorry, unfortunately I missed your mail, thank you for your response and sorry for the delay. On Tue, Nov 19, 2013 at 11:24 PM, Pascal Hambourg pas...@plouf.fr.eu.org wrote: Hello, Steffen Dettmer a écrit : On Thu, Nov 14, 2013 at 4:36 PM, Steffen Dettmer steffen.dett...@gmail.com wrote

persistent-net.rules for fixed ethX names and VLANs

Hi, I have persistent-net.rules in form: SUBSYSTEM==net, KERNEL==eth* ACTION==add, ATTR{address}==40:d8:55:09:43:0f, NAME=eth3 which makes the Ethernet device with the given MAC address known as eth3, so far so good. When trying to add a VLAN using e.g.: ip link add link eth3 name eth3.77

Re: persistent-net.rules for fixed ethX names and VLANs

On Thu, Nov 14, 2013 at 4:36 PM, Steffen Dettmer steffen.dett...@gmail.com wrote: I have persistent-net.rules in form: SUBSYSTEM==net, KERNEL==eth* ACTION==add, ATTR{address}==40:d8:55:09:43:0f, NAME=eth3 How to use fixed ethX device names and VLAN devices at the same time? I found

Fwd: Questions about SIGHUP behavior

Hi, thanks for your detailed answer. On Tue, Nov 12, 2013 at 6:02 PM, David F deb...@meta-dynamic.com wrote: On 11/12/2013 07:35 AM, Steffen Dettmer wrote: Debian 7.2 with /bin/bash as login shell (via /etc/passwd), shopt huponexit off (as by default), bash run via SSH from other host

Questions about SIGHUP behavior

Hi, Debian 7.2 with /bin/bash as login shell (via /etc/passwd), shopt huponexit off (as by default), bash run via SSH from other host. When closing shell with CTRL-D, sleep continues to run. I had expected I had to use nohup, setsid, disown or a combination of them in order to keep background

How to configure udev to rename USB network cards correctly

Hi, we have USB network cards and udev rules for them, for example: SUBSYSTEM==net, ACTION==add, ATTRS{manufacturer}==Novatel Wireless*, ATTRS{serial}==?*, NAME=ethnovatel%n when booting, we see e.g., ethnovatel3 and ethnovatel4, as expected. When unplugging/replugging (or power cycling) the

Re: Passing nowait command line option to dhclient

Hi, thanks for your quick and helpful reply! On Thu, Oct 17, 2013 at 11:09 PM, Bob Proulx b...@proulx.com wrote: Steffen Dettmer wrote: Your indention is terrible! Sorry, I'll improve. I think I have to pass the option -nw to dhclient, but how do I do that correctly? If you want dhclient

Re: Configuring multiple IP addresses on VLAN interface using ifupdown

On Fri, Oct 18, 2013 at 9:40 AM, Tom H tomh0...@gmail.com wrote: On Thu, Oct 17, 2013 at 12:57 PM, Steffen Dettmer steffen.dett...@gmail.com wrote: but I get an error message that ifup tries to configure the VLAN interface twice, but the addresses are set. I assume that you mean auto eth3.77

Re: Configuring multiple IP addresses on VLAN interface using ifupdown

Hi! On Thu, Oct 17, 2013 at 11:39 PM, Bob Proulx b...@proulx.com wrote: Steffen Dettmer wrote: However all of the docs I see just now suggest using a bridge. There are docs recommending to take the burden of kernel software briding to add an alias IP?! Configuring multiple IP addresses

Re: Configuring multiple IP addresses on VLAN interface using ifupdown

On Fri, Oct 18, 2013 at 9:53 AM, Tom H tomh0...@gmail.com wrote: auto eth0 iface eth0 inet static address 10.0.5.16 netmask 255.255.255.0 iface eth0.77 inet manual auto br0.77 iface br0.77 inet manual bridge_ports eth0.77 bridge_fd 0

Re: Configuring multiple IP addresses on VLAN interface using ifupdown

Hi, thanks again for your fast help. On Fri, Oct 18, 2013 at 1:18 PM, Tom H tomh0...@gmail.com wrote: So Bob must be right about your ifupdown version not using iproute I'm using Wheezy with ifup version 0.7.8, I think this is the latest officially released (aka the best) one? and, as he

Re: Configuring multiple IP addresses on VLAN interface using ifupdown

also is wrong. For hotplug-interfaces it could be a very old PID in the file and the number could have been reused by another process (isn't it a bit unexpected to find such things in base services like ifup that are supposed to be rock-solid?). Steffen On Fri, Oct 18, 2013 at 2:05 PM, Steffen

Re: Configuring multiple IP addresses on VLAN interface using ifupdown

Hi! On Fri, Oct 18, 2013 at 3:24 PM, Tom H tomh0...@gmail.com wrote: I'm using Wheezy with ifup version 0.7.8, I think this is the latest officially released (aka the best) one? Strange. I was under the impression that Debian 7's ifupdown is using iproute but you had a vconfig error in an

Re: Configuring multiple IP addresses on VLAN interface using ifupdown

On Fri, Oct 18, 2013 at 3:24 PM, Tom H tomh0...@gmail.com wrote: ---8=== auto lo iface lo inet loopback allow-auto eth0.9 iface eth0.9 inet static address 192.168.1.119 netmask 255.255.255.0 gateway 192.168.1.1

Configuring multiple IP addresses on VLAN interface using ifupdown

Hi, I'd like to configure multiple IP addresses to a VLAN tagged interface. I tried auto eth3.107 iface eth3.77 inet static address 10.0.5.15 netmask 255.255.255.0 iface eth3.77 inet static address 10.0.5.16 netmask 255.255.255.0 but I get an error message that ifup tries to

Passing nowait command line option to dhclient

Hi, I configured several interfaces using ifupdown using DHCP by stanzas like: auto eth2 iface eth2 inet dhcp When booting and one of the DHCP interfaces has no cable attached, booting is delayed about around 60 seconds (seems to be value of dhclient.conf:timeout). I think I have to pass the