Thanks, Vit.
In addition, we have two testing platforms - v6eval and koi.
v6eval only uses serial line to control remote target,
but koi can also use ssh or telnet.
Jaskiran,
which test do you want to test?
For DNS test, the platform must be koi.
Then you can skip to prepare serial connection.
But If you want to test for example IPv6 Core Protocols or IPsec,
you must use v6eval as the platform.
In this case, you must prepare serial connection.
Thanks,
On Wed, 10 Dec 2008 08:41:04 +0100
Vit Pelcak <vpelcak@suse.cz> wrote:
> JASKIRAN DHINGRA napsal(a):
> >
> > Hello all:
> >
> > I am new user to Tahi Project so have few Queries,kindly clear it :-
> >
> > In our lab we have two PC one as DNS server and other as client,we
> > have to implement IPv6 scheme to our packets from client to server and
> > we also need to run Tahi automation test suite to see whether all
> > configurations are working and also whether our server is acting as a
> > proper router or not
> >
>
> It is all described in readmes. You need to have at least one ethernet
> card on each machine (depending on what and which OS do you want to
> test) to be connected.
>
> On one machine TN (tester node) you need FreeBSD installed (personally,
> I use FreeBSD 7.0) and on the second machine NUT (node under test), you
> need OS you want to test.
>
> v6eval and test sets would be installed and run on TN and configured
> according provided readme files.
>
> Then just enter directory where you have test sets unpacked (or
> installed, see readmes) and run "make test" or something else (see
> readme and makefiles).
>
> > so kindly explain us as we setup the hardware in the lab" what is the
> > need of serial line communication between tester and target", which i
> > have seen in the PDF explaining about how to setup Tahi test tool in
> >
> > http://www.tahi.org/conformance/doc/tool-2.3/v6eval-e.pdf
> >
>
> Serial connection is needed to automate process of testing. You can live
> without it, but doing everything manually is pain.
>
> During tests it is needed to perform several actions on NUT repeatedly
> (ie. restart computer and so), and as these tests take several hours,
> you'd be asked to restart PC some hundred times, disable or enable
> something and so.
>
> Serial console allows you to automate this. If you use proper "remotes",
> these can perform automatic login to NUT and run needed commands.
> So you just let those tests work overnight and when you return to work,
> you have all results.
>
> I _strongly_ suggest to use serial console.
>
> > can we prepare the setup without this serial line communication and
> > only by using ethernet lan cables.?
> >
>
> Actually, yes. I'd suggest serial, but using Lan will work, too.
> Generally in same manner. You just need proper remotes to be used.
>
> > can you please send us some link explaining more about hardware setup
> > in the lab
> >
>
> Everything is described in readmes. You need at least 1 ethernet (see
> readme for test set, as these vary) and either serial or one more
> eternet for sending commands to NUT. That is why I make just some
> generic suggestions as tests simply vary and I don't remember all settings.
>
> > thanks
> >
> > Regards
> >
> > Jaskiran Dhingra
> >
>
> Regards
> Vit Pelcak
>
>
>
--
Yukiyo Akisada <akisada@tahi.org>