IPv6 in the enterprise

[Andrew Yourtchenko]

On Tue, Apr 19, 2011 at 3:50 PM, Asbjorn Hojmark - Lists
<lists at hojmark.org> wrote:
>> I don't understand what the benefits are of then using a GUA a
>> default gateway address on the end-nodes is.
>
> In practice, pinging a link-local address can be difficult for the end-users.
>
> A Windows user, for example, can't just "ping fe80::1" if he has multiple interfaces (most do). >They have to enter something like "ping fe80::1%10" and you won't know in advance which >interface number the end-user has to ping. The same goes for ping6 on a Linux machine, where >you can't just "ping6 fe80::1" but have to do something like "ping6 -I eth2 fe80::1".

What about something like the below impro:

ping6 `ip -6 route | grep default | awk '{ print fe80::1"%"$5; }'`

Warning: no error check for existence and uniqueness of the default
route - but with a bit of work should be possible to have "ping
default gateway" type of wrapper for ping6.

This makes me think - probably a bit of work with powershell (assuming
win7) could alleviate the problem on Windows as well ?

>
> If you have to guide the end-user through finding the correct link-local interface to ping from, you might as well (and IMO easier) guide them through pinging a GUA, which you know in advance.

How about push the automation script to them during the install ? and
then "Could you do Windows-R and type 'pang' there ?" (the name seems
to be not used for any command, so I gratuitously hijacked it for the
example)

Curious if that could be a workable scenario IRL from the support standpoint.

cheers,
andrew

>
> Just my 2 cent.
>
> -A
>
>