From: Marcello Barnaba <marcello@softmedia.info>
To: linux-kernel@vger.kernel.org
Subject: Interfaces losing inet6 addresses in ifconfig output after some uptime
Date: Thu, 29 Jul 2004 15:42:17 +0200 [thread overview]
Message-ID: <1091108537.14310.33.camel@nowhere.openssl.softmedia.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 2310 bytes --]
This is somewhat strange, after an average of 25 days of uptime, either
with kernel 2.6.6 or kernel 2.6.7 (didn't notice this with earlier
kernels, but the problem may be there as well, sorry but I didn't care
about this before, and the box is in production so it cannot be rebooted
easily), ifconfig does not display the inet6 addresses of my interfaces
anymore, but the addresses work as expected and are correctly in iproute
output:
golem:/etc/shorewall# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:FC:5A:0B:58
inet addr:192.168.203.1 Bcast:192.168.203.127
Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:50564399 errors:0 dropped:0 overruns:0 frame:0
TX packets:46289378 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3363466008 (3.1 GiB) TX bytes:1097487814 (1.0 GiB)
Interrupt:10
golem:/etc/shorewall# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:50:fc:5a:0b:58 brd ff:ff:ff:ff:ff:ff
inet 192.168.203.1/25 brd 192.168.203.127 scope global eth0
inet 192.168.203.6/25 brd 192.168.203.127 scope global secondary
eth0:1
inet6 2001:1418:106:1::a1/64 scope global
valid_lft forever preferred_lft forever
inet6 2001:1418:106:1::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::250:fcff:fe5a:b58/64 scope link
valid_lft forever preferred_lft forever
oh, as you can see I just now noticed that ifconfig dropped the
secondary interface IP address as well..
This is a vanilla 2.6.7:
Linux golem.softmedia.lan 2.6.7 #1 Fri Jul 2 11:11:30 CEST 2004 i686
unknown
15:41:42 up 27 days, 4:21, 2 users, load average: 0.01, 0.00, 0.00
..running a debian woody:
net-tools 1.60
ifconfig 1.42 (2001-04-13)
Known kernel bug, ifconfig bug, whatever? A net-tools upgrade from
backports.org is possible, what do you guys think about this issue?
TIA.
--
Marcello Barnaba - SoftMedia S.c.r.l. :: Mobile: +39 (340) 3698342
Via Mauro Amoruso, 11 - 70124 Bari :: Phone: +39 (080) 5046314
pub 1024D/F04476A2 :: 6807 EEA5 7F97 AC9A D8EF AE73 64CD 71A2 F044 76A2
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-07-29 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 13:42 Marcello Barnaba [this message]
2004-07-29 15:54 ` Brian Bruns
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=1091108537.14310.33.camel@nowhere.openssl.softmedia.lan \
--to=marcello@softmedia.info \
--cc=linux-kernel@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 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®