On Fri 01 Sep 2023 at 21:31:39 (+0100), Brad Rogers wrote:
> On Fri, 1 Sep 2023 14:02:31 -0600 D. R. Evans wrote:
>
> >So how do I fix this so that the networking is configured to work
> >correctly during the boot sequence, as it has always done before?
>
> I had changing ethernet port issues and
On Fri, 1 Sep 2023 18:33:51 -0400
Greg Wooledge wrote:
...
> Standard installation. But as you noted, it's optional. Debian *also*
> allows the use of Network Manager, systemd-networkd, and probably several
> other systems for configuring one's network(s).
Yes - I use iwd for basic (wireless)
On 02/09/2023 13:09, Brad Rogers wrote:
On Sat, 2 Sep 2023 12:08:37 +0100
Brian wrote:
Hello Brian,
I did not write any of the text you quote.
You did, but it was not what Timothy was responding to.
What you wrote was quoted right at the bottom of the message, and
irrelevant to Timothy's
On 2023-09-02, Brian wrote:
> On Sat 02 Sep 2023 at 19:37:22 +0100, Brian wrote:
>
>> On Sat 02 Sep 2023 at 08:19:56 -0600, D. R. Evans wrote:
>>
>> [...]
>>
>> > I will file a bug report.
>>
>> You have filed the report against general. This is a non-optimal
>> package. Someone may or may not
On Fri 01 Sep 2023 at 21:57:39 (-0400), Greg Wooledge wrote:
> On Fri, Sep 01, 2023 at 08:40:43PM -0500, David Wright wrote:
> > I know you have a low opinion of allow-hotplug, but I can't see that
> > auto/allow-auto is necessarily better for the naive user that doesn't
> > install a DE for whatev
On Sat 02 Sep 2023 at 08:19:56 (-0600), D. R. Evans wrote:
> Starting a new thread so that this doesn't get lost in the postings in
> the original thread.
>
> The original thread was started at:
> https://lists.debian.org/debian-user/2023/09/msg00024.html
>
> That post contains a description of
Brian wrote on 9/2/23 04:51:
Installation over ethernet, no DE - ifupdown provided.
Installation over ethernet or wireless with a DE - network-manager provided.
Yep, that one's exactly what I experienced.
Although the machine is used more like a server than a desktop, it has DE
(KDE) to make
Brian wrote on 9/2/23 13:01:
Send a mail to
cont...@bugs.debian.org
Ib the mail body put
ressign 1051086 installation-report
thanks
Sorry. That's "reassign".
Done. Thank you.
I pondered where to assign in, and couldn't see anywhere that the report
really fit. (I interpreted "i
On Sat 02 Sep 2023 at 19:37:22 +0100, Brian wrote:
> On Sat 02 Sep 2023 at 08:19:56 -0600, D. R. Evans wrote:
>
> [...]
>
> > I will file a bug report.
>
> You have filed the report against general. This is a non-optimal
> package. Someone may or may not move it to a better place.
>
> Doing it
On Sat 02 Sep 2023 at 08:19:56 -0600, D. R. Evans wrote:
[...]
> I will file a bug report.
You have filed the report against general. This is a non-optimal
package. Someone may or may not move it to a better place.
Doing it for yourself:
Send a mail to
cont...@bugs.debian.org
Ib the mail b
Michael Kjörling wrote on 9/2/23 03:23:
You might want to poke around a little among the files in
/etc/NetworkManager, particularly /e/NM/system-connections. That's
what NetworkManager _should_ be using to set up the interfaces. See if
there's something there to explain the two seemingly being
Starting a new thread so that this doesn't get lost in the postings in the
original thread.
The original thread was started at:
https://lists.debian.org/debian-user/2023/09/msg00024.html
That post contains a description of the problem.
I now have a workaround (although not an explanation) fo
On Sat, 2 Sep 2023 08:44:38 -0400
Greg Wooledge wrote:
Hello Greg,
>Because we've already deleted the message from person
I can understand that for the occasional slip up (1), but when the
perpetrator does it habitually
(1) Over-zealous with the delete key, for example.
--
Regards
On Sat, Sep 02, 2023 at 01:09:45PM +0100, Brad Rogers wrote:
> Which begs the question:
> Why do some people respond to a message from person Y, when they're
> /actually/ dealing with something written by person X?
Because we've already deleted the message from person X, and didn't
notice the issu
"D. R. Evans" writes:
> I don't think that debian has used used /etc/network/interfaces for a
> while, at least not by default. Certainly there's nothing useful there
> on the machine that I just upgraded and whose networking is failing to
> configure itself correctly.
I used to think that too.
On Sat, 2 Sep 2023 12:08:37 +0100
Brian wrote:
Hello Brian,
>I did not write any of the text you quote.
You did, but it was not what Timothy was responding to.
What you wrote was quoted right at the bottom of the message, and
irrelevant to Timothy's response.
Which begs the question:
Why do
On Sat, Sep 2, 2023 at 6:34 AM Brian wrote:
> On Fri 01 Sep 2023 at 16:56:42 -0600, D. R. Evans wrote:
>
> > Michel Verdier wrote on 9/1/23 15:06:
> >
> > >
> > > If you want old names put in /etc/default/grub
> > >
> > > GRUB_CMDLINE_LINUX="net.ifnames=0"
> > >
> >
> > Nice to know, but I'll sta
On Fri 01 Sep 2023 at 22:32:00 +, Andy Smith wrote:
> Hello,
>
> On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote:
> > I don't think that debian has used used /etc/network/interfaces for a while,
> > at least not by default.
>
> All of my Debian servers (and desktops) have an
> /e
On Fri 01 Sep 2023 at 16:56:42 -0600, D. R. Evans wrote:
> Michel Verdier wrote on 9/1/23 15:06:
>
> >
> > If you want old names put in /etc/default/grub
> >
> > GRUB_CMDLINE_LINUX="net.ifnames=0"
> >
>
> Nice to know, but I'll stay with the new names, I think.
>
> > network manager is good
On 1 Sep 2023 21:41 -0600, from doc.ev...@gmail.com (D. R. Evans):
> It would be nice to really fix the Network Manager misconfiguration; but it
> seems that the expertise here is all with old-style. Which is fine. I'm
> happy to go back to old-style.
You might want to poke around a little among t
David Wright wrote on 9/1/23 19:40:
I don't see that the OP is doing anything complicated that requires
rc.local to run at all. They just need to distinguish between the two
Correct. I was simply trying to workaround the problem by putting commands
into rc.local that are known to work when I
On Fri, Sep 01, 2023 at 08:40:43PM -0500, David Wright wrote:
> I know you have a low opinion of allow-hotplug, but I can't see that
> auto/allow-auto is necessarily better for the naive user that doesn't
> install a DE for whatever reason.
>
> AIUI auto gives you a one-shot attempt to start the n
On Fri 01 Sep 2023 at 17:38:48 (-0400), Greg Wooledge wrote:
> On Fri, Sep 01, 2023 at 03:18:47PM -0600, D. R. Evans wrote:
> > [[ I speculate wildly that systemd or something doesn't complete configuring
> > the network until after rc.local has finished processing (I know that
> > rc.local execute
Michel Verdier wrote on 9/1/23 15:06:
If you want old names put in /etc/default/grub
GRUB_CMDLINE_LINUX="net.ifnames=0"
Nice to know, but I'll stay with the new names, I think.
network manager is good for changing networks. For a server the network
must not change normally. So you could p
Andy Smith wrote on 9/1/23 16:32:
Your situation appears to have been triggered by the renaming of
your network interfaces (which was warned about in the release
These weird names like "Wired connection enp11s0(eth0)" were names that the
debian installer came up with several OS versions ago (
On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote:
> Greg Wooledge wrote on 9/1/23 15:38:
>
> > In particular, when using /etc/network/interfaces, only interfaces that
> > are marked as "auto" need to be up, to satisfy this criterion. An
>
> I don't think that debian has used used /etc
Hello,
On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote:
> I don't think that debian has used used /etc/network/interfaces for a while,
> at least not by default.
All of my Debian servers (and desktops) have an
/etc/network/interfaces file and ifupdown installed. It depends upon
choice
Greg Wooledge wrote on 9/1/23 15:38:
In particular, when using /etc/network/interfaces, only interfaces that
are marked as "auto" need to be up, to satisfy this criterion. An
I don't think that debian has used used /etc/network/interfaces for a while,
at least not by default. Certainly there
On Fri, Sep 01, 2023 at 03:18:47PM -0600, D. R. Evans wrote:
> [[ I speculate wildly that systemd or something doesn't complete configuring
> the network until after rc.local has finished processing (I know that
> rc.local executes late in the boot process, but I don't think that that
> means that
Thank you for your thoughts...
As people are addressing the rc.local issue (I now realise that I shouldn't
have mentioned it :-) )... I just checked, and:
1. rc.local is being executed;
2. it is executing the nmcli commands;
3. the commands are successful.
But it remains true that when the bo
On 2023-09-01, D. R. Evans wrote:
> The machine has two ethernet ports, which used to be eth0 and eth1 in the old
> days, but are now magically called "Wired connection enp11s0(eth0)" and "Wired
> connection enp12s0(eth1)".
If you want old names put in /etc/default/grub
GRUB_CMDLINE_LINUX="net.i
On 2023-09-01 at 16:50, Greg Wooledge wrote:
> On Fri, Sep 01, 2023 at 08:32:40PM +, Michael Kjörling wrote:
>
>> I don't think /etc/rc.local is executed by default on modern Debian
>> systems. Have you checked to make sure that rc-local.service is
>> enabled and actually gets started during b
On Fri, Sep 01, 2023 at 08:32:40PM +, Michael Kjörling wrote:
> I don't think /etc/rc.local is executed by default on modern Debian
> systems. Have you checked to make sure that rc-local.service is
> enabled and actually gets started during boot? Is there anything
> relevant in the logs for tha
On 1 Sep 2023 14:02 -0600, from doc.ev...@gmail.com (D. R. Evans):
> Well, great, sort-of, except that every time I reboot I have to manually
> issue the two above nmcli commands to take down and bring back up enp11s.
>
> I tried putting them in my rc.local file, but that had no effect (for
> reas
On Fri, 1 Sep 2023 14:02:31 -0600
"D. R. Evans" wrote:
Hello D.,
>So how do I fix this so that the networking is configured to work
>correctly during the boot sequence, as it has always done before?
I had changing ethernet port issues and found that creating
/etc/systemd/network/99-default.link
I just upgraded my main server to bookworm, having successfully, over the
course of the past couple of months, methodically upgraded my other machines
with only minor issues.
Unfortunately, the upgrade of the server, the most important of my machines,
has not been smooth at all, even though no
36 matches
Mail list logo
