Your message dated Wed, 13 Nov 2013 22:34:39 +0100 with message-id <[email protected]> and subject line Re: iproute2: doesn't calculate the broadcast addr for IPv4 aliases has caused the Debian Bug report #717887, regarding iproute2: doesn't calculate the broadcast addr for IPv4 aliases 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.) -- 717887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717887 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: iproute2 Version: 3.10.0-1 Severity: normal Tags: upstream Hi. Not sure wheter this is actually an issue or not: When using ifconfig, respectively the old schema via /e/n/interfaces to set up secondary IP addresses like this: iface eth0:1 inet static address 84.16.242.145 netmask 255.255.255.0 it will also automatically calculate the broadcast address: e.g. eth0:1 Link encap:Ethernet HWaddr 82:a7:3a:36:38:27 inet addr:84.16.242.145 Bcast:84.16.242.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 It seems that with iproute/ip this no longer happens for such secondary addresses, i.e. when doing: ip addr add 1.2.3.4/27 dev eth0 label eth0:0 I'd get: inet 1.2.3.4/27 brd 0.0.0.0 scope global secondary eth0:0 valid_lft forever preferred_lft forever I really have to set it manually as in ip addr add 1.2.3.4/27 broadcast 1.2.3.4 dev eth0 label eth0:0 to get inet 1.2.3.4/27 brd 1.2.3.223 scope global secondary eth0:0 valid_lft forever preferred_lft forever But as said... I'm not sure whether this is intended at all or a feature. Cheers, Chris.
--- End Message ---
--- Begin Message ---On Fri, Jul 26, 2013 at 02:59:35AM +0200, Christoph Anton Mitterer wrote: [...] > Not sure wheter this is actually an issue or not: As far as I can tell, there is no issue. > > When using ifconfig, respectively the old schema via /e/n/interfaces > to set up secondary IP addresses like this: > iface eth0:1 inet static > address 84.16.242.145 > netmask 255.255.255.0 > > it will also automatically calculate the broadcast address: > e.g. > eth0:1 Link encap:Ethernet HWaddr 82:a7:3a:36:38:27 > inet addr:84.16.242.145 Bcast:84.16.242.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Thanks for including the comparison with ifconfig, but please when there's a difference - don't assume deprecated ifconfig is correct. > > > It seems that with iproute/ip this no longer happens for such secondary > addresses, > i.e. when doing: > ip addr add 1.2.3.4/27 dev eth0 label eth0:0 > I'd get: > inet 1.2.3.4/27 brd 0.0.0.0 scope global secondary eth0:0 > valid_lft forever preferred_lft forever This means the broadcast address is auto-calculated by linux. > > I really have to set it manually as in Why do you really need to do that? Manually setting it is discuraged unless you have a non-standard networking setup. You should not set it, and let linux do it's job. > ip addr add 1.2.3.4/27 broadcast 1.2.3.4 dev eth0 label eth0:0 > to get > inet 1.2.3.4/27 brd 1.2.3.223 scope global secondary eth0:0 > valid_lft forever preferred_lft forever > > > But as said... I'm not sure whether this is intended at all or a feature. As already mentioned, I can't see any issue - so closing this bug report. > > Cheers, > Chris. > > -- Andreas Henriksson
--- End Message ---
