Bug 705303 - [TAHI][IPv6][Core-router] Failed on tahi test "Part J: NUT receives valid DAD NS (contains TLL)"
Summary: [TAHI][IPv6][Core-router] Failed on tahi test "Part J: NUT receives valid DAD...
Keywords:
Status: CLOSED DUPLICATE of bug 705293
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jiri Benc
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-17 10:30 UTC by xhu
Modified: 2011-11-14 21:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-14 21:23:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description xhu 2011-05-17 10:30:17 UTC
Description of problem:
Failed on tahi test "Part J: NUT receives valid DAD NS (contains TLL)"

The test description can be seen in http://focus.bne.redhat.com/~xhu/Core-Router/Conform/RHEL5u7-beta/Self_Test_5-0-0-Router-RHEL5.7beta-20110516/addr.p2/LLA_DAD_NSPostDAD_wTLL.html

The test log can be seen in http://focus.bne.redhat.com/~xhu/Core-Router/Conform/RHEL5u7-beta/Self_Test_5-0-0-Router-RHEL5.7beta-20110516/addr.p2/15.html

The test tcpdump file can be seen in http://focus.bne.redhat.com/~xhu/Core-Router/Conform/RHEL5u7-beta/Self_Test_5-0-0-Router-RHEL5.7beta-20110516/addr.p2/15_html_Link0.pcap and http://focus.bne.redhat.com/~xhu/Core-Router/Conform/RHEL5u7-beta/Self_Test_5-0-0-Router-RHEL5.7beta-20110516/addr.p2/15_html_Link1.pcap

Version-Release number of selected component (if applicable):
kernel-2.6.18-261.el5

How reproducible:
everytime

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Failed on tahi test "Part J: NUT receives valid DAD NS (contains TLL)"

Expected results:
Tahi test "Part J: NUT receives valid DAD NS (contains TLL)" should be pass

Additional info:

Comment 1 Jiri Benc 2011-11-14 21:23:55 UTC

*** This bug has been marked as a duplicate of bug 705293 ***


Note You need to log in before you can comment on or make changes to this bug.