>>> Lars Ellenberg <[email protected]> schrieb am 23.05.2011 um 15:37 in
Nachricht <[email protected]>:
> On Mon, May 23, 2011 at 01:13:48PM +0200, Lars Marowsky-Bree wrote:
> > On 2011-05-12T11:28:49, Ulrich Windl <[email protected]>
> > wrote:
> >
> > > So I guess it simply does not work (or more likely: it never was
> implemented).
> >
> > That is not correct, by the way.
>
> Oh yes, it is correct.
>
> IPaddr somehow received that parameter in its meta data,
> but does not use it. At least not in my checkout.
>
> That may have been just before it was split into IPaddr and IPaddr2.
>
> IPaddr2 however does implement it:
>
> > "iflabel" is implemented and passed to
> > the "ip" command via the "label" commandline option (if set).
>
> That is IPaddr2.
> IPaddr does not know about the "ip" command.
>
> So conclusion may be: use IPaddr2 ;-)
Hi!
My book of "incredible cluster wisdom" ;-) (I don't want to make advertisement;
it's only German anyway (ISBN 978-3-8362-1339-4)) says IPaddr is using ifconfig
to add a new virtual interface on an existing one (visible through ifconfig),
while IPaddr2 is using ip internally (not visible through ifconfig).
As YaST (SUSE's ifup) some managed to make interfaces that are both labelled
and visible through "ifconfig", I was not expecting the impossible ;-)
Actually here's the interesting part:
MESSAGE=`\
ip addr add dev $INTERFACE \
"local" $IPADDR${PREFIXLEN:+/$PREFIXLEN} \
${REMOTE_IPADDR:+peer $REMOTE_IPADDR} \
${BROADCAST:+broadcast "$BROADCAST"} \
${LABEL:+label $INTERFACE:$LABEL} \
${SCOPE:+scope $SCOPE} \
$IP_OPTIONS \
2>&1 `
>
> And we need to patch out the "iflabel" parameter from IPaddr again,
> probably.
Sounds like a good idea.
[...]
Regards,
Ulrich
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
