Date: Wed, 10 Dec 2008 09:15:40 +0100 From: Vit Pelcak <vpelcak@suse.cz> Subject: [users:01024] Re: Help regarding IPv6 Conformance Test setup using TAHI To: users@tahi.org Message-Id: <493F7AAC.50101@suse.cz> In-Reply-To: <eb5694890812092100s475d00b7o470d858c49ff731a@mail.gmail.com> References: <eb5694890812092100s475d00b7o470d858c49ff731a@mail.gmail.com> X-Mail-Count: 01024Shashank Sharma napsal(a): > Hi All, > > I'm new to the TAHI project and require it for IPv6 conformance test. > > Following are specifications of the resources used: > OS : FreeBSD 6.3-RELEASE for Tester interface and Fedora 8 for the > Network Under Test. Good. I did test Linux, too. > IPv6 Conformance Test Tool : v6eval3.1.1 Latest is v6eval-3.1.0 ;-) http://www.tahi.org/release/ > IPv6 Conformance Test Suite : Test Specification: 4.0.2 Do you speak about SelfTest? http://www.tahi.org/logo/phase2-core/ I did pass these tests 100% on Linux as Client. See: http://qa.suse.cz/vpelcak/ipv6ready/ Only one failure occurred in dhcpv6 testing, but this single test was then run separately and manually and passed: http://qa.suse.cz/vpelcak/dhcpv6-p2-sles11-b5-64/rfc3315/index.html If you wish, I can help you quite a lot. I'm planning to write some howto for Linux. It is fairly easy. But for setup of FreeBSD there is extensive readme which contains everything. > > In the v6eval specification it is mentioned the use of serial > communication between the Target and Tester. > I'm not clear with this serial communication requirement in Ipv6 > testing. Is there a way that we can avoid this or > its mandatory. Kindly, tell me the usage of serial communication in > test setup. Serial is great asset. Really. You don't want to run all those tests manually. Believe me. Lan can substitute serial however, but why would you do this when you have in attachment of my email premade scripts and configs for your tests ;-) First you must install v6eval of course. Follow readme of v6eval and used test set and nothing should surprise you. linux-v6.tar.bz2 unpack to /usr/local/v6eval/bin *.def belongs to /usr/local/v6eval/etc and need to be modified according your settings (type, password for root, hostname and MAC addresses of eth interfaces in nut.def, tn.def will be perhaps kept as it is, only RemoteDevice could differ and interface names (but not MAC addresses, keep those as these are) for Link0 and 1 will perhaps be different (see ifconfig)). Test serial connection in minicom ran from TN. Also keep in mind that you need cross connected ethernet cable to connect those 2 PCs. Also, take _special_ care that you connect interfaces Link0 and Link1 mentioned in tn.def with appropriate interfaces Link0 and Link1, otherwise tests will fail as wrong interfaces will be used communicate. V6evalremote.pm put to /usr/local/lib/perl5/site_perl/5.8.8 Perhaps you will have different version of perl. Then replace old V6evalRemote.pm with one provided by me. I hope it is enough. For start make this working and at least few tests pass. If you wish, you can contact me by jabber: belisarivs@njs.netlab.cz Just keep in mind that I'm in GMT+1 time zone. Regards Vit Pelcak > Thanks & Regards, > > Shashank Sharma > Engineer > Hughes Systique Corporation > D - 8, Infocity II, Sector 33, > Gurgaon, Haryana - 122022 > Tel: +91-124-3045400 (ext: 2418) > +91 9899912081 > Email: shashank.sharma@hsc.com <mailto:shashank.sharma@hsc.com> > www.hsc.com <http://www.hsc.com>1024_2.txt (attatchment)(tag is disabled)
1024_3.txt (attatchment)(tag is disabled)
attatchment (application/x-perl) ignored1024_5.bz2