On 03/11/2023 00:58, to...@tuxteam.de wrote:
On Thu, Nov 02, 2023 at 10:41:06PM +0700, Max Nikulin wrote:
I am a bit surprised by a use case when temporary unplugging of cable should
be ignored. I have not tested it, but I hope, a setting, I have noticed in
docs, allows NetworkManager to
On Thu, Nov 02, 2023 at 10:41:06PM +0700, Max Nikulin wrote:
> On 02/11/2023 00:44, to...@tuxteam.de wrote:
> > On Wed, Nov 01, 2023 at 10:00:45PM +0700, Max Nikulin wrote:
> > >
> > > Doesn't allow-hotplug means adding a network adapter (e.g. a USB one), not
> > > plugging network cable into an
On Thu, Nov 2, 2023 at 11:41 AM Max Nikulin wrote:
> [...]
>
> I am a bit surprised by a use case when temporary unplugging of cable
> should be ignored. I have not tested it, but I hope, a setting, I have
> noticed in docs, allows NetworkManager to handle it as well.
I think it is a bit broader
On 02/11/2023 00:44, to...@tuxteam.de wrote:
On Wed, Nov 01, 2023 at 10:00:45PM +0700, Max Nikulin wrote:
Doesn't allow-hotplug means adding a network adapter (e.g. a USB one), not
plugging network cable into an existing adapter (built-in or connected
earlier)?
Following the man page
wrote:
> On Wed, Nov 01, 2023 at 10:17:16AM -0400, Felix Miata wrote:
> > to...@tuxteam.de composed on 2023-11-01 12:12 (UTC+0100):
> >
> > > More "down to the bolts" folks use ifupdown (I do). If I stick an
> > > Ethernet cable into my laptop I want to be able to say "sudo ifup
> > > eth0".
On Wed, Nov 01, 2023 at 10:00:45PM +0700, Max Nikulin wrote:
> On 01/11/2023 21:33, to...@tuxteam.de wrote:
> > I was just pointing at the fact that even ifupdown can automatically
> > bring up an interface on connect (cf. allow-hotplug), courtesy of udev.
>
> Doesn't allow-hotplug means adding a
Max Nikulin (12023-11-01):
> I am curious if ConfigureWithoutCarrier= and IgnoreCarrierLoss= from
> systemd.network(5) may help.
>
> NetworkManager has a similar option, unfortunately it may be changed
> per-device, not per-connection.
I do not have the time to test it anew. IIRC, when I tried,
On 01/11/2023 18:31, Nicolas George wrote:
systemd-networkd plus netplan. It was terrible, the network would get
de-configured if somebody pulled the ethernet cable (and that happens a
lot here!) and rebooted the machine while they were at it, and the NIS
and NFS do not appreciate it much.
I
On 01/11/2023 21:33, to...@tuxteam.de wrote:
I was just pointing at the fact that even ifupdown can automatically
bring up an interface on connect (cf. allow-hotplug), courtesy of udev.
Doesn't allow-hotplug means adding a network adapter (e.g. a USB one),
not plugging network cable into an
Il 01/11/23 15:33, to...@tuxteam.de ha scritto:
On Wed, Nov 01, 2023 at 10:17:16AM -0400, Felix Miata wrote:
to...@tuxteam.de composed on 2023-11-01 12:12 (UTC+0100):
More "down to the bolts" folks use ifupdown (I do). If I stick an Ethernet
cable into my laptop I want to be able to say
On Wed, Nov 01, 2023 at 10:17:16AM -0400, Felix Miata wrote:
> to...@tuxteam.de composed on 2023-11-01 12:12 (UTC+0100):
>
> > More "down to the bolts" folks use ifupdown (I do). If I stick an Ethernet
> > cable into my laptop I want to be able to say "sudo ifup eth0".
>
> That's more than I
to...@tuxteam.de composed on 2023-11-01 12:12 (UTC+0100):
> More "down to the bolts" folks use ifupdown (I do). If I stick an Ethernet
> cable into my laptop I want to be able to say "sudo ifup eth0".
That's more than I need to do. systemd-networkd.socket notices and appropriately
responds to
On Wed, 1 Nov 2023 12:19:47 +0100
"Marco M." wrote:
> Am 01.11.2023 um 11:43:32 Uhr schrieb Alessandro Baggi:
>
> > I've read on an old email that many don't use NM for network
> > configuration. I'm using it because I replaced some CentOS
> > installation with Debian 12.
> >
> > What is the
Greg Wooledge (12023-11-01):
> ALL installations of ALL versions of Debian support "ifupdown", also
> known as /etc/network/interfaces, for configuring the network. If
> your system is NOT a laptop, and doesn't move around from place to
> place, this is probably what you want.
>
> Servers?
Am 01.11.2023 um 11:43:32 Uhr schrieb Alessandro Baggi:
> I've read on an old email that many don't use NM for network
> configuration. I'm using it because I replaced some CentOS
> installation with Debian 12.
>
> What is the default method to configure the network?
Desktop environments use
On Wed, Nov 01, 2023 at 11:43:32AM +0100, Alessandro Baggi wrote:
> I've read on an old email that many don't use NM for network configuration.
> I'm using it because I replaced some CentOS installation with Debian 12.
>
> What is the default method to configure the network?
Depends on how you
On Wed, Nov 01, 2023 at 01:10:22PM +0200, y...@vienna.at wrote:
> On Wed, 1 Nov 2023 11:43:32 +0100
> Alessandro Baggi wrote:
> > Hi list,
[...]
> With SystemD instead of SysV and ip of Kusnetsow and iproute2 with Baturin
> you should do it by yourselve.
See? Yet another choice (I can't vouch
On Wed, Nov 01, 2023 at 11:43:32AM +0100, Alessandro Baggi wrote:
> Hi list,
> I've read on an old email that many don't use NM for network configuration.
> I'm using it because I replaced some CentOS installation with Debian 12.
[...]
I don't know how the actual numbers are. I'd guess that
On Wed, 1 Nov 2023 11:43:32 +0100
Alessandro Baggi wrote:
Hi list,
I've read on an old email that many don't use NM for network
configuration. I'm using it because I replaced some CentOS
installation with Debian 12.
What is the default method to configure the network?
There is an
Hi list,
I've read on an old email that many don't use NM for network
configuration. I'm using it because I replaced some CentOS installation
with Debian 12.
What is the default method to configure the network?
There is an alternative to NM on Debian 12?
Thank you in advance.
Alessandro.
20 matches
Mail list logo
