Hi,
Are you sure that all your nodes are running 10 Mbit or 100 Mbit ?
Will the hub get confused by a mixture of 10 and 100 Mbit cards? I have recently
seen a case like this (on NetBSD 1.5 sending NS).
Try using a cross-over cable between your router and each of your hosts - one at
a time. This will
isolate the case of the failure - in my case the hub...
regards
Palle
Francois Tigeot wrote:
> Hi,
>
> IPv6 autoconfiguration with -STABLE and Dlink DFE-550TX network adapters is
> not working as it should.
>
> My network topology is simple : 3 machines on the same ethernet segment,
> connected by a 10/100 hub. They are running 4.4-RC as of today and use the
> same NIC, a Dlink DFE-550TX (ste driver).
>
> Initialy running the 'rtsol ste0' command on a client machines did not give
> any result.
> I then tried to see what was going on on the wire by running tcpdump. This
> modified the behavior of the machine running it.
>
> Here are some tcpdump results observed after running a single 'rtsol' command
> on the client:
>
> Router and client interfaces in normal mode.
> traffic captured from an other machine on the same hub:
>
> 10:19:50.036 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:19:54.055 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:19:58.075 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
>
> Tcpdump running on the router.
> The router and an other machine on the wire show the same results:
>
> 10:20:42.590 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:20:42.882 fe80::250:baff:fe15:69fc > ff02::1: icmp6: router advertisement
> 10:20:46.609 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:20:46.742 fe80::250:baff:fe15:69fc > ff02::1: icmp6: router advertisement
> 10:20:50.629 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:20:50.802 fe80::250:baff:fe15:69fc > ff02::1: icmp6: router advertisement
>
> The client does not get configured.
>
> Tcpdump running on the client, router interface in normal mode
> The client and the observation machine show the same results:
>
> 10:22:04.575 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:22:08.595 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:22:12.615 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
>
> The client does not get configured.
>
> Tcpdump running on the client and the router.
> All three machines show the same results:
>
> 10:25:23.608 fe80::250:baff:fe71:bded > ff02::2: icmp6: router solicitation
> 10:25:24.083 fe80::250:baff:fe15:69fc > ff02::1: icmp6: router advertisement
> 10:25:24.084 :: > ff02::1:ff71:bded: icmp6: neighbor sol: who has [client]
>
> Here, the client machine gets configured.
>
> It seems that only the machines having their interface in promiscuous mode
> were able to receive the multicast datagrams. They then ran as they should
> have, which leads me to think the problem is not with the card itself.
>
> Is this a known problem with the ste driver ?
>
> How can I be sure the client does not receive the advertisement without
> running tcpdump ?
>
> Thanks in advance,
>
> Francois Tigeot
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
