Nope!
That was one of the alternatives I was considering. So that's the
answer, issue the series of pings from the NUT?
Thanks for the quick response, Jon, and congratulations on your
successful tests.
-Brett
Jon_Franklin@Dell.com wrote:
> Are you issuing this from the NUT (your device being tested)?
>
> --
> Jon Franklin
> jon_franklin@dell.com
> x3-8143
> -----Original Message-----
> From: Brett.Lee@Sun.COM [mailto:Brett.Lee@Sun.COM]
> Sent: Friday, July 31, 2009 8:38 AM
> To: users@tahi.org
> Subject: [users:01268] Self_Test - Path MTU - Interface Question
>
> Hello,
>
> Am running Self_Test 4-0-5, and have a question with:
>
> Section 4: RFC 1981 - Path MTU Discovery for IPv6
> Test Case 15: Multicast Destination - One Router
>
> As part of executing the test case, I am being prompted to issue a ping
> command:
>
> ping6> Press enter key, and excute the following commands within 5
> seconds.
> ping6> Do ``ping6 DataSize= 1452, Send Count= 1, Interface= lnc0,
> Destination= FF1E::1:2''
>
> After pressing ENTER, attempts to execute this command from the test
> node result in an error:
>
> # ping6 -s 1452 -c 1 -I lnc0 FF1E::1:2
> ping6: lnc0: invalid interface name
>
> Have also tried an alternate execution of the command, substituting
> "lnc0" with "fxp1" (the physical interface for that link), but as "fxp1"
>
> has IPv6 disabled (per the v6eval instructions), that attempt fails
> also.
>
> # ping6 -s 1452 -c 1 -I lnc0 fxp1::1:2
> ping6: hostname nor servname provided, or not known
>
> # ifconfig fxp1
> fxp1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
> 1500
> options=8<VLAN_MTU>
> ether 00:06:5b:39:75:0b
> media: Ethernet autoselect (100baseTX)
> status: active
>
> Do I need to configure "lnc0" to support multicast?
> What am I missing?
>
> Thanks in advance, -Brett
>
>
>
>