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
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 from our manual pages, we'd like
to improve
On 06.07.2016 17:41, Thomas Haller wrote:
> On Wed, 2016-07-06 at 16:45 +0200, poma wrote:
>> On 18.06.2016 14:36, Chris Laprise wrote:
>>
>> [...]
>>
>>> Is there more of a consensus now on this issue?
>>>
>>> My last attempt at using NM 1.2 with wpas 2.4 and iwlwifi driver
>>> (which
>>>
On Wed, 2016-07-06 at 16:45 +0200, poma wrote:
> On 18.06.2016 14:36, Chris Laprise wrote:
>
> [...]
>
> > Is there more of a consensus now on this issue?
> >
> > My last attempt at using NM 1.2 with wpas 2.4 and iwlwifi driver
> > (which
> > supposedly uses nl80211) resulted in NM saying it
On 18.06.2016 14:36, Chris Laprise wrote:
[...]
> Is there more of a consensus now on this issue?
>
> My last attempt at using NM 1.2 with wpas 2.4 and iwlwifi driver (which
> supposedly uses nl80211) resulted in NM saying it couldn't turn
> randomization on.
>
> If I compile the latest NM
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
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 24.05.2016 18:18, poma wrote:
> [...]
>
> However working Association / Connection random MAC address only applies to
> the:
> 1. wpa_supplicant (Client) -> wpa_supplicant (Hotspot)
> 2. wpa_supplicant (Client) -> NetworkManager (Hotspot)
>
> but not for:
> 3. NetworkManager (Client) ->
On 25.05.2016 16:56, 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
>>>
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 MAC address before it
[...]
However working Association / Connection random MAC address only applies to the:
1. wpa_supplicant (Client) -> wpa_supplicant (Hotspot)
2. wpa_supplicant (Client) -> NetworkManager (Hotspot)
but not for:
3. NetworkManager (Client) -> NetworkManager (Hotspot)
On 24.05.2016 16:46, poma wrote:
> On 24.05.2016 13:22, poma wrote:
>>
>> [...] NetworkManager [...]
>>
>> WPA Supplicant comparative test
>> - wpa_supplicant v2.6-devel git a26c9c2 2016-05-20
>> - Linux 4.6
>> - QEMU emulator version 2.6.0 (Hotspot)
>>
>>
>> Pre-association / Scanning random MAC
On 24.05.2016 13:22, poma wrote:
>
> [...] NetworkManager [...]
>
> WPA Supplicant comparative test
> - wpa_supplicant v2.6-devel git a26c9c2 2016-05-20
> - Linux 4.6
> - QEMU emulator version 2.6.0 (Hotspot)
>
>
> Pre-association / Scanning random MAC address
>
> = Client (mt7601u) =
>
> #
[...] NetworkManager [...]
WPA Supplicant comparative test
- wpa_supplicant v2.6-devel git a26c9c2 2016-05-20
- Linux 4.6
- QEMU emulator version 2.6.0 (Hotspot)
Pre-association / Scanning random MAC address
= Client (mt7601u) =
# grep -v '^#\|^$' /etc/wpa_supplicant.conf
> So, you had the right version of wpa-supplicant but it didn't work?
> Could you send a logfile of NM with TRACE logging enabled?
>
>
>
It looks like the logging level is set to info by default.
>> As a side comment, If I use the "unsupported" wpa_supplicant version
>> (ie
>> the last stable),
On Sun, 2016-05-22 at 15:43 +0200, fo...@sciunto.org wrote:
> Hi Thomas,
Hi,
> > Oh, I didn't actually test mac-addr-randomization myself :)
> > I am definitely interested whether it works for you (but I still
> > expect
> > it works, if wpa-supplicant has support).
> I made further test with
Hi Thomas,
> Oh, I didn't actually test mac-addr-randomization myself :)
> I am definitely interested whether it works for you (but I still expect
> it works, if wpa-supplicant has support).
I made further test with another computer, but same OS. I got the same
behavior, ie I couldn't randomize
On 21.05.2016 01:03, poma wrote:
> On 20.05.2016 19:36, Dan Williams wrote:
>> On Fri, 2016-05-20 at 19:03 +0200, poma wrote:
>>> On 19.05.2016 12:22, Thomas Haller wrote:
On Thu, 2016-05-19 at 01:41 +0200, poma wrote:
>
> On 18.05.2016 16:49, Thomas Haller wrote:
>>
>>
On 20.05.2016 19:36, Dan Williams wrote:
> On Fri, 2016-05-20 at 19:03 +0200, poma wrote:
>> On 19.05.2016 12:22, Thomas Haller wrote:
>>>
>>> On Thu, 2016-05-19 at 01:41 +0200, poma wrote:
On 18.05.2016 16:49, Thomas Haller wrote:
>
>
I actually have a question for you,
On Fri, 2016-05-20 at 19:03 +0200, poma wrote:
> On 19.05.2016 12:22, Thomas Haller wrote:
> >
> > On Thu, 2016-05-19 at 01:41 +0200, poma wrote:
> > >
> > > On 18.05.2016 16:49, Thomas Haller wrote:
> > > >
> > > >
> > > I actually have a question for you, and Lubo;
> > >
> > > In the
On 19.05.2016 12:22, Thomas Haller wrote:
> On Thu, 2016-05-19 at 01:41 +0200, poma wrote:
>> On 18.05.2016 16:49, Thomas Haller wrote:
>>>
>> I actually have a question for you, and Lubo;
>>
>> In the wpa_supplicant, Pre-association MAC random-ization is disabled
>> per default:
>>
>>
On Sun, 2016-05-15 at 22:36 +0200, fo...@sciunto.org wrote:
> Thank you Thomas for you quick reply.
>
>
> >
> > When you run wpa-supplicant via NetworkManager, NM configures the
> > supplicant via D-Bus. While /etc/wpa_supplicant/wpa_supplicant.conf
> > still is used (depending on your
On Thu, 2016-05-19 at 01:41 +0200, poma wrote:
> On 18.05.2016 16:49, Thomas Haller wrote:
> >
> I actually have a question for you, and Lubo;
>
> In the wpa_supplicant, Pre-association MAC random-ization is disabled
> per default:
>
> https://w1.fi/cgit/hostap/tree/doc/dbus.doxygen#n964
>
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 18.05.2016 16:49, Thomas Haller wrote:
> On Wed, 2016-05-18 at 01:36 +0200, 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
On Wed, 2016-05-18 at 11:21 -0400, Chris Laprise wrote:
>
> 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
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 Wed, 2016-05-18 at 01:36 +0200, 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,
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:
>> Hi,
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 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
get
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
setting for
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
>> setting for this in nmcli or the
Thank you Thomas for you quick reply.
> When you run wpa-supplicant via NetworkManager, NM configures the
> supplicant via D-Bus. While /etc/wpa_supplicant/wpa_supplicant.conf
> still is used (depending on your configuration), I don't think it
> matters nor is does it sound right to do.
OK, so
On Sun, 2016-05-15 at 19:28 +, François Boulogne wrote:
> Hi,
Hi,
> I also tried on my side and it didn't work. Here are the details. I'm
> using
> archlinux and I compiled wpa_supplicant from git (cloned today). I'm
> using
> networkmanager 1.2.2.
>
> In
Hi,
I also tried on my side and it didn't work. Here are the details. I'm using
archlinux and I compiled wpa_supplicant from git (cloned today). I'm using
networkmanager 1.2.2.
In /etc/wpa_supplicant/wpa_supplicant.conf, I turned the options (mac_addr
(x2) and preassoc_mac_addr) to 1 or 2.
For
On 13.05.2016 17:37, Chris Laprise wrote:
>
>
> 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
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 applet. I
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 applet. I found a reference to a
> setting on
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 applet. I
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 applet. I found a reference to a
> setting on
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 applet. I found a reference to a
> setting on
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:
43 matches
Mail list logo
