On Fri, Feb 03, 2023 at 03:29:54PM +0100, Santiago Ruano Rincón wrote:
> Hi!
>
> El 31/01/23 a las 14:10, Antoine Beaupré escribió:
[..snip..]
> > One might argue this should be the default and that ifup should clear
> > interfaces before bringing them up, but I'm not familiar enough with
> > if
Hi!
El 31/01/23 a las 14:10, Antoine Beaupré escribió:
> I have a similar problem with ifupdown on my home server which has
> accumulated a rather unfortunate pile of crap...
>
> I am not sure where the problem comes from. I suspect it might be
> related to the initrd raising the interfaces befor
On 2023-01-31 21:02:11, ael wrote:
> On Tue, Jan 31, 2023 at 02:10:46PM -0500, Antoine Beaupré wrote:
>> I have a similar problem with ifupdown on my home server which has
>> accumulated a rather unfortunate pile of crap...
>>
>> iface eth0 inet static
>> # fix RTNETLINK errors on boot see ht
On Tue, Jan 31, 2023 at 02:10:46PM -0500, Antoine Beaupré wrote:
> I have a similar problem with ifupdown on my home server which has
> accumulated a rather unfortunate pile of crap...
>
> iface eth0 inet static
> # fix RTNETLINK errors on boot see https://bugs.debian.org/961508
> pr
I have a similar problem with ifupdown on my home server which has
accumulated a rather unfortunate pile of crap...
I am not sure where the problem comes from. I suspect it might be
related to the initrd raising the interfaces before ifup actually runs,
and the RTNETLINK error is about the gateway
Package: ifupdown
Version: 0.8.35
Severity: normal
There seem to be so many open bugs for ifupdown that it is not clear
whether there is any point in reporting this, but perhaps it may help
others.
I have encountered the unhelpful error message "RTNETLINK answers: File
exists" on more than one m
6 matches
Mail list logo
