From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Alexey Toptygin <alexeyt@freeshell.org>
Cc: lartc@mailman.ds9a.nl, netdev@vger.kernel.org
Subject: Re: [LARTC] ip address delete bug?
Date: Tue, 04 Oct 2005 22:58:19 +0000 [thread overview]
Message-ID: <4343090B.5010803@gmx.net> (raw)
In-Reply-To: <Pine.NEB.4.62.0510042118190.24353@ukato.freeshell.org>
Alexey Toptygin schrieb:
> On Tue, 4 Oct 2005, Carl-Daniel Hailfinger wrote:
>
>> OK, I found out that this is documented behaviour, although the hint
>> is not in the man page.
>
> If it's not in the man page, then where is the below quote from?
ip-cref.tex.
>> "secondary --- this address is not used when selecting the default
>> source address for outgoing packets. An IP address becomes secondary
>> if another address within the same prefix (network) already exists.
>> The first address within the prefix is primary and is the tag address
>> for the group of all the secondary addresses. When the primary address
>> is deleted all of the secondaries are purged too."
>>
>> That means there is no way to change the IP of an interface if the
>> prefix and network size stay the same. Are there any plans to fix that?
>
> What's wrong with delete followed by add?
You are logged into the machine via ssh on eth0. You delete the ip
address of eth0. How are you going to add the new address to eth0 now
that your connection is gone? Go to the server room and use the console?
Normally, I would add the new IP to eth0, start another ssh to the new
IP, log out from the session to the old IP, remove the old IP from eth0
and be done. If I want the server to be reachable under both IPs during
a transition period, I can delay deletion of the old IP until later.
> This thread started on netdev, so I'm cc-ing that, in case someone
> doesn't read both lists.
Didn't start there, but if netdev is interested, we can keep them in cc.
> Alexey
Regards,
Carl-Daniel
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
WARNING: multiple messages have this Message-ID (diff)
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Alexey Toptygin <alexeyt@freeshell.org>
Cc: lartc@mailman.ds9a.nl, netdev@vger.kernel.org
Subject: Re: ip address delete bug?
Date: Wed, 05 Oct 2005 00:58:19 +0200 [thread overview]
Message-ID: <4343090B.5010803@gmx.net> (raw)
In-Reply-To: <Pine.NEB.4.62.0510042118190.24353@ukato.freeshell.org>
Alexey Toptygin schrieb:
> On Tue, 4 Oct 2005, Carl-Daniel Hailfinger wrote:
>
>> OK, I found out that this is documented behaviour, although the hint
>> is not in the man page.
>
> If it's not in the man page, then where is the below quote from?
ip-cref.tex.
>> "secondary --- this address is not used when selecting the default
>> source address for outgoing packets. An IP address becomes secondary
>> if another address within the same prefix (network) already exists.
>> The first address within the prefix is primary and is the tag address
>> for the group of all the secondary addresses. When the primary address
>> is deleted all of the secondaries are purged too."
>>
>> That means there is no way to change the IP of an interface if the
>> prefix and network size stay the same. Are there any plans to fix that?
>
> What's wrong with delete followed by add?
You are logged into the machine via ssh on eth0. You delete the ip
address of eth0. How are you going to add the new address to eth0 now
that your connection is gone? Go to the server room and use the console?
Normally, I would add the new IP to eth0, start another ssh to the new
IP, log out from the session to the old IP, remove the old IP from eth0
and be done. If I want the server to be reachable under both IPs during
a transition period, I can delay deletion of the old IP until later.
> This thread started on netdev, so I'm cc-ing that, in case someone
> doesn't read both lists.
Didn't start there, but if netdev is interested, we can keep them in cc.
> Alexey
Regards,
Carl-Daniel
next prev parent reply other threads:[~2005-10-04 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 17:55 [LARTC] ip address delete bug? Carl-Daniel Hailfinger
2005-10-03 18:00 ` Peter Surda
2005-10-04 19:11 ` Carl-Daniel Hailfinger
2005-10-04 21:23 ` Alexey Toptygin
2005-10-04 21:23 ` Alexey Toptygin
2005-10-04 22:58 ` Carl-Daniel Hailfinger [this message]
2005-10-04 22:58 ` Carl-Daniel Hailfinger
2005-10-04 23:08 ` [LARTC] " Alexey Toptygin
2005-10-04 23:08 ` Alexey Toptygin
[not found] ` <1128474946.6224.8.camel@localhost.localdomain>
2005-10-05 15:32 ` [LARTC] " Carl-Daniel Hailfinger
2005-10-05 15:32 ` Carl-Daniel Hailfinger
2005-10-04 23:20 ` [LARTC] " Peter Surda
2005-10-04 23:23 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4343090B.5010803@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--cc=alexeyt@freeshell.org \
--cc=lartc@mailman.ds9a.nl \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.