Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 426979 - TAHI--DNSv6--TN can't Receive SYN Packet
TAHI--DNSv6--TN can't Receive SYN Packet
Status: CLOSED DUPLICATE of bug 428446
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: bind (Show other bugs)
All Linux
urgent Severity medium
: rc
: ---
Assigned To: Adam Tkac
Depends On:
Blocks: 253764
  Show dependency treegraph
Reported: 2007-12-29 02:37 EST by Zhiyong Wu
Modified: 2013-04-30 19:37 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-14 05:00:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Zhiyong Wu 2007-12-29 02:37:00 EST
Description of problem:

  When having DNSv6 tests in the server mode,we found that TN can't Receive SYN

Version-Release number of selected component (if applicable):


Software Environment:   
TAHI package:    

How reproducible:
  every time

Steps to Reproduce:    
  1. Configure TAHI test environment.     
  2. Run the TAHI test suite     
  3. After the test completes, check for the results 
Actual results:

   TN can't Receive SYN Packet.

Expected results:

   TN can Receive SYN Packet.

Additional info:
   please refer to

   NUT is set to be the client mode


   (1) 89	Returning of answer

   (2) 91	Priority comparison

   (3) 92	Priority comparison (round-robin)

   (4) 93	Weight comparison
Comment 1 RHEL Product and Program Management 2007-12-30 18:54:39 EST
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 3 Adam Tkac 2008-01-11 05:09:28 EST
I've started testing (by hand, of course) of problem 1 (Returning of answer) and
found some strange configuration mistakes.
Machine 1: IPV6tester, FreeBSD,
Machine 2: IPv6testee, RHEL 5.1,

First, network configuration (from
should have this topology:

Machine 1: IPv6 addr 3ffe:501:ffff:101::20
                      router 3ffe:501:ffff:100::1
Machine 2: IPv6 addr 3ffe:501:ffff:100:XXXX

Machine 2 has correct configuration (ifconfig eth0 says inet6
3ffe:501:ffff:100:21a:a0ff:febd:5d1/64) but I'm pretty unsure about machine 1.
It doesn't have any IPv6 address assigned. Also I'm not able ping6 router.
Please tell me if network configuration is set as expected. Looks it isn't for me.
Comment 4 Adam Tkac 2008-01-14 05:00:45 EST

*** This bug has been marked as a duplicate of 428446 ***
Comment 5 Zhiyong Wu 2008-01-14 05:30:28 EST
Machine 1: IPV6tester, FreeBSD,
Machine 2: IPv6testee, RHEL 5.1,

(1) the two interfaces is not used for testing DNSv6, but used for your remotely 


(2) the two interfaces used for testing DNSv6 are rl0( freebsd6.2)
and eth0 ( rhel5.1)

(3) the topology above is a logical topology, TAHI test suites will create it 


note that the network configuration you saw last time is used for IPv6 DNS test.

now, you can login IPV6tester by ssh and IPV6testee by ssh, and look at the ipv6 DNS test environment. 
Comment 6 Zhiyong Wu 2008-01-14 05:40:47 EST
the two interfaces used for ipv6 DNS test are:

Machine 1: IPV6tester, FreeBSD, rl0 ,
Machine 2: IPv6testee, RHEL 5.1, eth0,

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