Bug #9418

NetworkManager persistence feature does not save hidden Wi-Fi networks

Added by emmapeel 2015-05-17 10:37:09 . Updated 2015-08-13 02:33:55 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
2015-05-17
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

reported by user, haven’t been able to test it myself:

When Persistence configured to save network information, and while can save openly broadcasted wireless networks, NetworkManager cannot remember hidden networks from one session to the other.

Steps to reproduce
—————————

- Persistence enabled, with network.

- Connect to a Hidden wireless network with WPA2 personal, add password

- Restart
- Click on ‘Connect to Hidden network’

Description of the error
————————————
The network is not on the list. Credentials have to be entered again.

What should happen
—————————

Saved network appears on the list and password does not need to be entered again.

Subtasks

History

#1 Updated by intrigeri 2015-05-18 15:20:57

  • Assignee set to emmapeel
  • QA Check set to Info Needed

> When Persistence configured to save network information, and while can save openly broadcasted wireless networks, NetworkManager cannot remember hidden networks from one session to the other.

Please try to reproduce with Network Connections and GNOME Keyring persistence features enabled. (IIRC some of the NM persistence cannot possibly work without GNOME Keyring being persistent as well.)

#2 Updated by intrigeri 2015-06-10 18:03:01

emmapeel: ping?

#3 Updated by emmapeel 2015-06-11 08:50:58

  • Assignee deleted (emmapeel)

Sorry, I am still looking for some spare hardware on this one, is taking longer than expected. For the time being I deassign myself, though I will try to look for a router on the cemetery at home.

#4 Updated by intrigeri 2015-06-11 09:12:51

  • Assignee set to emmapeel

> Sorry, I am still looking for some spare hardware on this one, is taking longer than expected. For the time being I deassign myself, though I will try to look for a router on the cemetery at home.

No problem. Please reassign to another frontdesk person who can more easily test this, though (I’m concerned that such a ticket with no assignee will simply be forgotten, and it would be a shame if that’s a real bug).

#5 Updated by emmapeel 2015-06-13 09:42:09

  • Assignee changed from emmapeel to mercedes508

cheers mercedes508 for taking it!

#6 Updated by mercedes508 2015-06-18 14:59:01

  • Status changed from New to Confirmed
  • Assignee deleted (mercedes508)
  • Type of work changed from Test to Research

I was able to reproduce that bug.

Even if network-manager doesn’t seem to remember the hidden wireless network, it saved its settings from the first time I did connect. But yes, when trying for the second time to connect to that hidden network, I have to type again its name & password, as if it was the first time.

#7 Updated by intrigeri 2015-06-19 01:59:42

  • Assignee set to mercedes508

> I was able to reproduce that bug.

> Even if network-manager doesn’t seem to remember the hidden wireless network, it saved its settings from the first time I did connect. But yes, when trying for the second time to connect to that hidden network, I have to type again its name & password, as if it was the first time.

Thanks. A few more questions:

  • You had the “GNOME Keyring” persistence feature enabled, right?
  • If, during one single Tails session with persistence enabled for network connections and GNOME keyring, you successfully connect to a hidden network, and then disconnect, then can you reconnect without typing its name and password again?
  • Same question without persistence enabled.

#8 Updated by mercedes508 2015-06-19 05:47:25

> * You had the “GNOME Keyring” persistence feature enabled, right?

Yes.

> * If, during one single Tails session with persistence enabled for network connections and GNOME keyring, you successfully connect to a hidden network, and then disconnect, then can you reconnect without typing its name and password again?

Yes. And assuming my hidden network is called “hidden”, then network-manager even offer the possibility to connect to hidden, hidden1, hidden2. Which are actually the same network but according to their settings respectively correspond to the three different sesssions I connected to them.

> * Same question without persistence enabled.

Then I can reconnect without typing its name and password, but of course network-manager only propose one network called hidden.

#9 Updated by mercedes508 2015-06-19 05:47:47

  • Assignee changed from mercedes508 to intrigeri
  • QA Check changed from Info Needed to Dev Needed

#10 Updated by intrigeri 2015-06-30 12:11:18

  • Subject changed from Network Manager cannot save Hidden networks to NetworkManager persistence feature does not save hidden Wi-Fi networks
  • Category set to Persistence
  • Assignee deleted (intrigeri)
  • QA Check deleted (Dev Needed)

OK, we’re done with triaging this bug, then.

#11 Updated by karrer 2015-08-13 01:47:37

Dear Debuggers,

I still find this annoying bug even in the newest 1.5-version of tails.
Did I miss how to solve it? (Using persistence is necessary in my case).

Thank you for a short hint.
A. Karrer

#12 Updated by intrigeri 2015-08-13 02:33:55

> I still find this annoying bug even in the newest 1.5-version of tails.

Thanks for confirming.

> Did I miss how to solve it?

This bug is still open, and AFAIK there’s no known workaround nor proper solution yet.