wpa_supplicant cli works, but NM insists "wireless is disabled"
Hello, I have appealed to the Fedora Forum, but no one seems to have a clue there. Here is the thread: http://forums.fedoraforum.org/showthread.php?t=199562 (A quick synopsis of the thread: I've activated/deactivated everything i could think of, related to NetworkManager; yet, everything wireless is grayed out in the applet. But wpa_supplicant (cli) works! Additional info (beyond above thread): I compiled the latest NetworkManager svn; still same grayed out behavior. ) I tried looking in the source and tracing the calls to and from nm_client_wireless_get_enabled (if that's even a function) but, ignorant of C, didn't get far. Please help! tia andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with Networkmanager 0.7
I had to install 0.7 in order to get my E220 to work. Works fine! I use Ubuntu 8.0.4 on my EeePC 1000 / 901 However, I got some other problems with it. 1. Each time I connect to the network I have to key in the Shared key, although it is saved. I can go to Edit that connection and even show the key. What gone wrong with that? Why does it not take the key automatically? How to fix it? As mentioned above I have an EeePC 1000 and 901. While 901 does not ask me for the key, 1000 does. The OS is on a SD card cloned to the other one. Somewhere these two versions drifted apart. 2. I have two users, and I cannot get Networkmanager to work at the second users account. I though it will be globally installed. 3. Most annoying is that, if for any reason I lose the wireless connection, the icon changes to no connection. The right click on the icon shows me ticked Enable Network. It cannot be unticked. There is no Enable Wireless. And a ping to a remote site works with and without plugged in Ethernet cable, so that I cannot say which connection it actually is using, since the left click on the icon gives me only the choice to use VPN, which I have not setup at all. 4. I got already several updates automatically via Ubuntu updates, but it remains always 0.7 and no apparently changes. bye R. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Making NM portable
Just committed and pushed the libnl based backed for the Linux kernel: git://bombadil.infradead.org/~rishi/inetutils.git Next up is going to be some support for IPv6 for the *BSD backend. A FreeBSD guy sent a patch today. Happy hacking, Debarshi ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Support for bonding?
Hi, Has any thought been given to supporting a setup like the one described here: http://www.debian-administration.org/articles/312#comment_9 ? I googled up that post when thinking about how to retain connectivity when moving from wired to wireless and vice-versa. I'm happy to do the configuration manually (although someone clearly wants NM to handle it: http://brainstorm.ubuntu.com/idea/10534/) but it seems at least likely that NM might interfere. If that's not the case, so much the better; I'll try to set it up and see what happens. Regardless, allowing people to dock/undock or plug-in/roam without interrupting their connections seems like it's right up NM's alley. Thanks, -- Dave Abrahams Boostpro Computing http://boostpro.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Making NM portable
> Yeah, but NM uses libnl for all address operations too. So unless > libroute adds addressing abstractions, NM will still use libnl code > internally. Yes, I plan to write a libifconfig using libnl for the Linux backend. The BSD backend will again use PF_ROUTE or some libnl-like abstraction of it. (Sorry for the late response) Happy hacking, Debarshi ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] nm-service-openvpn: prevent segfault
On Wednesday 17 September 2008, Robert Buchholz wrote: > Hey, > > r4056 introduced management socket cleanup in the openvpn plugin - > and a SIGSEGV for me, when openvpn fails to start (because one needs > 2.1_rc now). Backtrace, log and patch follow. ping; more love for less segfaults. -R. signature.asc Description: This is a digitally signed message part. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Web-based Network Login
Hello On Fri, 2008-09-26 at 11:13 -0400, Slokunshialgo wrote: > Hello, > > I've been looking into making an addition to NetworkManager to > automatically authenticate to networks with a web-based login process. > For example, you go to a cafe and they have a paid hotspot, you would > connect to the wifi, open a browser, and enter a username & password. > The idea is to automatically do then when connecting to the network. > > The basic idea thus far is to use d-bus to connect NM to a Firefox > extension (starting it if need be) and pass a saved username and > password. This extension would then use different things in Firefox to > login to the page, passing back success or failure. > > Does anybody have any suggestions, or any problems with the proposed > idea? Using twill with dispatcher scripts ? > > --Slokunshialgo > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Ritesh Khadgaray Ph: +919970164885 Desktop LinuX N Stuff, RHCE Software Maintenance Engineer, Pune, Red Hat ॐ मणि पद्मे हूँ Eat Right, Exercise, Die Anyway. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
import vpn configuration failed
Hi, When I import a configuration file in the NM-vpnc, it prompt (nm-connection-editor:29232): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (nm-connection-editor:29232): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() ** (nm-connection-editor:29232): WARNING **: add_connection: unhandled connection scope 0! First, does the connection name support utf-8 character? Second, should the plugin add scope? User or System for importing configuration file. And I add below code, it no warning, but still import failed. NMConnectionScope scope = NM_CONNECTION_SCOPE_USER; nm_connection_add_setting (connection, NM_SETTING (s_con)); nm_connection_set_scope (connection, scope); // Add scope Thanks! Sincerely Yours, Bin Li http://cn.opensuse.org test.pcf Description: application/font-pcf ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
