On Thursday 17 December 2020 at 13:03:57, rattenkopf via Dng wrote:
> hi Antony
>
> Yesterday I had the same problem - mainboard network interface gets eth1
> as name and the both interfaces from the pci-card are eth0 and eth2 and
> fiddling with udef-rule didn't get the wanted result.
Indeed -
hi Antony
Yesterday I had the same problem - mainboard network interface gets eth1
as name and the both interfaces from the pci-card are eth0 and eth2 and
fiddling with udef-rule didn't get the wanted result.
But I notice, that as system booted from an usb stick dos not have this
problem, but the
On Sun, Dec 13, 2020 at 10:15:26PM +0100, Antony Stone wrote:
> On Sunday 13 December 2020 at 21:13:10, d...@d404.nl wrote:
>
> > It looks like systemd again is responsible for this mess.
>
> That is unexpected for me, since I am starting from a clean installation of
> Devuan Beowulf - no upgrad
On Sun, 13 Dec 2020 14:20:25 +0100
Antony Stone wrote:
> On Sunday 13 December 2020 at 13:02:45, Florian Zieboll via Dng wrote:
>
> > Am 13. Dezember 2020 12:01:39 MEZ schrieb Antony Stone
> :
> > > Well, here's the output from "dmesg | grep eth". It shows the
> > > r8169 interfaces being gi
On Sun, 13 Dec 2020 10:45:56 +0100
Antony Stone wrote:
> On Sunday 13 December 2020 at 09:25:24, terryc wrote:
>
> > Just add the line
> > hwaddress mac:add:dress:in:usual:format
> >
> > to match eth2 & eth3 to the desired card.
>
> I think that's entirely the wrong way round.
>
> Sett
On 13/12 22:22, Antony Stone wrote:
> On Sunday 13 December 2020 at 21:42:50, Simon Hobson wrote:
>
> > Hendrik Boom wrote:
> > > I had to solve it by assigning new names to the interfaces (thus not eth0
> > > or eth1) and modifying all the config files mentioning those interface
> > > names (I f
On Sunday 13 December 2020 at 21:42:50, Simon Hobson wrote:
> Hendrik Boom wrote:
> > I had to solve it by assigning new names to the interfaces (thus not eth0
> > or eth1) and modifying all the config files mentioning those interface
> > names (I found them with grep) to use the new names instea
On Sunday 13 December 2020 at 21:13:10, d...@d404.nl wrote:
> It looks like systemd again is responsible for this mess.
That is unexpected for me, since I am starting from a clean installation of
Devuan Beowulf - no upgrade, no crossover from Debian - just a totally new
install of Devuan (which
Hendrik Boom wrote:
> I had to solve it by assigning new names to the interfaces (thus not eth0 or
> eth1) and modifying all the config files mentioning those interface names (I
> found them with grep) to use the new names instead.
Not for the OPs reason, but a long time ago I started to use "
Le 13/12/2020 à 01:09, Ralph Ronnquist via Dng a écrit :
> On 13/12 00:40, Antony Stone wrote:
>>> If it worked for you previously then, a) there would have been rules
>>> for double renaming,
>> Please point me at where I should find these.
>>
>> I only know that /etc/udev/rules.d/70-persistent-ne
On 13-12-2020 14:20, Antony Stone wrote:
> On Sunday 13 December 2020 at 13:02:45, Florian Zieboll via Dng wrote:
>
>> Am 13. Dezember 2020 12:01:39 MEZ schrieb Antony Stone
> :
>>> Well, here's the output from "dmesg | grep eth". It shows the r8169
>>> interfaces being given names eth0, eth1 (th
Le 13/12/2020 à 00:01, Ralph Ronnquist via Dng a écrit :
> On 12/12 23:22, Antony Stone wrote:
>> On Saturday 12 December 2020 at 23:11:25, Ralph Ronnquist via Dng wrote:
>> ...
>>
>> 1. Why is this so totally different from what I could previously do using
>> /etc/udev/rules.d/70-persistent-net.r
On Sunday 13 December 2020 at 14:25:37, tito via Dng wrote:
> On Sun, 13 Dec 2020 10:45:56 +0100 Antony Stone wrote:
> >
> > From Ascii onwards I get the errors:
> >
> > udevd[441]: Error changing net interface name eth2 to eth0: File
> > exists udevd[441]: could not rename interface '4' from 'e
On Sun, 13 Dec 2020 14:25:37 +0100
tito via Dng wrote:
> On Sun, 13 Dec 2020 10:45:56 +0100
> Antony Stone wrote:
>
> > On Sunday 13 December 2020 at 09:25:24, terryc wrote:
> >
> > > On Sat, 12 Dec 2020 14:15:53 +0100
> > >
> > > Antony Stone wrote:
> > > > Hi.
> > > >
> > > > I've just in
On Sun, 13 Dec 2020 10:45:56 +0100
Antony Stone wrote:
> On Sunday 13 December 2020 at 09:25:24, terryc wrote:
>
> > On Sat, 12 Dec 2020 14:15:53 +0100
> >
> > Antony Stone wrote:
> > > Hi.
> > >
> > > I've just installed a couple of Beowulf systems, each of which has
> > > three ethernet int
On Sunday 13 December 2020 at 13:02:45, Florian Zieboll via Dng wrote:
> Am 13. Dezember 2020 12:01:39 MEZ schrieb Antony Stone
:
> > Well, here's the output from "dmesg | grep eth". It shows the r8169
> > interfaces being given names eth0, eth1 (the ones I want as eth1 and
> > eth2), then the t
Am 13. Dezember 2020 12:01:39 MEZ schrieb Antony Stone
:
> Well, here's the output from "dmesg | grep eth". It shows the r8169
> interfaces being given names eth0, eth1 (the ones I want as eth1 and eth2),
> then the tg3 interface gets called eth2 (which I want as eth0).
>
> At 6 seconds in, y
On Sunday 13 December 2020 at 11:23:21, Florian Zieboll via Dng wrote:
> Am 13. Dezember 2020 10:45:56 MEZ schrieb Antony Stone:
> > From Ascii onwards I get the errors:
> >
> > udevd[441]: Error changing net interface name eth2 to eth0: File exists
> > udevd[441]: could not rename interface '4'
Am 13. Dezember 2020 10:45:56 MEZ schrieb Antony Stone
:
> From Ascii onwards I get the errors:
>
> udevd[441]: Error changing net interface name eth2 to eth0: File exists
> udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File exists
>
> and so on.
Does the bootlog give a hi
On Sunday 13 December 2020 at 09:25:24, terryc wrote:
> On Sat, 12 Dec 2020 14:15:53 +0100
>
> Antony Stone wrote:
> > Hi.
> >
> > I've just installed a couple of Beowulf systems, each of which has
> > three ethernet interfaces; one on the motherboard, and two on a PCI
> > card.
> >
> > I'm tr
On Sat, 12 Dec 2020 14:15:53 +0100
Antony Stone wrote:
> Hi.
>
> I've just installed a couple of Beowulf systems, each of which has
> three ethernet interfaces; one on the motherboard, and two on a PCI
> card.
>
> I'm trying to work out how to give those interfaces the names I want;
> the mothe
On Sat, 12 Dec 2020 16:06:03 +0100
Antony Stone wrote:
> On Saturday 12 December 2020 at 15:27:08, d...@d404.nl wrote:
>
> > On 12-12-2020 14:15, Antony Stone wrote:
> > >
> > > According to https://wiki.debian.org/NetworkInterfaceNames the
> > > old 70- persistent-net.rules system _should_ s
On 13/12 02:47, Antony Stone wrote:
> On Sunday 13 December 2020 at 01:09:18, Ralph Ronnquist via Dng wrote:
>
> > Well, the kernel modules makes the first naming, and assigns them as
> > eth0, eth1, eth2. That happens before udev starts.
> >
> > The kernel refuses any attempt to name an interfac
On Sunday 13 December 2020 at 01:09:18, Ralph Ronnquist via Dng wrote:
> Well, the kernel modules makes the first naming, and assigns them as
> eth0, eth1, eth2. That happens before udev starts.
>
> The kernel refuses any attempt to name an interface to, say, eth0 if
> that name is taken.
>
> Th
On 13/12 00:40, Antony Stone wrote:
> > If it worked for you previously then, a) there would have been rules
> > for double renaming,
>
> Please point me at where I should find these.
>
> I only know that /etc/udev/rules.d/70-persistent-net.rules was the
> *only* file I needed to edit if I wanted
On Sat, 12 Dec 2020 23:11:52 +0100
Antony Stone wrote:
> On Saturday 12 December 2020 at 14:15:53, Antony Stone wrote:
>
> > Historically, I've been used to udev
> > and /etc/udev/rules.d/70-persistent- net.rules doing this, where I
> > can specify the name I want for each interface according to
On Sunday 13 December 2020 at 00:01:06, Ralph Ronnquist via Dng wrote:
> On 12/12 23:22, Antony Stone wrote:
> >
> > 1. Why is this so totally different from what I could previously do using
> > /etc/udev/rules.d/70-persistent-net.rules under jessie and earlier
> > releases?
>
> If it worked for
On Sunday 13 December 2020 at 00:01:11, Florian Zieboll via Dng wrote:
> On Sat, 12 Dec 2020 23:11:52 +0100 Antony Stone wrote:
> > I would still *really like* to know:
> >
> > 1. how can I get 70-persistent-net.rules to carry on working as it
> > used to, under Beowulf? (I never had to do this
On Sat, 12 Dec 2020 23:11:52 +0100
Antony Stone wrote:
> I would still *really like* to know:
>
> 1. how can I get 70-persistent-net.rules to carry on working as it
> used to, under Beowulf? (I never had to do this sort of workaround
> in Jessie or before.)
Hallo Antony,
do I understand corr
On 12/12 23:22, Antony Stone wrote:
> On Saturday 12 December 2020 at 23:11:25, Ralph Ronnquist via Dng wrote:
> ...
>
> 1. Why is this so totally different from what I could previously do using
> /etc/udev/rules.d/70-persistent-net.rules under jessie and earlier releases?
>
> 2. https://wiki.de
On Saturday 12 December 2020 at 23:11:25, Ralph Ronnquist via Dng wrote:
> It really isn't that hard:
>
> when the kernel starts it will give its default names to the
> interfaces as ethN numbering them in order it initializes them. In
> your case it will use the names eth0, eth1 and eth2 that ge
On Saturday 12 December 2020 at 14:15:53, Antony Stone wrote:
> Historically, I've been used to udev and /etc/udev/rules.d/70-persistent-
> net.rules doing this, where I can specify the name I want for each
> interface according to its MAC address.
> 1. how can I get 70-persistent-net.rules to ca
It really isn't that hard:
when the kernel starts it will give its default names to the
interfaces as ethN numbering them in order it initializes them. In
your case it will use the names eth0, eth1 and eth2 that get assigned
in whatever time order the kernel discovers them in.
Eventually(!) the h
On Sat, Dec 12, 2020 at 02:15:53PM +0100, Antony Stone wrote:
> Hi.
>
> I've just installed a couple of Beowulf systems, each of which has three
> ethernet interfaces; one on the motherboard, and two on a PCI card.
>
> I'm trying to work out how to give those interfaces the names I want; the
>
On Saturday 12 December 2020 at 16:28:04, Didier Kryn wrote:
> Le 12/12/2020 à 14:15, Antony Stone a écrit :
> >
> > 1. how can I get 70-persistent-net.rules to carry on working under
> > Beowulf?
> >
> > 2. what's the "correct" way to get my interfaces named the way I want,
> > according to the
Le 12/12/2020 à 14:15, Antony Stone a écrit :
> Hi.
>
> I've just installed a couple of Beowulf systems, each of which has three
> ethernet interfaces; one on the motherboard, and two on a PCI card.
>
> I'm trying to work out how to give those interfaces the names I want; the
> motherboard as eth
On Saturday 12 December 2020 at 16:06:29, tito via Dng wrote:
> On Sat, 12 Dec 2020 14:15:53 +0100 Antony Stone wrote:
> > Historically, I've been used to udev
> > and /etc/udev/rules.d/70-persistent- net.rules doing this, where I
> > can specify the name I want for each interface according to its
On Sat, 12 Dec 2020 14:15:53 +0100
Antony Stone wrote:
> Hi.
>
> I've just installed a couple of Beowulf systems, each of which has
> three ethernet interfaces; one on the motherboard, and two on a PCI
> card.
>
> I'm trying to work out how to give those interfaces the names I want;
> the mothe
On Saturday 12 December 2020 at 15:27:08, d...@d404.nl wrote:
> On 12-12-2020 14:15, Antony Stone wrote:
> >
> > According to https://wiki.debian.org/NetworkInterfaceNames the old 70-
> > persistent-net.rules system _should_ still work in Buster / Beowulf, but
> > I can't work out how to get it t
On 12-12-2020 14:15, Antony Stone wrote:
> Hi.
>
> I've just installed a couple of Beowulf systems, each of which has three
> ethernet interfaces; one on the motherboard, and two on a PCI card.
>
> I'm trying to work out how to give those interfaces the names I want; the
> motherboard as eth0, an
Hi.
I've just installed a couple of Beowulf systems, each of which has three
ethernet interfaces; one on the motherboard, and two on a PCI card.
I'm trying to work out how to give those interfaces the names I want; the
motherboard as eth0, and the PCI card as eth1 / eth2.
Historically, I've be
41 matches
Mail list logo
