https://bugs.kde.org/show_bug.cgi?id=464245

SolidTemperature0 <i6ic...@mailezee.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
                 CC|                            |i6ic...@mailezee.com
     Ever confirmed|0                           |1

--- Comment #1 from SolidTemperature0 <i6ic...@mailezee.com> ---
Adding the setting "wifi.cloned-mac-address=random" makes so that each
connection gets a different mac address each time you connect. It would
definitely be useful if such setting could be set in a GUI. It also supports
the option "stable" that create a random mac address for each connection only
once. In general, the features that I'd like to see would be:
1. A setting for enable and disable random mac address when scanning
("wifi.scan-rand-mac-address=yes")
2. A setting for enable random mac from wifi and ethernet connections (with
settable mask, so that if someone wants they can force a specific vendor for
example), for both "random" e "stable" options.
2.1 If such a setting it's enable it should be noticeable also in the setting
of a specific connection where you could:
    a) randomize again the mac address if you want (if cloned-mac-address is
both "random" or "stale")
    b) change/add a mask for the randomization of that specific connection (if
the "stale" setting is enable or the automatic randomization is disable then
you should also suggest the user the generate a new mac
    c) enable the randomization for that newtork if disbaled (both "stale" and
"random" option should be available), disable the randomization for that
specific connection if enable (and show also the real mac address that is used)
and switch from "stale" and "random" setting for that specific connection.
   d) in the cases of b) and c), if something different from the default option
is selected, then it should somehow be highlighted.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to