On 2022-04-11 07:56, Reco wrote:
> Good news - it explains "ifup: unknown interface eth0" messages.
> Bad news - this /e/n/i is not valid.
>
> The reason being - both eth0 and eth1 lack interface definitions, i.e.
> have no "iface" stanzas.
>
> If you absolutely need both eth0 and eth1 in the UP
Hi.
On Mon, Apr 11, 2022 at 01:48:35AM +0200, Dmitry Katsubo wrote:
> The configuration is trivial: it adds both eth0 eth1 to the bridge
> br0.
>
> === cut /etc/network/interfaces ===
> auto lo
> auto eth0
> auto eth1
>
> iface lo inet loopback
>
> auto br0
> iface br0 inet static
>
> As /var/log/messages helpfully show, your udev rules work.
> The problem is, next thing udev does is renaming your network interfaces
> back to (Un)Predictable Naming™ scheme.
>
> Thus whatever stanzas you have in your interfaces(5) about eth0 and eth1
> fail, thus the whole netw
t;,
> KERNEL=="eth*", NAME="eth1"
As /var/log/messages helpfully show, your udev rules work.
The problem is, next thing udev does is renaming your network interfaces
back to (Un)Predictable Naming™ scheme.
Thus whatever stanzas you have in your interfaces(5) about eth0 a
On Sun, Apr 03, 2022 at 10:48:31PM -0500, David Wright wrote:
> On Mon 04 Apr 2022 at 02:38:39 (+0200), Dmitry Katsubo wrote:
> > On 2021-02-17 14:21, Henning Follmann wrote:
> >
> > > Are you using eth0, eth1?
> > > Or are you using predictable network names?
> > >
On Mon 04 Apr 2022 at 02:38:39 (+0200), Dmitry Katsubo wrote:
> On 2021-02-17 14:21, Henning Follmann wrote:
>
> > Are you using eth0, eth1?
> > Or are you using predictable network names?
> > https://wiki.debian.org/NetworkInterfaceNames
> Well, I use eth0/eth1 as I have renamed them from
On Mon, Apr 04, 2022 at 02:38:39AM +0200, Dmitry Katsubo wrote:
> I've exercised several directions to solve the issue, however I've failed.
> Would be great if somebody can share his idea. After upgrading from Debian
> buster to bullseye I still have the same issue:
Upgrading from one release
On 4/4/22 10:31 am, Jeremy Ardley wrote:
In my case I am delegating ipv6 prefixes that I obtain from my ISP and
also advertising them, making radvd redundant. I have kept my ISC dhcp
servers as I am doing DDNS with my bind instance. Possibly
systemd-networkd.service does DDNS as well but I
On 4/4/22 10:15 am, Charles Curley wrote:
On Mon, 4 Apr 2022 09:50:19 +0800
Jeremy Ardley wrote:
* systemd-networkd.service
* networking.service
* NetworkManager.service
Possibly because they do different things.
I have no experience what the first one does.
On Mon, 4 Apr 2022 09:50:19 +0800
Jeremy Ardley wrote:
> * systemd.networkd.service
> * networking.service
> * NetworkManager.service
Possibly because they do different things.
I have no experience what the first one does. The latter two are not
mutually exclusive. Use networking.service
On 4/4/22 8:38 am, Dmitry Katsubo wrote:
Dear Debian community,
I've exercised several directions to solve the issue, however I've failed.
Would be great if somebody can share his idea. After upgrading from Debian
buster to bullseye I still have the same issue:
# systemctl status
Dear Debian community,
I've exercised several directions to solve the issue, however I've failed.
Would be great if somebody can share his idea. After upgrading from Debian
buster to bullseye I still have the same issue:
# systemctl status networking.service
— networking.service - Raise
On 2021-02-17 08:28, Andrei POPESCU wrote:
On Mi, 17 feb 21, 00:01:01, Gary Dale wrote:
On 2021-02-16 19:44, Dmitry Katsubo wrote:
Dear Debian community,
I am puzzled with the following problem. When my Debian 10.8 starts, the unit
"networking.service" is
marked as failed with the following
On Mi, 17 feb 21, 00:01:01, Gary Dale wrote:
> On 2021-02-16 19:44, Dmitry Katsubo wrote:
> > Dear Debian community,
> >
> > I am puzzled with the following problem. When my Debian 10.8 starts, the
> > unit "networking.service" is
> > marked as failed with the following reason:
> >
> >
On Wed, Feb 17, 2021 at 01:44:35AM +0100, Dmitry Katsubo wrote:
> Dear Debian community,
>
> I am puzzled with the following problem. When my Debian 10.8 starts, the unit
> "networking.service" is
> marked as failed with the following reason:
>
[...]
>
> and also set a big timeout for br0 in
On 2021-02-16 19:44, Dmitry Katsubo wrote:
Dear Debian community,
I am puzzled with the following problem. When my Debian 10.8 starts, the unit
"networking.service" is
marked as failed with the following reason:
root@debian:~ # systemctl status networking.service
*— networking.service -
Hi.
On Wed, Feb 17, 2021 at 01:44:35AM +0100, Dmitry Katsubo wrote:
> root@debian:~ # systemctl status networking.service
...
> Process: 691 ExecStart=/sbin/ifup -a --read-environment (code=exited,
> status=1/FAILURE)
> Main PID: 691 (code=exited, status=1/FAILURE)
...
> Any ideas
Dear Debian community,
I am puzzled with the following problem. When my Debian 10.8 starts, the unit
"networking.service" is
marked as failed with the following reason:
root@debian:~ # systemctl status networking.service
*— networking.service - Raise network interfaces
Loaded: loaded
18 matches
Mail list logo
