Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g7FG7qRw006391 for ; Thu, 15 Aug 2002 09:07:53 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g7FG7qQk006390 for netdev-outgoing; Thu, 15 Aug 2002 09:07:52 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-netdev@oss.sgi.com using -f Received: from kaneda.pheared.net (root@kaneda.isrd.net [206.205.246.39]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g7FG7dRw006380 for ; Thu, 15 Aug 2002 09:07:39 -0700 Received: from kaneda.isrd.lan (kevin@localhost [127.0.0.1]) by kaneda.pheared.net (8.12.3/8.12.3) with ESMTP id g7FGABCK010105; Thu, 15 Aug 2002 12:10:11 -0400 Received: from localhost (kevin@localhost) by kaneda.isrd.lan (8.12.3/8.12.3/Submit) with ESMTP id g7FGABdL010101; Thu, 15 Aug 2002 12:10:11 -0400 X-Authentication-Warning: kaneda.isrd.lan: kevin owned process doing -bs Date: Thu, 15 Aug 2002 12:10:11 -0400 (EDT) From: Kevin Dwyer To: kuznet@ms2.inr.ac.ru cc: Alan Robertson , Subject: Re: Resend: SIOCGIFBRDADDR? In-Reply-To: <200208151533.TAA26970@sex.inr.ac.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-4.5 required=5.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK version=2.20 X-Spam-Level: Sender: owner-netdev@oss.sgi.com Precedence: bulk On Thu, 15 Aug 2002, kuznet@ms2.inr.ac.ru grunted something like: > You forgot to say what kind of "bogus result" is obtained. Since I'm the one who has primarily been chasing this problem, I'll explain. (cut from my original email...) Specifically, it uses iproute to add aliases to a device, like eth0 in this example: ip -f inet addr add 10.5.5.1 dev eth0 scope link ip -f inet addr add 10.5.5.2 dev eth0 scope link ip -f inet addr add 10.5.5.3 dev eth0 scope link ip -f inet addr add 10.5.5.4 dev eth0 scope link ip -f inet addr add 10.5.5.5 dev eth0 scope link That's all fine, except that it causes really weird stuff to happen to the output of ifconfig. For one, the inet addr: field will change once in a while if I make a modification with ifconfig. That doesn't affect heartbeat, but the Bcast: field is wrongly reported as 0.0.0.0. Now, I know for a fact that I set it correctly when I bring up the interface, prior to using the ip route commands. Once they've been applied, it goes crazy. So my question: Does anyone know if there's an ip route command to make the Bcast field show up as the correct value, or is there a better way for heartbeat to get the broadcast address? (and from a followup email...) # ip addr show eth0 primary scope global 2: eth0: mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:c0:95:e1:bc:64 brd ff:ff:ff:ff:ff:ff inet 10.5.5.8/24 brd 10.5.5.255 scope global eth0 That command gives me the correct broadcast address in the brd field. Correct meaning, the one we're looking for, and would otherwise have gotten if I hadn't used the before-mentioned iproute commands. Any help is appreciated. Thanks. -[ kevin@pheared.net devel.pheared.net ]- -[ Rather be forgotten, than remembered for giving in. ]- -[ ZZ = g ^ (xb * xa) mod p g = h^{(p-1)/q} mod p ]-