Version: 0.7.8


Since upgrading from Debian Squeeze to Wheezy I have been having a number
of issues with the ifupdown package.


 I have found what appears to be two new bugs in ifupdown 0.7.8-Wheezy
which were not in 0.6.10-Squeeze.


 *Bug No 1:-*


 ifupdown no longer supports interfaces with minus signs in the name for
example:-


 wan-2.3076:ucarp


 if I attempt to bring up the interface like so:-


 ifup wan-2.3076:ucarp


 I am presented with the following error message:-


 RTNETLINK answers: Numerical result out of range
Failed to bring up wan-2.3076:ucarp.

If I force install (downgrade) to ifupdown 0.6.10-Squeeze, I am able to
bring up the interface.


 If I rename the interface to wan2.3076:ucarp I am able to bring up the
interface using ifupdown 0.7.8.


 *Bug No 2:-*


 ifdown brings down the underlying vlan when trying to shut-down a virtual
interface.


 For example,


 If I have a physical interface:-


 wan2, with a vlan 3076 running ucarp on a virtual interface I should be
able to shut-down each interface in sequence.


 ifdown wan2.3076:ucarp

ifdown wan2.3076


 However if I type:-


 ifdown wan2.3076:ucarp running ifupdown 0.7.8 it brings down vlan 3076 and
the virtual ucarp interface.


 It should only bring down the virtual ucarp interface.


 If I force install ifupdown 0.6.10-Squeeze it works correctly.


 Can someone please look at this urgently.

Hello,

Trevor, please try to install the latest ifupdown from testing and tell
me if anything changes.

Thanks.

Hello,

The only real difference in dependencies is iproute2. I think there
shouldn't be any problem with it.

Hello,

Well, recompiling from source gave you the same dependencies as
ifupdown doesn't depend on anything newer really :) You should have
changed iproute2 dependency to iproute, which is the old name of that
package. Newer iproute would upgrade your libc, but nothing really
apart from that, but as you've already built ifupdown from source,
just change the dependency.

Hello,

Just edit debian/rules before building, change iproute2 to iproute
there.

P.S. Please don't remove the BTS address from Cc.

Hello,


No, that's fine.

Good.

Probably something's still wrong in ifupdown's vlan/alias parsing code.
Unfortunately, I can't spend much time on this now, but I'll try to
produce some solution soon.

And once again, as I asked you already, please don't remove the BTS
address from Cc. If you're using a web mail, please use Reply to All
button — we want the communications to be logged in the bug report.

Hello,

Trevor, I tried to reproduce your issue, but I couldn't, unfortunately.

Could you please run ifup with -v and give me its output, and a
corresponding chunk from your interfaces file.

Version: 0.7.8


Does anyone know when the fixed ifupdown package (0.7.48.1?) will be
available in wheezy-backports?

I have the same issue with using vlans and ucarp:


root@test:~# ifquery -l -v
lo
eth2.40
eth2.10
eth3.90

root@test:~# ifquery -v eth2.40
Querying interface eth2.40=eth2.40 (inet)
address: 10.1.40.252
network: 10.1.40.0
netmask: 255.255.255.0
broadcast: 10.1.40.255
vlan-raw-device: eth2
ucarp-vid: 40
ucarp-vip: 10.1.40.254
ucarp-password: secretpassword
ucarp-advskew: 10
ucarp-master: yes

root@test:~# ifquery -v eth2.40:ucarp
Querying interface eth2.40:ucarp=eth2.40:ucarp (inet)
address: 10.1.40.254
netmask: 255.255.255.255
broadcast: 10.1.40.254

root@test:~# ip addr show eth2.40
6: eth2.40@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP link/ether 90:e2:ba:64:f3:60 brd ff:ff:ff:ff:ff:ff
    inet 10.1.40.252/24 brd 10.1.40.255 scope global eth2.40
    inet 10.1.40.254/32 brd 10.1.40.254 scope global eth2.40:ucarp
    inet6 fe80::92e2:baff:fe64:f360/64 scope link
       valid_lft forever preferred_lft forever

root@test:~# ifdown -v eth2.40:ucarp
Configuring interface eth2.40:ucarp=eth2.40:ucarp (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/sendmail
run-parts: executing /etc/network/if-down.d/upstart

ip -4 addr flush dev eth2.40:ucarp label eth2.40:ucarp
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/sendmail
run-parts: executing /etc/network/if-post-down.d/vlan
ip link del eth2.40:ucarp

root@test:~# ip addr show eth2.40
Device "eth2.40" does not exist.



Thanks

actually we should file a different bug for it as it is actually an iproute(2)
problem.
The problem here is (I do have the same issues):
ip link del eth2.40:ucarp will also bring down / delete the underlaying
interface eth2.40. IMHO ip shouldn't touch the underlaying interface.