Re: [v6ops] new draft: draft-vyncke-v6ops-ipv6-only-thin-clients

Le 29/06/2015 04:32, Mark ZZZ Smith a écrit :
>
> ------------------------------------------------------------------------
> *From:* Brian E Carpenter <brian.e.carpenter@gmail.com>
> *To:* v6ops list <v6ops@ietf.org>
> *Cc:* draft-vyncke-v6ops-ipv6-only-thin-clients@.ietf.org
> *Sent:* Sunday, 28 June 2015, 9:54
> *Subject:* Re: [v6ops] new draft: draft-vyncke-v6ops-ipv6-only-thin-clients
>
>  > 1.  Wake-on-Lan
> ...
>  >    for a specific host.  This is called the magic packet: with the
>  >    Ethernet payload having somewhere 6 bytes containing 0xFF followed by
>  >    16 times the network interface datalink-layer address.
>
> How is this going to work with surveillance-averse clients that change
> their MAC address from time to time? I think wake-on-lan is going to
> need a complete rethink (including IPv6, of course) because of this.
>
> / As I haven't worked on a network that uses WoL, I was thinking that it
> must already be pretty onerous to be maintaining a list of devices and
> their MAC addresses for WoL purposes.
>
> / There seem to be a number of other WoL methods; here are the list of
> WoL packet types/events that can be set using the Linux 'ethtool'
> utility for a NIC:
>
> --
>         wol p|u|m|b|a|g|s|d...
>                Sets Wake-on-LAN options.  Not all devices  support
>   this.   The
>                argument  to  this  option  is a string of characters
> specifying
>                which options to enable.
>
>                p   Wake on PHY activity
>                u   Wake on unicast messages
>                m   Wake on multicast messages
>                b   Wake on broadcast messages
>                a   Wake on ARP
>                g   Wake on MagicPacket™
>                s   Enable SecureOn™ password for MagicPacket™
>                d   Disable (wake on  nothing).   This  option
>                    clears all previous options.

That begs for an option 'n' Wake on ND.

Alex

>
>         sopass xx:yy:zz:aa:bb:cc
>                Sets  the  SecureOn™ password.  The argument to this
> option must
>                be 6 bytes in Ethernet MAC hex format (xx:yy:zz:aa:bb:cc).
> --
>
> / Looking at the WoL spec referenced, that looks to be the MagicPacket
> option mentioned above. Perhaps networks using WoL are using more coarse
> methods which would continue to work even with changing MAC addresses.
>
> / Regards,
> / Mark.
>
>
> It seems to me that to solve this *and* the PXE issue, there's going
> to end up being some requirement for the thin client to wake itself
> up periodically and execute some sort of discovery process. (Something
> we are going to need in the Anima WG, too, IMHO.)
>
> Regards
>    Brian
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org <mailto:v6ops@ietf.org>
> https://www.ietf.org/mailman/listinfo/v6ops
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>