Re: Adhoc: IPV4 setting 'link-local'
On Wed, 2010-08-04 at 11:43 +0200, Simon Schampijer wrote: > Hi, > > creating a wireless adhoc network setting the property 'method' of the > setting 'ipv4' to 'link-local' does give me the following error: > "nm_device_wifi_set_mode(): error setting card wlan0 to mode 2: Device > or resource busy". So you see this error on *both* iwl3945 and liberatas_sdio, or just iwl3945? This is odd, but not completely expected; NM will only force-set the device back to infrastructure when deactivating. That's mostly historical as some older drivers couldn't scan well when in adhoc mode for some reason. > Using the property 'shared' does work fine. I have tested with nm-applet > (you can edit the properties of the network in the edits menu as > nm-applet set the property to 'shared' by default) and tried it from > sugar over the dbus interface, too. > > I see this behavior on one machine with the iwl3945 driver and on the > other machine using the libertas_sdio driver it does work fine, both > running the latest NM F11 release > NetworkManager-0.7.2.997-2.git20100609. So, the issue might be on the > driver side? What do others think? Looks like avahi-autoipd is being bitchy. Need to figure out why that is, but at the moment there isn't any log help for avahi-autoipd at all. Can you: mv /usr/sbin/avahi-autoipd /usr/sbin/avahi-autoipd.orig and put this into a script named /usr/sbin/avahi-autoipd: #!/bin/bash avahi-autoipd --debug --syslog $@ make sure you chmod 755 that script, then try the link-local connection again; you shouldn't need to restart NM. This should cause avahi to print out anything that's going wrong to /var/log/messages. Dan > Regards, > Simon > > > > --- Full output --- > > Aug 4 11:26:56 laptop NetworkManager: Activation > (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected > to wireless network 'mammamia'. > Aug 4 11:26:56 laptop NetworkManager: Activation (wlan0) Stage > 3 of 5 (IP Configure Start) scheduled. > Aug 4 11:26:56 laptop NetworkManager: Activation (wlan0) Stage > 3 of 5 (IP Configure Start) started... > Aug 4 11:26:56 laptop NetworkManager: (wlan0): device state > change: 5 -> 7 (reason 0) > Aug 4 11:26:56 laptop NetworkManager: Activation (wlan0) Stage > 3 of 5 (IP Configure Start) started avahi-autoipd... > Aug 4 11:26:56 laptop NetworkManager: Activation (wlan0) Stage > 3 of 5 (IP Configure Start) complete. > Aug 4 11:26:56 laptop NetworkManager: aipd_watch_cb(): wlan0: > avahi-autoipd exited with error code 1 > Aug 4 11:26:56 laptop NetworkManager: (wlan0): device state > change: 7 -> 9 (reason 22) > Aug 4 11:26:56 laptop NetworkManager: Activation (wlan0) failed > for access point (mammamia) > Aug 4 11:26:56 laptop NetworkManager: Marking connection > 'mammamia' invalid. > Aug 4 11:26:56 laptop NetworkManager: Activation (wlan0) failed. > Aug 4 11:26:56 laptop NetworkManager: (wlan0): device state > change: 9 -> 3 (reason 0) > Aug 4 11:26:56 laptop NetworkManager: (wlan0): deactivating > device (reason: 0). > Aug 4 11:26:56 laptop NetworkManager: > nm_device_wifi_set_mode(): error setting card wlan0 to mode 2: Device or > resource busy > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Manage NM connections manually...
On 07/31/2010 10:03 AM, George wrote: > Hello All > > I'm developing a kind of test software and now I need to deal with > network. I have to enumerate wireless devices (done), create connection > using them, activate it, ... , close it, delete it. I can't use NM > system settings service due to it needs to have root password and it's > very undesirable. I tried to add connection directly thru gconf database > and nm-applet starts to see new connection but if any secrets will be > needed or or previously supplied secrets became /obsolete/ nm-applet > shows own dialogs and this is also unacceptable because my program has > custom fullscreen interface. If connection cant be established user > should learn it from me not from nm-applet :) So the only way I see is > to implement NM user setting service and do whatever I want even it > doesn't seem to be easy task (but We have working example (nm-applet)) . > But there's another issue I see: > AFAIK the only one setting service can be registered at a time, so when > my program will start I'll have to stop nm-applet process and on exit > I'll have to start nm-applet again. I dont like that there's possibility > that after my program nm-applet will not run (crash in my program or > whatever). Yep, these are all problems that the current architecture has. We are working on putting more fine-grained security mechanisms on system settings so as to (hopefully) address these issues: http://live.gnome.org/NetworkManager/RemovingUserSettings In the meantime, your best bet probably is to make the app be a user settings service, as you've suggested. That will indeed mean that nm-applet won't be able to run. I don't know of a way to work around that, and yeah, that will suck. All I can say is that we hope to fix that. :) Good luck! Have a good one, ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to save pin number and auto-connect on startup?
On Fri, 2010-08-06 at 10:00 +0200, Tassilo Horn wrote: > David Cuenca writes: > > Hi David, > > > I'm new to N-M, connecting to 3G net in Switzerland using a Huawei > > K3715 USB stick and Ubuntu 10.04. After the painful configuration > > process (I had to enter manually "vendor=0x12d1 product=140c" in the > > configuration file) everything works wonderful -- even better that the > > original software. > > Oh, I'm totally unable to get my Huawei E160 working. Could you please > provide those config files you have edited? Maybe that could help me. Does the device have IDs in the 'option' driver? Any Huawei modems that are not driven by 'option' should get their IDs added to that kernel module so people don't need to hack it. Next, does your device need a modeswitch? Many modems have fake driver CDs and need to be flipped into modem mode by usb_modeswitch. If it's a new device, it may not have been added to usb_modeswitch yet. Recent versions of usb_modeswitch (1.1.3 and later at least) will automatically eject the fake CD for you via udev rules when you plug the device in. Most Huawei devices have these fake CDs. > > The only thing I miss is the option to save the pin number and > > auto-connect on startup. > > Hm, I use KNetworkManager, and in the Broadband Connection tab, there > are fields for the PIN, PUK, APN, etc. At least the PIN/PUK are saved > in the KDE keychain (kwallet). I guess it's the same when using > nm-applet, where those credentials should be stored in the GNOME > keyring. He's talking about something that's new in NM 0.8.1, likely. Immediately when the modem is plugged in and nm-applet notices that modem-manager needs a PIN code, nm-applet will ask you for that PIN code. Now here's the problem: the PIN is specific to the *SIM*, not the device. But most modems don't allow us to request the IMSI (the SIM's serial #) before we've entered the PIN, so we have no idea which PIN to use with this device. Chicken+egg problem really. There may be some ways to work around this (store the PIN with whatever attributes we *can* get from the device) and just do best-effort, asking the user when we can't figure it out. Needs to be written though. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Modem gone after suspend/resume
On Fri, 2010-08-06 at 19:21 +0400, Andrey Borzenkov wrote: > On Friday 06 of August 2010 18:30:48 Torsten Spindler wrote: > > Hello, > > > > > a 3G modem is no longer recognized by modem-manager when the > system > > resumes. It seems the USB identification changes upon resume, > from > > usb6/6-1 to usb6/6-2. This might be caused by udev rules? > > > > > Nope, it did not change. Device usb6/6-2 existed also before > suspend: > > [2.444051] usb 6-2: new full speed USB device using > uhci_hcd and address 3 > [2.636033] usb 6-2: configuration #1 chosen > from 1 choice > > There is not enough information to know what it is, but > I guess it is (built-in?) smart card reader, based on > > [ 4251.276912] > usb 6-2: usbfs: process 1360 (pcscd) did not claim interface 0 before > use > > Compare lsusb -v output before and after resume. > > As for your > modem - it seems to have dropped off after resume: > > [ 4251.624038] usb > 6-1: new full speed USB device using uhci_hcd and address 4 > [ > 4251.744422] usb 6-1: device descriptor read/64, error -71 > [ > 4251.968059] usb 6-1: device descriptor read/64, error -71 > [ > 4252.184088] usb 6-1: new full speed USB device using uhci_hcd and > address 5 > [ 4252.304068] usb 6-1: device descriptor read/64, error > -71 > [ 4252.528099] usb 6-1: device descriptor read/64, error -71 > [ > 4252.744095] usb 6-1: new full speed USB device using uhci_hcd and > address 6 > [ 4253.160115] usb 6-1: device not accepting address 6, > error -71 > [ 4253.272083] usb 6-1: new full speed USB device using > uhci_hcd and address 7 > [ 4253.688067] usb 6-1: device not accepting > address 7, error -71 > [ 4253.688104] hub 6-0:1.0: unable to enumerate > USB device on port 1 > > I would start with checking that device alone > (without any application) can survive suspend/resume cycle. Stop NM/MM > to make sure nothing attempts to attach to device; plug in modem; > verify that it is available using lsusb; now suspend/resume and check > whether modem is still available. If not - this is kernel problem and > NM cannot do anything about it. If the modem *does* come back after resume and provides serial ports, but MM doesn't notice those ports, then it's likely a driver/udev problem in the kernel. But like Andrey has diagnosed, it looks like the modem simply doesn't come back after resume, likely because it's firmware doesn't handle resume well, or there's a kernel bug with USB bus re-enumeration on resume. Dan > > > I've collected some logs here on > Launchpad: > > dmesg after resume: > > > http://launchpadlibrarian.net/53157289/dmesg > > find in the sys > directory after resume: > > > http://launchpadlibrarian.net/53157295/find > > debug output for > modemmanager: > > http://launchpadlibrarian.net/53157338/mm.log > > > > Any > chance to get modem-manager/networkmanager to rescan the device > > tree > to find the modem again? > > > > Torsten > > > > > > > ___ > > networkmanager-list > mailing list > > networkmanager-list@gnome.org > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: iwconfig and interesting problem
On Fri, 2010-08-06 at 15:30 +0430, Mohsen Pahlevanzadeh wrote: > But When i use this key in network-manager's interface i can connect to > the internet. What kind of key are you choosing in NetworkManager? Hex/ASCII? Or Passphrase? If you're choosing passphrase (which you probably are since NM enforces the limits on Hex & ASCII) then the passphrase you use goes through a semi-standard hashing scheme to determine the actual WEP key that's used: 1) repeat the given key (googooli) over 64 characters 2) MD5 that buffer into a 16-byte hash 3) the first 13 bytes of that 16-bit hash are the actual WEP key Since this method was never actually standardized, iwconfig does not do this for you. Nor does wpa_supplicant actually. Dan > On Thu, 2010-08-05 at 16:53 -0500, Dan Williams wrote: > > On Thu, 2010-08-05 at 09:19 +0430, Mohsen Pahlevanzadeh wrote: > > > Dear all > > > When i use by hand iwconfig , i get following error: > > > debian:/home/mohsen# iwconfig wlan0 essid mohsen key s:googooli > > > > Your key is wrong here; you're attempting to use a WEP ASCII key, and > > those *must* be either 5 or 13 characters long. Yours is 8 and thus is > > not a valid WEP ASCII key. > > > > Dan > > > > > Error for wireless request "Set Encode" (8B2A) : > > > SET failed on device wlan0 ; Invalid argument. > > > debian:/home/mohsen# > > > But i have a question: > > > How networkmanager can connect to access poin? if possible tell me that > > > i can try and connect.because networkmanagers's parameter that it > > > involved can help me. > > > Yours, > > > Mohsen > > > > > > ___ > > > networkmanager-list mailing list > > > networkmanager-list@gnome.org > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 3g Modem pin entry in the clear
On Sat, 2010-08-07 at 16:29 +0200, Klaus Lichtenwalder wrote: > Am 24.07.2010 20:36, schrieb Klaus Lichtenwalder: > > Hi, > > > > I'm just wondering, when I plug my 3g USB modem, NetworkManager > > (ModemManager?) asks for the pin to unlock the sim card. No problem with > > that, except that it shows the pin entered. Shouldn't that be more like > > a password entry? I also can enter the pin in the network config for > > that connection, where it is properly hidden (in gnome-keyring), but > > this entry is obviously not used. Am I doing something wrong here? > > > > > > Ok, > I did some digging, and found that the behavior is specified in a glade > specification. For my usage it looks like the attached patch works. We do want a "Show password" checkbox though just in case you need to check that you PIN is right before you hit OK :) Which I've added and pushed to 0.8.x and master. Thanks for the poke to get this done. Dan > > > Klaus > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Setting static ip base on NetworkManager
On 08/03/2010 07:58 AM, edward_do...@wistron.com wrote: > Dear, > could someone teach me how i can set static ip base on NM. > (gateway , DNS etc..) > > Now, if i don't use nm-applet to control NM. > what can i do? > i study NM DBus doc. But it doesn't define any Wifi or Wire staic ip. Right, the DBus API spec describes (among other things) how to add/replace/delete connections, but it doesn't discuss the contents of the connection settings themselves. For that, you'd want to look at: http://projects.gnome.org/NetworkManager/developers/settings-spec-08.html I'd also recommend looking at the example code in the examples/python directory in the sources of the N-M daemon. Here it is on git: http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/examples/python add-system-connecton.py does pretty much exactly what you want to do. :) Other good resources: - http://live.gnome.org/NetworkManager - http://live.gnome.org/NetworkManagerConfiguration - http://live.gnome.org/NetworkManager/SystemSettings - The D-feet DBus debugger - https://fedorahosted.org/d-feet/ I found it massively helpful when learning about NetworkManager and DBus in general. Hope that helps! Have a good one, Daniel ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wifi GNOME network manager version into KUbuntu, Debian "pinning method, etc. ; jor networkmanager
On 08/07/2010 02:45 PM, giovanni_re wrote: > KUbuntu 10.4, > > = > Failing to get wifi to connect to access point. It can see APs, but > fails to get dhcp via command mode, & fails connect with wicd. > > = > It has been suggested (on KUbuntu list?) to remove the KU network > manager package, & that might get wicd & console command wifi working. Well, for the purposes of testing, you can temporarily stop NetworkManager. This command does that: $ sudo stop network-manager (I say "temporarily" because it would come back on a reboot.) > Previously, I was told that there is more networking success if one > installs Ubuntu (not KUbuntu) [to get the Ubuntu/Gnome network manager > sw], then install KDE on top of that. > > = > For a system that was installed as KUbuntu: > > Might it be possible to use something like Debian "pinning" to hold back > the KU network manager package, & then install the Ubuntu NetworkManager > package? Guess I'd at least have to ad the Ubuntu repositories to > /etc/apt/sources.list. Nope, none of that is needed. Ubuntu and Kubuntu use the same repository; they differ only in what packages are installed by default. The GNOME and KDE "versions" [1] of NetworkManager both reside in that common repository, and they can be installed side-by-side. All you need to do is: $ sudo apt-get install network-manager-gnome Then, if you wanted to run the GNOME "version" instead of the KDE "version", you would do: $ killall knetworkmanager $ nm-applet & And it should work, even if you are in KDE. Hope that helps! Have a good one, Daniel [1] Well, strictly speaking, the core of NetworkManger is a daemon that doesn't care at all about what desktop environment is running. Indeed, both Ubuntu and Kubuntu use the exact same daemon. However, using the daemon on its own is rather inconvenient, so various front-ends or "clients" exist. One is 'nm-applet', which comes in the network-manager-gnome and is installed by default with Ubuntu; this is the "GNOME version". Another is 'knetworkmanager', which is what Kubuntu installs by default. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
On Sat, 2010-08-07 at 16:32 +0300, Ville-Pekka Vainio wrote: > I decided to test the Broadcom proprietary driver and it has the same > problem as b43, I still need to click "Enable Wireless" before NM shows > any wifi networks. I think that's unnecessary, the wireless could just > be enabled by default. Before you check "enable wireless", what is the contents of: /var/lib/NetworkManager/NetworkManager.state and what is the output of: rfkill list cat /sys/class/rfkill/*/state cat /sys/class/rfkill/*/type Lets see what those have in them and then we can debug further. ALso, what are the top lines of /var/log/daemon.log when NetworkManager starts up? It'll be something like this: Aug 2 21:34:54 dcbw NetworkManager[1271]: WiFi enabled by radio killswitch; enabled by state file Aug 2 21:34:54 dcbw NetworkManager[1271]: WWAN disabled by radio killswitch; disabled by state file Aug 2 21:34:54 dcbw NetworkManager[1271]: WiMAX enabled by radio killswitch; enabled by state file Aug 2 21:34:54 dcbw NetworkManager[1271]: Networking is enabled by state file Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NEWS entries / Announcement mails
On Fri, 2010-08-06 at 18:56 +0200, Dominique Leuenberger wrote: > >>> On 08/06/2010 at 6:44 PM, Daenyth Blank wrote: > > On Fri, Aug 6, 2010 at 11:52, Dominique Leuenberger > > wrote: > >> Hi everybody, > >> > >> I know you're all busy coding and enhancing NM, which is a good thing per > >> se. Yet I would like to ask if anybody could once in a while spend some > >> time > >> extending the NEWS file or create a Announcement mail when a new version > >> gets out? > > > > Like this? > > http://blogs.gnome.org/dcbw/2010/08/02/determination-that-is-incorruptible/ > > Thanks, exactly something like this :) > > Is there something similar to this for > - NetworkManager-openvpn > - NetworkManager-pptp > - gnome-network-applet > - NetworkManager-vpnc > - ModemManager > > ? As those certainly did get some love to on the road to 0.8.1, but it's at > best related to what NM itself received. Release announcement sent, bad Dan for the lag. These days most changelogs are redundant given great git history and web interfaces to git. Almost nobody updates them anymore. What's usually missing is a good overview of the changes that's lighter than the git history but hits the hilights. For the VPN plugins... all of them got updated translations, and additionally: - vpnc: added the "Force NAT-T" option - openvpn: support for tun-mtu, fragment, and mss-fix options, PKCS#12 and PKCS#8 private keys, RIPEMD-160 HMAC auth, and better handling of unencrypted private keys - pptp: fix for MPPE and auth method GUI jitter and suppression of some annoying PPTP warning messages - openconnect: support proxy, 'key-from-fsid' settings, and Cisco Secure Desktop thingy Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
ANN: NetworkManager 0.8.1 released
Hi, I'm pleased to belatedly announce the release of NetworkManager 0.8.1. This release is the culmination of a ton more effort than just the minor version bump signifies, and a huge thanks goes out to everyone involved in the features, code, and testing. As always, this release nails the top feature request and piles in a bit of something for everyone else. Major enhancements include: - Bluetooth Dial-Up Networking - nmcli: a command-line interface for controlling NetworkManager - Mobile Broadband Status: signal strength, roaming, and access technology display - Enhanced IPv6 support: including DHCPv6 and tons of fixes - Logging and Debugging: make NM as quiet or verbose as you like 650 commits, 80+ bugs fixed, and almost 20,000 lines of code changed since 0.8. Tarballs in the usual places: http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.8/ http://ftp.gnome.org/pub/GNOME/sources/network-manager-applet/0.8/ http://ftp.gnome.org/pub/GNOME/sources/NetworkManager-vpnc/0.8/ http://ftp.gnome.org/pub/GNOME/sources/NetworkManager-openvpn/0.8/ http://ftp.gnome.org/pub/GNOME/sources/NetworkManager-pptp/0.8/ http://ftp.gnome.org/pub/GNOME/sources/NetworkManager-openconnect/0.8/ And there are already packages for Fedora, Ubuntu, and Debian at least. Now on the road to 0.8.2 and NM 0.9. Cheers, Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Is Network Manager in 11.3 different from 11.2?
On Fri, 2010-08-06 at 11:17 -0700, Robert Smits wrote: > For many years I've used scpm to reconfigure my laptop by changing the nfs > fstab file depending on what environment I was in. This year I understand > scpm is no longer available in 11.3, and I've been told to use network > manager. In 11.2, network manager, despite it's name couldn't manage > networks, just connections. Has network manager changed so I can easily > alter my nfs setup as I move my laptop from connection to connection? That depends on exactly what your needs were :) Back in 2008 your question was about "network profiles" which you could select at startup and which would automatically start your NFS/SMB shares for you when the network was connected. In NM-land you can do that with dispatcher scripts, which are basically like hooks that run when the network has gone up or has gone down. There's more information about this in 'man NetworkManager'. NetworkManager works with "connections" which are mostly like profiles, except you don't have to pick one on startup. They are mostly autodetected for those network types where we can detect such stuff. Each connection has an UUID (universally unique identifier) which can be used to perform operations when that connection goes up or down, like mounting specific shares. What's not there that I seem to recall you wanted was the ability to automatically mount shares without having to write scripts because at the time you were not comfortable doing so. And I admit there is not a good, user-friendly mechanism to do this yet from the GUI. It can, however, be done with dispatcher scripts. In Fedora we ship an 05-netfs script which restarts the 'netfs' service when a network connection goes up or down. 'netfs'is is a simple service that mounts and unmounts any CIFS/SMB, NFS, or NetWare mount listed in /etc/fstab. I have to assume that SUSE has something similar. It doesn't care about the connection UUID, but UUID checks could be added to bring up certain shares only when connected to your home network for example. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Wifi GNOME network manager version into KUbuntu, Debian "pinning method, etc. ; jor networkmanager
KUbuntu 10.4, = Failing to get wifi to connect to access point. It can see APs, but fails to get dhcp via command mode, & fails connect with wicd. = It has been suggested (on KUbuntu list?) to remove the KU network manager package, & that might get wicd & console command wifi working. Previously, I was told that there is more networking success if one installs Ubuntu (not KUbuntu) [to get the Ubuntu/Gnome network manager sw], then install KDE on top of that. = For a system that was installed as KUbuntu: Might it be possible to use something like Debian "pinning" to hold back the KU network manager package, & then install the Ubuntu NetworkManager package? Guess I'd at least have to ad the Ubuntu repositories to /etc/apt/sources.list. There might also be another debian method to do this. = Being as Ubuntu is Debian based, is there some way to make this work? = I ran Debian from about 2000-2005, so haven't done pinning for a long time. = Thanks :) == Join in the Global weekly meetings, via VOIP, about all Free SW HW & Culture http://sites.google.com/site/berkeleytip/ ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 3g Modem pin entry in the clear
Am 24.07.2010 20:36, schrieb Klaus Lichtenwalder: > Hi, > > I'm just wondering, when I plug my 3g USB modem, NetworkManager > (ModemManager?) asks for the pin to unlock the sim card. No problem with > that, except that it shows the pin entered. Shouldn't that be more like > a password entry? I also can enter the pin in the network config for > that connection, where it is properly hidden (in gnome-keyring), but > this entry is obviously not used. Am I doing something wrong here? > > Ok, I did some digging, and found that the behavior is specified in a glade specification. For my usage it looks like the attached patch works. Klaus -- Klaus Lichtenwalder, Dipl. Inform., http://lklaus.homelinux.org/Klaus/ PGP Key fingerprint: BF52 72FA 1F5A 1E29 C0F8 498C C4C6 633C 2821 97DA diff.glade Description: application/glade signature.asc Description: OpenPGP digital signature ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
On 08/07/2010 08:32 AM, Ville-Pekka Vainio wrote: > I decided to test the Broadcom proprietary driver and it has the same > problem as b43, I still need to click "Enable Wireless" before NM shows > any wifi networks. I think that's unnecessary, the wireless could just > be enabled by default. As I suspected, it is not a b43 problem. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
I decided to test the Broadcom proprietary driver and it has the same problem as b43, I still need to click "Enable Wireless" before NM shows any wifi networks. I think that's unnecessary, the wireless could just be enabled by default. -- Ville-Pekka Vainio ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
