Hi Zhou,
I don't know about network card driver 8139too.
In my case, fedora8 with dm9601 driver had problem.
You try promiscuous mode using tcpdump on the system with the problem.
And you might find the system log related information.
Shirley Zhou $BeaJe#sea(I/$Bk{(I8$Bea:e"@eaNe"!(B:
> Hi, Ozoe
>
> My NUT is fedora 11-i386, and TN is FreeBSD6.3.
> My network card driver is 8139too,output of ifconfig test network card.
>
> [root@host-test ~]# ifconfig
> eth1 Link encap:Ethernet HWaddr 00:21:27:9D:F5:69 inet
> addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::221:27ff:fe9d:f569/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:35 errors:0 dropped:0 overruns:0 frame:0
> TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:4531 (4.4 KiB) TX bytes:10070 (9.8 KiB)
> Interrupt:18 Base address:0x4f00
> Any I missed?
>
> Thanks a lot!
>
> Ozoe Nobumichi wrote:
>> Hi Zhou,
>>
>> Please let me know your test environment in detail.
>>
>> I have the experience that the multicast group address
>> (33:33:00:01:00:03)frame was dropped with a certain USB network I/F.
>>
>> Shirley Zhou $BeaJe#sea(I/$Bk{(I8$Bea:e"@eaNe"!(B:
>>> I test the same case in another system, it pass.
>>>
>>> tcpdump file is :
>>>
>>> 19:18:17.354280 IP6 fe80::200:ff:fe00:a6a6 > ff02::1: ICMP6, router
>>> advertisement, length 56
>>> 19:18:20.381821 IP6 fe80::218:8bff:fe74:2ee7 >
>>> fe80::200:ff:fe00:a2a2: ICMP6, neighbor solicitation, who has
>>> fe80::200:ff:fe00:a2a2, length 32
>>> 19:18:21.381789 IP6 fe80::218:8bff:fe74:2ee7 >
>>> fe80::200:ff:fe00:a2a2: ICMP6, neighbor solicitation, who has
>>> fe80::200:ff:fe00:a2a2, length 32
>>> 19:18:22.381601 IP6 fe80::218:8bff:fe74:2ee7 >
>>> fe80::200:ff:fe00:a2a2: ICMP6, neighbor solicitation, who has
>>> fe80::200:ff:fe00:a2a2, length 32
>>> 19:18:42.885969 IP6 fe80::218:8bff:fe74:2ee7 > ff02::16: HBH ICMP6,
>>> multicast listener report v2, 2 group record(s), length 48
>>> 19:18:43.017195 IP6 3ffe:501:ffff:100:200:ff:fe00:a4a4.dhcpv6-server
>>> > ff05::1:3.dhcpv6-server: dhcp6 relay-fwd
>>> 19:18:43.017838 IP6 fe80::218:8bff:fe74:2ee7 > ff02::1:ff00:a4a4:
>>> ICMP6, neighbor solicitation, who has
>>> 3ffe:501:ffff:100:200:ff:fe00:a4a4, length 32
>>> 19:18:43.112344 IP6 3ffe:501:ffff:100:200:ff:fe00:a4a4 >
>>> fe80::218:8bff:fe74:2ee7: ICMP6, neighbor advertisement, tgt is
>>> 3ffe:501:ffff:100:200:ff:fe00:a4a4, length 32
>>> 19:18:43.112522 IP6 fe80::218:8bff:fe74:2ee7.dhcpv6-server >
>>> 3ffe:501:ffff:100:200:ff:fe00:a4a4.dhcpv6-server: dhcp6 relay-reply
>>> 19:18:43.742923 IP6 fe80::218:8bff:fe74:2ee7 > ff02::16: HBH ICMP6,
>>> multicast listener report v2, 2 group record(s), length 48
>>>
>>> Can anyone point me what is the problem?
>>> Thanks.
>>> Shirley
>>>
>>> Shirley Zhou wrote:
>>>> Hi, All
>>>>
>>>> I am testing DHCPv6 server using DHCPv6_Self_Test_P2_1_0_17.
>>>> I found there is no relay reply message for relay-forward message.
>>>> I take RFC3315, case 12-Part B:Relay Agent/Server Message Format as
>>>> example, can anyone tell me how to resolve this problem? Thanks in
>>>> advance!
>>>> dhcp6s.conf
>>>>
>>>> prefer-life-time 10000;
>>>> valid-life-time 20000;
>>>> renew-time 5000;
>>>> rebind-time 16000;
>>>> #
>>>> interface eth0 {
>>>> link AAA {
>>>> #
>>>> #
>>>> #
>>>> #
>>>> relay 3ffe:501:ffff:101::/64;
>>>> range 3ffe:501:ffff:101::10 to 3ffe:501:ffff:101::11/64;
>>>> #
>>>> };
>>>> host host0 {
>>>> duid 00:01:00:01:00:04:93:e0:00:00:00:00:a2:a2;
>>>> };
>>>> };
>>>>
>>>> tcpdump file
>>>>
>>>> 18:43:44.729556 IP6 fe80::200:ff:fe00:a6a6 > ff02::1: ICMP6, router
>>>> advertisement, length 56
>>>> 18:43:47.645937 IP6 fe80::221:27ff:fe9d:f569 >
>>>> fe80::200:ff:fe00:a2a2: ICMP6, neighbor solicitation, who has
>>>> fe80::200:ff:fe00:a2a2, length 32
>>>> 18:43:48.645998 IP6 fe80::221:27ff:fe9d:f569 >
>>>> fe80::200:ff:fe00:a2a2: ICMP6, neighbor solicitation, who has
>>>> fe80::200:ff:fe00:a2a2, length 32
>>>> 18:43:49.646068 IP6 fe80::221:27ff:fe9d:f569 >
>>>> fe80::200:ff:fe00:a2a2: ICMP6, neighbor solicitation, who has
>>>> fe80::200:ff:fe00:a2a2, length 32
>>>> 18:43:49.960096 IP6 fe80::221:27ff:fe9d:f569 > ff02::16: HBH ICMP6,
>>>> multicast listener report v2, 2 group record(s), length 48
>>>> 18:44:09.918475 IP6 fe80::221:27ff:fe9d:f569 > ff02::16: HBH ICMP6,
>>>> multicast listener report v2, 2 group record(s), length 48
>>>> 18:44:10.081407 IP6 3ffe:501:ffff:100:200:ff:fe00:a4a4.dhcpv6-server
>>>> > ff05::1:3.dhcpv6-server: dhcp6 relay-fwd
>>>> 18:44:19.216140 IP6 fe80::221:27ff:fe9d:f569 > ff02::16: HBH ICMP6,
>>>> multicast listener report v2, 2 group record(s), length 48
>>>> 18:44:35.752330 IP6 fe80::221:27ff:fe9d:f569 > ff02::16: HBH ICMP6,
>>>> multicast listener report v2, 2 group record(s), length 48
>>>>
>>>> Shirley Zhou
>>>>
>>>>
>>>
>>>
>>
>>
>
>
--
--
Nobumichi Ozoe
System & Control Research Center,
Corporate R&D Headquaters,
Yokogawa Electric Corporation
Tel: +81-422-52-5544 Fax: +81-422-52-2561
http://www.yokogawa.com/