Steve Litt wrote:
> The vast majority of documents I've read tell me that once you make the
> bridge, the hardware NIC must be robbed of its IP addresses. So that's
> what I did.
That is the correct way to do it - though from memory it does seem to still
work for host-LAN communications if you
>Le 02/03/2021 à 12:48, Steve Litt a écrit :
>> Hi all,
>>
>> As you know, I was asking many Qemu LAN-peer questions on this list a
>> week ago. My documentation on the subject has finally achieved
>> first-draft status. If you'd like to see it, go to:
>>
>>
Le 02/03/2021 à 12:48, Steve Litt a écrit :
> Hi all,
>
> As you know, I was asking many Qemu LAN-peer questions on this list a
> week ago. My documentation on the subject has finally achieved
> first-draft status. If you'd like to see it, go to:
>
> http://troubleshooters.com/linux/qemu/nobs.htm
Fri, 5 Mar 2021 18:56:25 + - Simon Hobson :
> Florian Zieboll via Dng wrote:
>
> > For the sake of completeness and y'all's convenience, here a link to
> > the related info in the Debianwiki:
> >
> > https://wiki.debian.org/NetworkInterfaceNames
[quote]
* UNPREDICTABILITY
it turns
>On Fri, 5 Mar 2021 18:56:25 +
>Simon Hobson wrote:
>
>> Florian Zieboll via Dng wrote:
>>
>> > For the sake of completeness and y'all's convenience, here a link
>> > to the related info in the Debianwiki:
>> >
>> > https://wiki.debian.org/NetworkInterfaceNames
>>
>> Did anyone else
On Fri, 5 Mar 2021 18:56:25 +
Simon Hobson wrote:
> Florian Zieboll via Dng wrote:
>
> > For the sake of completeness and y'all's convenience, here a link
> > to the related info in the Debianwiki:
> >
> > https://wiki.debian.org/NetworkInterfaceNames
>
> Did anyone else read that and
Florian Zieboll via Dng wrote:
> For the sake of completeness and y'all's convenience, here a link to the
> related info in the Debianwiki:
>
> https://wiki.debian.org/NetworkInterfaceNames
Did anyone else read that and think it could be summarised along the lines of :
"We thought X was badly
Le 05/03/2021 à 07:48, tito via Dng a écrit :
> On Thu, 4 Mar 2021 19:38:49 -0500
> Steve Litt wrote:
>
>>> On Wed, 03 Mar 2021 21:44:30 +
>>> g4sra via Dng wrote:
>>> In my young years I used to tinker with linux distros on floppy
>>> disks and there still where eth0, eth1 and so on but no
On Thu, 4 Mar 2021 19:38:49 -0500
Steve Litt wrote:
>
> >On Wed, 03 Mar 2021 21:44:30 +
> >g4sra via Dng wrote:
>
> >In my young years I used to tinker with linux distros on floppy
> >disks and there still where eth0, eth1 and so on but no udev,
> >so where did the names came from?
>
>
>On Wed, 03 Mar 2021 21:44:30 +
>g4sra via Dng wrote:
>In my young years I used to tinker with linux distros on floppy
>disks and there still where eth0, eth1 and so on but no udev,
>so where did the names came from?
Ya know, mknod wasn't so bad. The moment inotify was invented, I could
On Thu, 4 Mar 2021 11:02:08 +0100
Didier Kryn wrote:
> Le 04/03/2021 à 07:46, tito via Dng a écrit :
> > How Linux assigns network interface names
> > The default name for Ethernet interfaces is based upon how Linux
> > initializes them during device discovery. As Linux finds the network
> >
Quoting Steve Litt (sl...@troubleshooters.com):
> As you know, I was asking many Qemu LAN-peer questions on this list a
> week ago. My documentation on the subject has finally achieved
> first-draft status. If you'd like to see it, go to:
>
> http://troubleshooters.com/linux/qemu/nobs.htm
This
On Thu, 4 Mar 2021 07:24:50 +0100
aitor wrote:
> Hi tito,
>
> On 4/3/21 0:47, tito via Dng wrote:
> > In my young years I used to tinker with linux distros on floppy
> > disks and there still where eth0, eth1 and so on but no udev,
> > so where did the names came from?
>
> They were assigned
Hi tito,
On 4/3/21 0:47, tito via Dng wrote:
In my young years I used to tinker with linux distros on floppy
disks and there still where eth0, eth1 and so on but no udev,
so where did the names came from?
They were assigned by the kernel, i think.
Aitor.
On Wed, 03 Mar 2021 21:44:30 +
g4sra via Dng wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, March 3, 2021 7:54 PM, tito via Dng
> wrote:
>
> > On Wed, 03 Mar 2021 16:15:10 +
> > g4sra via Dng dng@lists.dyne.org wrote:
> >
>
>
> > >
>
> > > Your 'predictable' names name
‐‐‐ Original Message ‐‐‐
On Wednesday, March 3, 2021 7:54 PM, tito via Dng wrote:
> On Wed, 03 Mar 2021 16:15:10 +
> g4sra via Dng dng@lists.dyne.org wrote:
>
> >
> > Your 'predictable' names name are being assigned by what ?
>
> By the kernel, I suppose as you can pass a
On Wed, 03 Mar 2021 16:15:10 +
g4sra via Dng wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, March 3, 2021 3:21 PM, tito via Dng
> wrote:
>
> > On Wed, 03 Mar 2021 14:52:57 +
> > g4sra via Dng dng@lists.dyne.org wrote:
> >
>
> > > <-- huge snip -->
> > > Just for
‐‐‐ Original Message ‐‐‐
On Wednesday, March 3, 2021 3:21 PM, tito via Dng wrote:
> On Wed, 03 Mar 2021 14:52:57 +
> g4sra via Dng dng@lists.dyne.org wrote:
>
> > <-- huge snip -->
> > Just for completeness should someone dig this thread up trying to
> > solve an issue...such as a
On Wed, 03 Mar 2021 14:52:57 +
g4sra via Dng wrote:
> <-- huge snip -->
>
> Just for completeness should someone dig this thread up trying to
> solve an issue...such as a 12 port router
>
> The kernel's FDT determines the order of detection for built-in
> interfaces. Learn how to make
<-- huge snip -->
Just for completeness should someone dig this thread up trying to solve an
issue...such as a 12 port router
The kernel's FDT determines the order of detection for built-in interfaces.
Learn how to make them, then don't change it and the interfaces will always
come up the
On Wed, 3 Mar 2021 15:07:14 +0100
John Hughes wrote:
> On 03/03/2021 14:01, tito wrote:
> > On Wed, 3 Mar 2021 10:16:13 +0100
> > John Hughes wrote:
> >
> >> On 02/03/2021 15:57, tito via Dng wrote:
> >>> I would add that renaming of multiple cards/ports works
> >>> only if you rename all of
Le 03/03/2021 à 14:18, Antony Stone a écrit :
> I agree that "eth0" is less stupid than "enp0s0p1" etc., however I too like
> the use of descriptive names such as "CableModem", "Clients", "Servers" etc.
In case people like ethX names, which is my case, I just came with
the idea to use
On Wednesday 03 March 2021 at 14:03:46, tito via Dng wrote:
> On Wed, 3 Mar 2021 10:16:13 +0100 John Hughes wrote:
> >
> > Just avoid the "ethX" names (because of race conditions and because
> > they're stupid). Use something descriptive.
>
> they are less stupid than enp0s0p1 or the like and
On Wed, 3 Mar 2021 10:40:20 +0100
Florian Zieboll via Dng wrote:
> On Wed, 3 Mar 2021 08:04:19 +0100
> tito via Dng wrote:
>
> > you can set the device names by MAC addresses at boot
> > and in the past it worked as udev/eudev net-persisent-name.rules
> > (but seems to be broken, optimized out
On Wed, 3 Mar 2021 10:16:13 +0100
John Hughes wrote:
> On 02/03/2021 15:57, tito via Dng wrote:
> > I would add that renaming of multiple cards/ports works
> > only if you rename all of them to a different intermediate name
> > and then back to wanted name and order otherwise renaming
> > can
On Wed, 3 Mar 2021 12:13:04 +0100
Florian Zieboll via Dng wrote:
> Sure, it is more error prone to work with enx"$mac" NIC names, but as
> it's probably too late for complaining, I just made my router "future
> proof":
>
> backup /etc/:
> $ cp -a /etc /etc.bkp
>
> cd to /etc/:
> $ cd /etc/
>
On Wed, 3 Mar 2021 10:49:19 +0100
Antony Stone wrote:
> On Wednesday 03 March 2021 at 10:40:20, Florian Zieboll via Dng wrote:
>
> > On Wed, 3 Mar 2021 08:04:19 +0100
> >
> > tito via Dng wrote:
> > > you can set the device names by MAC addresses at boot
> > > and in the past it worked as
On Wednesday 03 March 2021 at 10:40:20, Florian Zieboll via Dng wrote:
> On Wed, 3 Mar 2021 08:04:19 +0100
>
> tito via Dng wrote:
> > you can set the device names by MAC addresses at boot
> > and in the past it worked as udev/eudev net-persisent-name.rules
> > (but seems to be broken,
On Wed, 3 Mar 2021 08:04:19 +0100
tito via Dng wrote:
> you can set the device names by MAC addresses at boot
> and in the past it worked as udev/eudev net-persisent-name.rules
> (but seems to be broken, optimized out nowadays).
Thanks, Tito, for the clue! I am using udev (resp. eudev) rules
Of course the code was wrong; I've corrected it below...
On 03/03 19:24, Ralph Ronnquist wrote:
> On 03/03 01:06, Steve Litt wrote:
> >
> > Am I hearing correctly when I think you two are saying I can make
> > multiple network devices have determinate names (even if I don't select
> > those
On 03/03 01:06, Steve Litt wrote:
>
> Am I hearing correctly when I think you two are saying I can make
> multiple network devices have determinate names (even if I don't select
> those names) by doing something with their MAC addresses? If so, how do
> I do it?
Since you do networking setup via
Le 03/03/2021 à 08:04, tito via Dng a écrit :
>> Am I hearing correctly when I think you two are saying I can make
>> multiple network devices have determinate names (even if I don't
>> select those names) by doing something with their MAC addresses? If
>> so, how do I do it?
>>
>> SteveT
>>
>>
On Wed, 3 Mar 2021 01:06:55 -0500
Steve Litt wrote:
>
> On Wed, 3 Mar 2021 13:06:45 +1100
> Ralph Ronnquist via Dng wrote:
>
> > On 03/03 00:19, g4sra via Dng wrote:
> > > ‐‐‐ Original Message ‐‐‐
> > > On Wednesday, March 3, 2021 12:15 AM, spiralofhope
> > > wrote:
> > > > On Wed,
On Wed, 3 Mar 2021 13:06:45 +1100
Ralph Ronnquist via Dng wrote:
> On 03/03 00:19, g4sra via Dng wrote:
> > ‐‐‐ Original Message ‐‐‐
> > On Wednesday, March 3, 2021 12:15 AM, spiralofhope
> > wrote:
> > > On Wed, 3 Mar 2021 01:34:40 +1100
> > > Ralph Ronnquist via Dng
On 03/03 00:19, g4sra via Dng wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, March 3, 2021 12:15 AM, spiralofhope
> wrote:
>
> > On Wed, 3 Mar 2021 01:34:40 +1100
> > Ralph Ronnquist via Dng dng@lists.dyne.org wrote:
> > > For bare-metal hardware I believe there is a first possible
‐‐‐ Original Message ‐‐‐
On Wednesday, March 3, 2021 12:15 AM, spiralofhope
wrote:
> On Wed, 3 Mar 2021 01:34:40 +1100
> Ralph Ronnquist via Dng dng@lists.dyne.org wrote:
>
> > For bare-metal hardware I believe there is a first possible "race"
> > between different modules (that
On Wed, 3 Mar 2021 01:34:40 +1100
Ralph Ronnquist via Dng wrote:
> For bare-metal hardware I believe there is a first possible "race"
> between different modules (that handle different card types), and a
> second possible "race" for multiple same-type cards, which are handled
> by the one and
On Wed, 3 Mar 2021 01:34:40 +1100
Ralph Ronnquist via Dng wrote:
> On 02/03 14:29, tito wrote:
> > On Wed, 3 Mar 2021 00:06:27 +1100
> > Ralph Ronnquist via Dng wrote:
> >
> > > On 02/03 06:48, Steve Litt wrote:
> > > > Hi all,
> > > >
> > > > As you know, I was asking many Qemu LAN-peer
On 02/03 14:29, tito wrote:
> On Wed, 3 Mar 2021 00:06:27 +1100
> Ralph Ronnquist via Dng wrote:
>
> > On 02/03 06:48, Steve Litt wrote:
> > > Hi all,
> > >
> > > As you know, I was asking many Qemu LAN-peer questions on this list
> > > a week ago. My documentation on the subject has finally
On Wed, 3 Mar 2021 00:06:27 +1100
Ralph Ronnquist via Dng wrote:
> On 02/03 06:48, Steve Litt wrote:
> > Hi all,
> >
> > As you know, I was asking many Qemu LAN-peer questions on this list
> > a week ago. My documentation on the subject has finally achieved
> > first-draft status. If you'd like
On 02/03 06:48, Steve Litt wrote:
> Hi all,
>
> As you know, I was asking many Qemu LAN-peer questions on this list a
> week ago. My documentation on the subject has finally achieved
> first-draft status. If you'd like to see it, go to:
>
> http://troubleshooters.com/linux/qemu/nobs.htm
Thank
Hi all,
As you know, I was asking many Qemu LAN-peer questions on this list a
week ago. My documentation on the subject has finally achieved
first-draft status. If you'd like to see it, go to:
http://troubleshooters.com/linux/qemu/nobs.htm
SteveT
Steve Litt
Autumn 2020 featured book: Thriving
42 matches
Mail list logo
