On Ma, 31 aug 21, 16:33:49, Reco wrote:
> On Tue, Aug 31, 2021 at 01:32:32PM +0300, Andrei POPESCU wrote:
> >
> > Another completely different approach is to use some other tool to
> > configure your network that can match on MAC address and just ignore the
> > names completely.
>
> Surely you
On Mon, 2021-08-30 at 20:26 -0400, Greg Wooledge wrote:
> On Tue, Aug 31, 2021 at 01:44:09AM +0200, Steve Keller wrote:
[...]
> > Actually, I don't know this. When I wrote unpredictable new naming
> > scheme I meant systemd's enps scheme, since it's
> > unpredictable for me as long as I don't lear
On Tue 31 Aug 2021 at 01:11:33 (+0200), Steve Keller wrote:
> Greg Wooledge writes:
> > On Mon, Aug 30, 2021 at 04:41:55PM -0400, Dan Ritter wrote:
> > > Steve Keller wrote:
> > > > I plan to upgrade a server from Debian stretch to buster. Having read
> > > > the release notes I wonder what's the
On Tue, Aug 31, 2021 at 01:32:32PM +0300, Andrei POPESCU wrote:
> On Lu, 30 aug 21, 16:41:39, Greg Wooledge wrote:
> > On Mon, Aug 30, 2021 at 10:20:46PM +0200, Steve Keller wrote:
> > > I plan to upgrade a server from Debian stretch to buster. Having read
> > > the release notes I wonder what's
On 30/08/2021 23:20, Steve Keller wrote:
't want to have to remember this hardware
configurationan and I don't want to type these cumbersome and error
prone names. I simply have eth0 for the internal network and eth1 for
my external network to the DSL router. That's easy and I want to keep
it
On Tue, Aug 31, 2021 at 01:32:32PM +0300, Andrei POPESCU wrote:
> Another completely different approach is to use some other tool to
> configure your network that can match on MAC address and just ignore the
> names completely.
>
> For systemd-networkd
>
> /etc/systemd/network/my.network
>
> [
On Lu, 30 aug 21, 16:41:39, Greg Wooledge wrote:
> On Mon, Aug 30, 2021 at 10:20:46PM +0200, Steve Keller wrote:
> > I plan to upgrade a server from Debian stretch to buster. Having read
> > the release notes I wonder what's the best way to avoid the new scheme
> > of unpredictable network int
On Ma, 31 aug 21, 01:11:33, Steve Keller wrote:
>
> I still don't understand, why eth in
> a systemd.link file would be a problem, since in the udev .rules this
> has worked for years.
Greg already explained what problems might show up if you try to use
eth.
The ud
On Tue, Aug 31, 2021 at 01:11:33AM +0200, Steve Keller wrote:
[...]
> OK, several people suggested the kernel command-line option
> net.ifnames=0. Since I almost never change hardware configurations
> this is probably OK even with my two NICs, one on the mainboard, the
> second is a PCI card. I
On Tue, Aug 31, 2021 at 01:44:09AM +0200, Steve Keller wrote:
> One interface is on the mainboard (eth0), the other is a PCI card
> (eth1). BTW, PCI really, not PCIe other something like that. It's a
> really old machine.
OK. I recommend making two "dot link" files, one for each card, in
order
Roberto C. Sánchez writes:
> Since nobody else has mentioned this link, here is where I recommend you
> start: https://wiki.debian.org/NetworkInterfaceNames
Oh, that's what I meant by "wiki" in my posts. Sorry, I should have
given the URL. It's linked from the buster release-notes in section
5
Greg Wooledge writes:
> On Tue, Aug 31, 2021 at 12:27:57AM +0300, IL Ka wrote:
> > >
> > > This gives unpredictable results if the system has more than one
> > > ethernet interface, or more than one wireless interface.
> > >
> > > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
Greg Wooledge writes:
> On Mon, Aug 30, 2021 at 04:41:55PM -0400, Dan Ritter wrote:
> > Steve Keller wrote:
> > > I plan to upgrade a server from Debian stretch to buster. Having read
> > > the release notes I wonder what's the best way to avoid the new scheme
> > > of unpredictable network in
On Mon, Aug 30, 2021 at 10:20:46PM +0200, Steve Keller wrote:
> I plan to upgrade a server from Debian stretch to buster. Having read
> the release notes I wonder what's the best way to avoid the new scheme
> of unpredictable network interface names.
>
> I don't care what PCI bus and
IL Ka schrieb:
> > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
>
> Isn't that what the topic starter asked about?:)
I don't think so:
| I simply have eth0 for the internal network and eth1 for
| my external network to the DSL router.
That looks like two ethernet NICs.
On Tue, Aug 31, 2021 at 12:27:57AM +0300, IL Ka wrote:
> >
> > This gives unpredictable results if the system has more than one
> > ethernet interface, or more than one wireless interface.
> >
> > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
> >
>
> Isn't that what the topic
>
> This gives unpredictable results if the system has more than one
> ethernet interface, or more than one wireless interface.
>
> It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
>
Isn't that what the topic starter asked about?:)
To make names predictable one can either leave
Dan Ritter wrote:
> Steve Keller wrote:
> > I plan to upgrade a server from Debian stretch to buster. Having read
> > the release notes I wonder what's the best way to avoid the new scheme
> > of unpredictable network interface names.
>
> In /etc/default/grub, assuming that you are booting
On Mon, Aug 30, 2021 at 11:36 PM Steve Keller wrote:
> So I'm still confused what to do after the upgrade to buster to keep
> my network names.
>
>
>
in /etc/default/grub add
"net.ifnames=0"
to GRUB_CMDLINE_LINUX
and execute "update-grub"
This service:
https://www.freedesktop.org/software/system
On Mon, Aug 30, 2021 at 04:41:55PM -0400, Dan Ritter wrote:
> Steve Keller wrote:
> > I plan to upgrade a server from Debian stretch to buster. Having read
> > the release notes I wonder what's the best way to avoid the new scheme
> > of unpredictable network interface names.
>
> In /etc/def
Steve Keller wrote:
> I plan to upgrade a server from Debian stretch to buster. Having read
> the release notes I wonder what's the best way to avoid the new scheme
> of unpredictable network interface names.
In /etc/default/grub, assuming that you are booting with grub,
GRUB_CMDLINE_LIN
On Mon, Aug 30, 2021 at 10:20:46PM +0200, Steve Keller wrote:
> I plan to upgrade a server from Debian stretch to buster. Having read
> the release notes I wonder what's the best way to avoid the new scheme
> of unpredictable network interface names.
You say "server", so I'm guessing it has
I plan to upgrade a server from Debian stretch to buster. Having read
the release notes I wonder what's the best way to avoid the new scheme
of unpredictable network interface names.
I don't care what PCI bus and what slot my NICs are attached to, I
don't want to learn and don't want to have to r
23 matches
Mail list logo
