same SSID and different MAC same pass is not true usually
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Manager Applet |
Fix Released
|
Wishlist
|
|||
network-manager-applet (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Hello!,
Today I come to talk about a issue that I have been experiencing since I first installed Ubuntu. When you save a password, it is only saved with the AP name, and that's a good point for enterprises, but for particulars, going to several places you most of the times you end with a lot of APs, and some of them, have the same name. That is why I suggest having the option to declare each SSID as multi-access point (would be the actual configuration) or a single acces point (would be for domestic APs)
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: network-
ProcVersionSign
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelMo
Architecture: amd64
CRDA: Error: [Errno 2] No existe el fichero o el directorio
CheckboxSubmission: 81800d45f20c113
CheckboxSystem: b845c366ea09c60
Date: Wed Feb 2 17:08:12 2011
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IpRoute:
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.9 metric 2
169.254.0.0/16 dev eth1 scope link metric 1000
default via 192.168.1.1 dev eth1 proto static
Keyfiles: Error: [Errno 2] No existe el fichero o el directorio
ProcEnviron:
PATH=(custom, user)
LANG=es_ES.utf8
SHELL=/bin/bash
SourcePackage: network-
XsessionErrors:
(polkit-
(nautilus:2988): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nm-applet:2985): Gdk-CRITICAL **: IA__gdk_
Changed in network-manager-applet: | |
importance: | Unknown → Wishlist |
status: | Unknown → New |
Changed in network-manager-applet: | |
status: | New → Confirmed |
Changed in network-manager-applet: | |
status: | Confirmed → In Progress |
Changed in network-manager-applet: | |
status: | In Progress → Fix Released |
You could just change the name of the connection, and tie it to the BSSID you want to use in the connection properties. Does that work for your use case?