Index: [Article Count Order] [Thread]

Date: Thu, 30 Oct 2008 18:25:37 +0000
From: "Tovey, Dwight (Adecco Tech - Boise)" <dwight.tovey@hp.com>
Subject: [users:00973] Re: DHCPv6 Self Test workaround
To: "users@tahi.org" <users@tahi.org>
Message-Id: <8C6EB8B07BAB2040BCAA8F162DEFCF1B1C4BF297EB@GVW1092EXB.americas.hpqcorp.net>
In-Reply-To: <4909CF41.7020608@suse.cz>
References: <4909CF41.7020608@suse.cz>
X-Mail-Count: 00973

 Vit -

The DHCPv6 enable/disable is controlled by the dhcp6c.rmt remote script (in /usr/local/v6eval/bin/<System_type>/dhcp6c.rmt).  You can replace that script with one that will do whatever you need in order to start/stop your DHCPv6 client.  It doesn't necessarily have to be a perl script either.  You can use whatever programming language you are most comfortable with (so long as it accepts the same parameters and returns the same status codes) to connect via the serial line and send the appropriate commands.

In my case, my NUT doesn't have a command shell, but instead uses an embedded web server to configure various parameter.  My dhcp6c.rmt is a python script that connects to the web server (over IPv4) and sets the appropriate flags to enable/disable DHCPv6.  I have my TN set up so that I can kick off a test run before I go home at night and it will run both the core protocol tests and the DHCPv6 tests with no user intervention.

        /dwight



> -----Original Message-----
> From: Vit Pelcak [mailto:vpelcak@suse.cz]
> Sent: Thursday, October 30, 2008 9:14 AM
> To: users@tahi.org
> Subject: [users:00972] DHCPv6 Self Test workaround
>
> Hi.
>
> I tried DHCPv6 Self Test 1.0.13. However, this testing suite
> is demanding too much user input.
>
> I mean, I usually let run those tests overnight, but DHCPv6
> Self test still asks for enabling or disabling DHCPv6.
>
> Is there any workaround to avoid this? I don't know how many
> tests from whole set requires this, but couldn't be done some
> workaround around this?
>
> I know that it depends on system on NUT but some basic
> construction, which could be then fixed for certain operating
> system by tester wouldn't help.
>
> If perl-Expect is used to communicate via serial, could also
> enabling and disabling be controlled over serial, too?
>
> At least, perl-Expect could login via serial and ask for
> disabling or enabling dhcp6 here. Tester (by this I mean
> someone who is performing testing, ie. me) could then easily
> replace text from screen by command which disables or enables
> dhcpv6 and everything is perfect.
>
> I'd do it by myself, but I have poor skills with perl and
> testsuite itself, so I would break it more than improve.
>
> Thank you for any ideas.
>
> Regards
> Vit Pelcak
>
>