Hi,
I just installed NetworkManager 1.2 in fedora 23 in the hopes that I can
get mac randomization working. Only problem is there's no sign of a
setting for this in nmcli or the applet. I found a reference to a
setting on the NetworkManager.conf manpage which states:
wifi.mac-address-
On 04/29/2016 09:07 PM, Thomas Haller wrote:
On Fri, 2016-04-29 at 16:09 -0400, Chris Laprise wrote:
Hi,
I just installed NetworkManager 1.2 in fedora 23 in the hopes that I
can
get mac randomization working. Only problem is there's no sign of a
setting for this in nmcli or the appl
On 05/12/2016 06:16 PM, Dan Williams wrote:
On Fri, 2016-04-29 at 16:09 -0400, Chris Laprise wrote:
Hi,
I just installed NetworkManager 1.2 in fedora 23 in the hopes that I
can
get mac randomization working. Only problem is there's no sign of a
setting for this in nmcli or the appl
On 05/16/2016 12:03 PM, poma wrote:
On 13.05.2016 00:16, Dan Williams wrote:
On Fri, 2016-04-29 at 16:09 -0400, Chris Laprise wrote:
Hi,
I just installed NetworkManager 1.2 in fedora 23 in the hopes that I
can
get mac randomization working. Only problem is there's no sign of a
settin
On 05/17/2016 07:36 PM, poma wrote:
On 16.05.2016 23:07, Chris Laprise wrote:
On 05/16/2016 12:03 PM, poma wrote:
On 13.05.2016 00:16, Dan Williams wrote:
On Fri, 2016-04-29 at 16:09 -0400, Chris Laprise wrote:
Hi,
I just installed NetworkManager 1.2 in fedora 23 in the hopes that I
can
On 05/18/2016 08:24 AM, poma wrote:
On 18.05.2016 06:14, Chris Laprise wrote:
On 05/17/2016 07:36 PM, poma wrote:
On 16.05.2016 23:07, Chris Laprise wrote:
On 05/16/2016 12:03 PM, poma wrote:
On 13.05.2016 00:16, Dan Williams wrote:
On Fri, 2016-04-29 at 16:09 -0400, Chris Laprise wrote
On 05/18/2016 02:25 PM, Dan Williams wrote:
Randomization happens in the supplicant, and the supplicant also
controls scanning. If randomization is enabled, the supplicant will
change the MAC address before it scans, so this should not be a
problem.
Of course, if you run 'iw dev wlan0 scan'
On 05/25/2016 10:56 AM, Dan Williams wrote:
On Wed, 2016-05-18 at 21:10 -0400, Chris Laprise wrote:
On 05/18/2016 02:25 PM, Dan Williams wrote:
Randomization happens in the supplicant, and the supplicant also
controls scanning. If randomization is enabled, the supplicant
will
change the
On 05/25/2016 10:56 AM, Dan Williams wrote:
NM always requests that non-associated scans (eg, before you've
connected to a wifi network) be randomized by default. You can
(through the mac randomization property) request that the association
address also be randomized.
You can also use the cl
On 08/30/2016 07:49 AM, Thomas Haller wrote:
Hi,
as a follow-up, I tried to explain the new options here:
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
Otherwise, our documentation should answer all your questions
-- if you don't understand something f
I am trying out the new NM in Debian testing by installing the
network-manager 1.4.0-3 and network-manager-gnome 1.4.0-2 versions from
unstable.
NM 1.4 shows up in the systray, but won't display any access points. It
does seem to be trying to manage the wifi device, as its MAC address now
ch
On 08/31/2016 01:16 PM, Thomas Haller wrote:
On Wed, 2016-08-31 at 12:07 -0400, Chris Laprise wrote:
I am trying out the new NM in Debian testing by installing the
network-manager 1.4.0-3 and network-manager-gnome 1.4.0-2 versions
from
unstable.
NM 1.4 shows up in the systray, but won
On 10/14/2016 12:43 PM, Thomas Haller wrote:
On Fri, 2016-10-14 at 11:00 -0400, Chris Laprise wrote:
On 08/31/2016 01:16 PM, Thomas Haller wrote:
On Wed, 2016-08-31 at 12:07 -0400, Chris Laprise wrote:
I am trying out the new NM in Debian testing by installing the
network-manager 1.4.0-3 and
On 11/06/2016 07:30 PM, Paul Swanson wrote:
Hello,
I've recently been configuring my Ubuntu 16.10 laptop for default
routing via VPN only and have discovered some difficulties.
My goal is to only connect to the Internet via a VPN and ensure that
DNS requests are resolved by a trusted server
On 11/07/2016 06:57 AM, Thomas Haller wrote:
Another thing is ensuring that all traffic is routed via the VPN (that
is, controlling the configured routes). That is not supported by NM
directly (besize that you can manually configure your underlying
connection to have no default-route and only gi
On 11/07/2016 01:49 PM, Stuart D. Gathman wrote:
Cool! I had not had time to find out exactly what qubes did, but you
explained it very well. I suspect that's not *all* qubes does, but
I'll be installing a prepackaged VM router (or hacking my own). What a
great
concept.
Yeah, Qubes really
e thoughts on this important subject from NM
developers...
1. A Study of MAC Address Randomization in Mobile Devices and
When it Fails
https://arxiv.org/pdf/1703.02874v1.pdf
--
Chris Laprise, tas...@openmailbox.org
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106
On 04/10/2017 01:35 PM, Chris Laprise wrote:
1. A Study of MAC Address Randomization in Mobile Devices and
When it Fails
https://arxiv.org/pdf/1703.02874v1.pdf
A listing of best practices from the paper:
Randomize across the entire address, providing
2^46 bits of randomization.
Use a
18 matches
Mail list logo