Re: unsecured networks

Hello Mr. Haller,

thank you very much for your response!

Yes, checking my web-browser date let me confirm that those login-pages set several cookies. However I can't confirm if they responsible for the connection fails. Those cookies was set from networks from hotels I resident during the last weeks and I am now in another hotel and didn't connect to it's Wifi-network so far. (I stopped accessing the network without entering an username or password as soon as I saw that it also use a "captive portal" for seeking help first. Now a strange thing happened: After reading your message did I tried to connect to the network today. But than the same behavior again: without that the portal popping up does network-manager try directly to connect to the network. Also network-managers GUI shows a clear-sign and Gnome shows me the signal-strength like the connection would be fully established.

On 03/10/2018 at 9:14 PM, "Thomas Haller" <thaller redhat com> wrote:
On Wed, 2018-10-03 at 20:19 +0200, live--- via networkmanager-list
> Hello NM-community,
> firth of all: thank you for this feature-rich networking tool, so far
> did it never missed my needs!
> However did I run into huge problems since I am working on changing
> locations and need to connect into unsecured wifi-networks that use a
> web-based login-page (sometimes you have to enter a username and
> password sometimes you just need to press a bottom to confirm to the
> Terms of Usage). In any way, I can login to those networks to the
> firth time and use it without any problems. But after some time I got
> disconnected or turned off the laptop and from this moment on was I
> complete unable to connect to those networks again. Even the "forget
> network" function inside the history doesn't changed anything. Can
> this be related to that I use '''wifi.cloned-mac-address=random''' to
> randomly change my mac-addresses on every new connection?


it is quite possible that such a login-page (captive portal) would
recognize you base on the MAC address. So, if you change the MAC
address, you would need to re-authenticate.

If you subsequently fail to re-authenticate, then it's unclear why the
login-page would be have that way. Maybe it stores a cookie in your
browser and does not like you changing the MAC address? That seems a
bit unusual though.

I wouldn't expect that deleting and re-creating the connection profile
in NetworkManager would help here.

Note there is "wifi.cloned-mac-address=stable" which precisely exists
to give you a scrambled MAC address but also control of when it
changes. The "stable" goes together with "connection.stable-id", see
`man nm-settings` and [1].



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]