Hi,
This issue has been bugging me on and off for a while, so I thought to
write it up and test it a bit more extensively.
I'm running FC4 on a Thinkpad laptop and an external old Orinoco WLAN
card. I have observed four, probably somewhat related phenomena:
A) when router lifetime is about to expire, the timer seems to wrap
for about 25 seconds. Does this overflow anything, or is
this just cosmetic?
B) sometimes, the card just sees the first RA (returned from RS
instead of multicast, maybe?), and the route/address times out
after it expires.
C) sometimes the card needs to be put to promiscuous mode to see
the first router advertisement, the rest work fine from that point
forward.
D) sometimes the card needs to be put to promiscuous mode, and in
order to avoid the expiry of RA information, must stay in the
promiscuous mode.
See the more detailed report below.
2.6.14-1.1637_FC4.netdev.2 based on 2.6.14.2pre
-----------------------------------------------
orinoco 0.15rc3 (David Gibson <[EMAIL PROTECTED]>, Pavel Roskin <[EMAIL
PROTECTED]>, et al)
orinoco_cs 0.15rc3 (David Gibson <[EMAIL PROTECTED]>, Pavel Roskin <[EMAIL
PROTECTED]>, et al)
eth1: Hardware identity 0001:0001:0004:0000
eth1: Station identity 001f:0001:0008:0048
eth1: Firmware determined as Lucent/Agere 8.72
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:60:1D:F0:2F:A9
eth1: Station name "HERMES I"
eth1: ready
eth1: index 0x01: Vcc 5.0, irq 3, io 0x3100-0x313f
1) after reboot (card in slot), default route shows up, but does not
get renewed. After timer expiry, the expiry timer seems to wrap
around, and after a couple of seconds, the route is removed.
The router lifetime we use is 180 seconds. Once the timer goes to
zero, the next value appears to be "21334373". The last value that
shows before the route gets removed is "213342348", so 25 seconds
later:
default via fe80::20a:5eff:fe51:7d58 dev eth1 proto kernel metric 1024
expires 21334348sec mtu 1500 advmss 1440 metric 10 64
2) if card removed and reinserted, the route/address is not re-learned
unless running tcpdump while getting the advertisement.
a) sometimes the route expires (maybe because the card doesn't see
the next advertisements?), or
b) while sometimes, the route gets renewed fine.
2.6.14-1.1644_FC4.netdev.4 based on 2.6.14.3
--------------------------------------------
The same behaviour as before, except that I saw only behaviour 2.a)
and behaviour 2.a) with the exception that the route/address was
learned without tcpdump as well -- let's call this 2.c).
kernel-2.6.14-1.1644_FC4 (with orinoco_cs 0.15rc2)
--------------------------------------------------
I was able to see the behaviours b) and c).
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
