Your message dated Sun, 1 Feb 2015 20:20:52 +0100
with message-id <[email protected]>
and subject line Re: Bug#776751: iproute2: "ip a d" deletes too many IP
addresses
has caused the Debian Bug report #776751,
regarding iproute2: "ip a d" deletes too many IP addresses
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
776751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776751
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iproute2
Version: 3.16.0-2
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
perhaps also a kernel issue. The following conversation with my computer just
happened:
Script started on So 01 Feb 2015 11:12:06 CET
root@coffee:~# ip mon &
[1] 2825
root@coffee:~# ip a a dev wlan0 192.168.0.2/24
4: wlan0 inet 192.168.0.2/24 scope global wlan0
valid_lft forever preferred_lft forever
local 192.168.0.2 dev wlan0 table local proto kernel scope host src
192.168.0.2
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.2
broadcast 192.168.0.0 dev wlan0 table local proto kernel scope link src
192.168.0.2
broadcast 192.168.0.255 dev wlan0 table local proto kernel scope link src
192.168.0.2
root@coffee:~# dhclient wlan0
4: wlan0 inet 192.168.0.127/24 brd 192.168.0.255 scope global secondary wlan0
valid_lft forever preferred_lft forever
local 192.168.0.127 dev wlan0 table local proto kernel scope host src
192.168.0.2
default via 192.168.0.1 dev wlan0
root@coffee:~# ip a d dev wlan0 192.168.0.2/24
Deleted 4: wlan0 inet 192.168.0.127/24 brd 192.168.0.255 scope global
secondary wlan0
valid_lft forever preferred_lft forever
Deleted local 192.168.0.127 dev wlan0 table local proto kernel scope host
src 192.168.0.2
Deleted 4: wlan0 inet 192.168.0.2/24 scope global wlan0
valid_lft forever preferred_lft forever
Deleted 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.2
Deleted broadcast 192.168.0.255 dev wlan0 table local proto kernel scope
link src 192.168.0.2
Deleted broadcast 192.168.0.0 dev wlan0 table local proto kernel scope link
src 192.168.0.2
Deleted local 192.168.0.2 dev wlan0 table local proto kernel scope host src
192.168.0.2
delete 192.168.0.1 dev wlan0 lladdr b8:27:eb:1b:73:5d REACHABLE
delete 224.0.0.251 dev wlan0 lladdr 01:00:5e:00:00:fb NOARP
delete 224.0.0.22 dev wlan0 lladdr 01:00:5e:00:00:16 NOARP
root@coffee:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 2c:d4:44:af:97:07 brd ff:ff:ff:ff:ff:ff
3: wwan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 36:30:39:b3:0d:70 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 60:67:20:51:3c:ca brd ff:ff:ff:ff:ff:ff
inet6 fe80::6267:20ff:fe51:3cca/64 scope link
valid_lft forever preferred_lft forever
root@coffee:~# exit
Script done on So 01 Feb 2015 11:13:00 CET
My expectation would be that I can delete the statically configured IP address
without affecting the address set by DHCP.
Simon
- -- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages iproute2 depends on:
ii libc6 2.19-13
ii libdb5.3 5.3.28-7~deb8u1
ii libselinux1 2.3-2
Versions of packages iproute2 recommends:
ii libatm1 1:2.5.1-1.5
ii libxtables10 1.4.21-2+b1
Versions of packages iproute2 suggests:
pn iproute2-doc <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iJwEAQECAAYFAlTN/nQACgkQ0sfeulffv7vMhQP/YPryGUVYckWKm5q/eZ58z9aY
zaugOuCXJfbeoyRupnJI+0e6cH60W0rmkFPY2rvfGrz1UoAqkR9DM65fXACjzD81
zSTnIUH2IPi2VdaHLx6a1LAWgRD50BoBWEsTPfFOVg9KuPYicvPCQg/b65wLgKQd
swCuk6KaNA6JSNrxUsg=
=ZdS+
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hello Simon Richter!
I'm pretty sure everything is working as expected. See below.
On Sun, Feb 01, 2015 at 11:22:53AM +0100, Simon Richter wrote:
[...]
> perhaps also a kernel issue. The following conversation with my computer just
> happened:
>
[...]
> 4: wlan0 inet 192.168.0.127/24 brd 192.168.0.255 scope global secondary
> wlan0
[...]
^^^^^^^^^
I guess this is one of the addresses you want to not "dissapear" when
your remove the primary address.
Please beware, you have added a secondary address (rather then additional
primary addresses).
Please compare this against your settings in
/proc/sys/net/ipv4/conf/all/promote_secondaries
I'm closing this since I bet you're able to figure out the rest... We don't
have resources for support in the bug tracking system. Please feel free
to reopen when you've researched your issue more and think you're actually
seeing a bug.
Regards,
Andreas Henriksson
--- End Message ---