Re: Sid: /sbin/ifenslave missing??

2020-05-17 Thread Sven Hartge
Sven Hartge  wrote:

> Temporary solution: downgrade to 2.9 again, hold the package and monitor
> the bug report I linked.

Sorry, the correct bug is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959236

Unfortunately it has only "normal" severity, "grave" would be better
here, since it not only breaks the function of the package, it breaks
the whole system.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.



Re: Sid: /sbin/ifenslave missing??

2020-05-17 Thread Sven Hartge
Grzesiek Sójka  wrote:
> On 5/17/20 12:34 PM, Sven Hartge wrote:

>> Mind doing a "ifup -v bond0" to really see what is called how and where
>> it fails in what way?

> after "ifup -v bond0" I get a larg number of following messages 
> (probably 1000?):

> + [ -n  ]
> + return 0
> + setup_master
> + add_master
> + [ -f /sys/class/net/bond0/bonding/slaves ]
> + return
> + early_setup_master
> + sysfs fail_over_mac
> + [ -n  ]
> + return 0
> + setup_master
> + add_master
> + [ -f /sys/class/net/bond0/bonding/slaves ]
> + return
> + early_setup_master
> + sysfs fail_over_mac
> /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth 
> (1000) reached
> run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 2
> ifup: failed to bring up bond0

Interesting. Yes, this seems like a genuine bug in the package but not
caused by the removal of the ifenslave shell script but by some bug in
the ifup-(pre)scripts provided by the package.

Temporary solution: downgrade to 2.9 again, hold the package and monitor
the bug report I linked.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.



Re: Sid: /sbin/ifenslave missing??

2020-05-17 Thread Grzesiek Sójka

On 5/17/20 12:34 PM, Sven Hartge wrote:

Mind doing a "ifup -v bond0" to really see what is called how and where
it fails in what way?


after "ifup -v bond0" I get a larg number of following messages 
(probably 1000?):


+ [ -n  ]
+ return 0
+ setup_master
+ add_master
+ [ -f /sys/class/net/bond0/bonding/slaves ]
+ return
+ early_setup_master
+ sysfs fail_over_mac
+ [ -n  ]
+ return 0
+ setup_master
+ add_master
+ [ -f /sys/class/net/bond0/bonding/slaves ]
+ return
+ early_setup_master
+ sysfs fail_over_mac
/etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth 
(1000) reached

run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 2
ifup: failed to bring up bond0

BTW: # apt-list | grep ifup
ifupdown/unstable,now 0.8.35+b1 amd64 [installed]



Re: Sid: /sbin/ifenslave missing??

2020-05-17 Thread Sven Hartge
Grzesiek Sójka  wrote:
> On 5/17/20 12:13 PM, Sven Hartge wrote:

>> How does your /etc/network/interfaces look like? Usally all the work is
>> done via if-pre-up.d and if-up.d scripts provided by the ifenslave
>> package.

> # cat /etc/network/interfaces
> source-directory /etc/network/interfaces.d
> auto bond0

> iface bond0 inet static
>   address 192.168.0.130
>   netmask 255.255.255.252
>   gateway 192.168.0.129
>   slaves eth0 eth1
>   mtu 9000

> So I need to "adjust" network configuration to bond using iproute2 instead?

No, that should work, my configurations look similar (but they are all
on Buster and thus on 2.9, so I have not seen this bug myself).

Mind doing a "ifup -v bond0" to really see what is called how and where
it fails in what way?

Grüße,
Sven.


-- 
Sigmentation fault. Core dumped.



Re: Sid: /sbin/ifenslave missing??

2020-05-17 Thread Grzesiek Sójka

On 5/17/20 12:13 PM, Sven Hartge wrote:

How does your /etc/network/interfaces look like? Usally all the work is
done via if-pre-up.d and if-up.d scripts provided by the ifenslave
package.


# cat /etc/network/interfaces
source-directory /etc/network/interfaces.d
auto bond0

iface bond0 inet static
  address 192.168.0.130
  netmask 255.255.255.252
  gateway 192.168.0.129
  slaves eth0 eth1
  mtu 9000

So I need to "adjust" network configuration to bond using iproute2 instead?



Re: Sid: /sbin/ifenslave missing??

2020-05-17 Thread Sven Joachim
On 2020-05-17 11:27 +0200, Grzesiek Sójka wrote:

> After upgrading ifenslave from 2.9 to 2.10 i found that there if no
> /sbin/ifenslave binary. To restore network connectivity I had to 
> manually downgrade to 2.9. Is it on purpose? If so, then how to
> properly configure link aggregation?

I don't use ifenslave, but this change has been done on purpose:

,
| ifenslave (2.10) unstable; urgency=medium
| [...]
|   * Remove the ifenslave binary, use iproute2 instead.
| [...]
|  -- Guus Sliepen   Sun, 26 Apr 2020 21:09:15 +0200
`

Refer to ip(8) and the manpages it references, if you can comprehend
them.

Cheers,
   Sven



Re: Sid: /sbin/ifenslave missing??

2020-05-17 Thread Sven Hartge
Grzesiek Sójka  wrote:

> After upgrading ifenslave from 2.9 to 2.10 i found that there if no
> /sbin/ifenslave binary. To restore network connectivity I had to
> manually downgrade to 2.9. Is it on purpose? If so, then how to
> properly configure link aggregation?

It seems you hit
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959075

But NEWS.Debian says:

,
| ifenslave (2.10) UNRELEASED; urgency=medium
|
|   This version of the ifenslave package no longer provides /sbin/ifenslave. 
The
|   /sbin/ip command from the iproute2 package supports creating bonding masters
|   and enslaving other interfaces to it.
|
|  -- Guus Sliepen   Tue, 08 May 2018 22:47:07 +0200
`

How does your /etc/network/interfaces look like? Usally all the work is
done via if-pre-up.d and if-up.d scripts provided by the ifenslave
package.

S!

-- 
Sigmentation fault. Core dumped.



Sid: /sbin/ifenslave missing??

2020-05-17 Thread Grzesiek Sójka

Hi there,

After upgrading ifenslave from 2.9 to 2.10 i found that there if no 
/sbin/ifenslave binary. To restore network connectivity I had to 
manually downgrade to 2.9. Is it on purpose? If so, then how to properly 
configure link aggregation?


Thank for any help in advance
Greg