From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org, net-tools@lina.inka.de, philb@gnu.org
Subject: Re: ifconfig and SIOCSIFADDR
Date: Wed, 25 Jul 2001 20:26:58 GMT [thread overview]
Message-ID: <200107252026.UAA21184@vlet.cwi.nl> (raw)
Hello!
And hello again!
> Yes. It didn't in 2.0.
Soooory, it did. This behavior is copied from there. :-)
You are mistaken. I already quoted you the source.
In case you do not believe in source reading I can demo as well.
2.4:
# ifconfig lo netmask 255.254.0.0 10.0.0.150
# ifconfig lo
lo Link encap:Local Loopback
inet addr:10.0.0.150 Mask:255.0.0.0
[2.4.6, net-tools 1.60]
2.0:
# ifconfig lo netmask 255.254.0.0 10.0.0.150
# ifconfig lo
lo Link encap:Local Loopback
inet addr:10.0.0.150 Bcast:127.255.255.255 Mask:255.254.0.0
[2.0.34, net-tools 1.33]
As you see, the behaviour where setting the address kills
the already set netmask is new.
> Yes. I liked such logic thirty years ago. That is Unix.
:-) Seems, thirty years ago there were not only Internet but Unix too.
Yes, rounded to a nice number. I suppose we started using Unix
26 or 27 years ago or so.
BTW I did not hear about any kind of Unix, which forgets
to set a valid mask on newly selected address.
Linux 2.0, when there already is a nonzero mask.
A zero mask is replaced by a default:
2.0:
# ifconfig lo netmask 0.0.0.0 10.0.0.150
# ifconfig lo
lo Link encap:Local Loopback
inet addr:10.0.0.150 Bcast:127.255.255.255 Mask:255.0.0.0
...
Andries
next reply other threads:[~2001-07-25 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 20:26 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-25 19:23 Andries.Brouwer
2001-07-25 19:40 ` kuznet
2001-07-26 14:47 ` Gerhard Mack
2001-07-24 14:47 Andries.Brouwer
2001-07-24 16:05 ` Ingo Oeser
2001-07-24 22:50 ` Alexey Kuznetsov
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=200107252026.UAA21184@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=net-tools@lina.inka.de \
--cc=philb@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®