Re: VPN not authenticating on Fedora 25
On Mon, 2017-01-30 at 20:41 +1300, Simon Geard wrote: > Looking for help on something. My VPN for remote access to work is > based on openconnect, and worked fine last time I used it - which was > about two months ago, so probably before upgrading to Fedora 25. > > My problem is simple - if I try to activate the VNP connection > through > either Gnome Shell or through the Network control panel, it > immediately > switches off again. In the control panel, I briefly (for small > fractions of a second) see the "Not connected" text replaced with > "Authentication required", before reverting back to "Not connected". > > Now, previously, this used to pop up a dialog for authentication... > any > idea why this is no longer happening? I tried creating a new VPN > connection in NM, but that exhibits the same problem. > > Ideas on how I can diagnose the problem? > > Simon. > Ah, please disregard this. I've just found a link that indicated that I need to manually install "NetworkManager-openconnect-gnome". I guess this must be something that was broken by the upgrade from Fedora 24 to 25... a package split, or something. Regardless, installing that package and rebooting seems to have fixed the problem. Simon. signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
VPN not authenticating on Fedora 25
Looking for help on something. My VPN for remote access to work is based on openconnect, and worked fine last time I used it - which was about two months ago, so probably before upgrading to Fedora 25. My problem is simple - if I try to activate the VNP connection through either Gnome Shell or through the Network control panel, it immediately switches off again. In the control panel, I briefly (for small fractions of a second) see the "Not connected" text replaced with "Authentication required", before reverting back to "Not connected". Now, previously, this used to pop up a dialog for authentication... any idea why this is no longer happening? I tried creating a new VPN connection in NM, but that exhibits the same problem. Ideas on how I can diagnose the problem? Simon. signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Simplify OpenVPN blob handling
On Tue, 2016-01-26 at 11:51 +, David Woodhouse wrote: > It does even make a little bit of sense, if the most sensitive item > on the computer in question *is* the VPN certificate That would certainly be the case for my VPN setup... it's just there so I can access the work network from my personal machine at home. All the sensitive stuff is being accessed through remote-desktop or ssh, so there's nothing confidential on the local machine. Simon. signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH 1/1] initscript: remove all distribution initscripts
On Wed, 2015-12-02 at 18:50 +0100, poma wrote: > > LFS? (B)LFS distributes their own script. I remember creating patches to get one distributed in upstream NM way back in the early days of NM, but I don't think that ever got committed. The idea was kind of contrary to LFS anyway, given the variations between such systems... Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: vpn and stuff
On Sat, 2015-09-19 at 22:17 +0200, Xen wrote: > But if you're not gonna help me, you're just bragging. > > Not sure if it solves every problem though. Bragging, I mean. I'm not bragging - I'm giving you advice. You're apparently unhappy with how the NM binaries are named because getting the capitalization right is difficult, something which bothers you enough that you're complaining to the developers about it. And I pointed out to you that this is a problem that you can avoid with a simple change to your shell settings, without any need for others. If you don't like that recommendation, you're welcome to ignore it, but there's no need to be insulting and calling it "bragging". Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: vpn and stuff
On Mon, 2015-09-14 at 17:18 +0200, Xen wrote: > In a command line shell you will just never learn or remember to > write Ne instead of ne.. Why would I need to? I just type 'ne' and tab, and let (case insensitive) command-line completion fill in the rest for me... Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Automatic connect.
On Mon, 2014-08-04 at 13:35 -0500, Dan Williams wrote: > NetworkManager will only connect to wifi networks which the user (or > some client) has told NetworkManager to previously connect to, as a > security measure. However, if you'd like get this behavior, you can > write a small client that watches the scan list advertised by NM and > then creates a temporary connection for any unprotected network. I'm > happy to explain more on this if you'd like. Of course, just because a network is "unprotected", doesn't mean it's usable. Most unsecured APs I see these days are the kind where you need to enter a password (or accept terms and conditions, etc) through a web page, and there's not a lot of value in auto-connecting to such a network. Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Control Center App vs nm-connection-editor
On Thu, 2014-01-09 at 14:17 -0600, Dan Williams wrote: > On Thu, 2014-01-09 at 15:52 +1300, Simon Geard wrote: > > One thing I noted the other day is that the Gnome UI doesn't support > > setting up connection sharing (i.e configuring the machine as a gateway, > > running a DHCP server, etc. Had to resort to nm-connection-editor for > > that. > > It does for creation of a WiFi Hotspot, which will then have access to > your upstream ISP (whether over ethernet, WWAN, etc). But it doesn't > AFAIK support connection sharing between arbitrary connections. In my case, I have a workstation with a failing wireless card, an old netbook with working wireless, and a crossover ethernet cable. Probably not a typical use case, I'll grant... Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Control Center App vs nm-connection-editor
On Tue, 2014-01-07 at 09:52 -0600, Dan Williams wrote: > In addition to what Pavel said, the GNOME Control Center makes some > choices about the UI design and what to include and what to leave out > that are quite appropriate for the GNOME design and target audience. > Same for KDE. nm-connection-editor exists to expose most options (but > not necessarily all of them) in a more complicated form, and is intended > to be either a parallel tool to each desktop's preferred settings > panels, or a standalone one for desktops that don't have any other > settings editor. One thing I noted the other day is that the Gnome UI doesn't support setting up connection sharing (i.e configuring the machine as a gateway, running a DHCP server, etc. Had to resort to nm-connection-editor for that. Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Connection priority between mobile broadband and wired
On Fri, 2014-01-03 at 13:15 -0600, Dan Williams wrote: > If this is the case, what you want to do is set the ethernet connection > to the "Shared" method in nm-connection-editor, which will cause > NetworkManager to start a DHCP server and proxy DNS server on the > ethernet connection, and then NAT the ethernet over to the WWAN to > provide connectivity. Essentially, Internet Connection Sharing with the > WWAN connection as the ISP and the ethernet connection as the local LAN. A very timely post, Dan - while not the original poster, I've just had need of that advice, thanks to a failing wifi adapter on my desktop machine. It's not a long-term fix, but for now, I've got internet access working again by routing it through an old laptop... much cleaner than with my first attempt which used iptables directly... Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager-dispatcher killing my scripts
On Tue, 2013-07-30 at 14:04 -0600, Jeff Sadowski wrote: > exec /bin/bash -c "$0 test" & Running it with exec means you're not starting a new process, just overwriting the current one. Same PID, so NM will still kill it... Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: conflicts with packages wicd, indicator-network
On Thu, 2012-06-21 at 19:08 -0600, paur...@gmail.com wrote: > I am running Ubuntu 12.04 and when > I try to use the wicd or indicator-network packages on my system, I > get errors related to network manager > > wicd cannot authenticate properly to my wireless network in the > presence of network manager (gives up reporting bad password) but if I > uninstall network manager, wicd connects okay with exact same > settings, I am wondering why? WICD and Network Manager do the same thing. If both of them are trying to do the same thing at the same time, they interfere with each other. > > also, I would like to use network manager with the indicator-network > plug-in for the system tray rather than via nm-applet, yet > indicator-network automatically replaces network manager with another > package called connman that is crash-prone, so is there no way to use > network manager with indicator-network? Same answer. Indicator-Network is a GUI for Connman, which does the same thing as Network Manager and WICD. And you can't run more than one network management daemon at the same time. Simon. signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: cross compiling without gnome
On Wed, 2011-05-25 at 15:17 +0300, Pantelis Koukousoulas wrote: > You can check what --with-distro the BLFS book proposes these days for > example, LFS/BLFS doesn't include NetworkManager, and never has. But speaking as an LFS user, --with-distro=redhat works fine for me... Simon. 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: Run a script when a connection is created?
On Thu, 2011-01-06 at 11:03 -0500, Paul Smith wrote: > Ah that's good info, thanks. I was hoping that I'd get more details on > the connection in addition to the device name, such as the DNS details > (search domain(s) and server(s)). Nothing like that available I > suppose? Read the NetworkManager man page for details on what's available... Simon. 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: [RFC] Fast-user-switching plans
On Wed, 2010-06-09 at 16:28 -0700, Dan Williams wrote: > I think it's clear that even if there are no user connections as such, > that we still need secrets on a per-user basis for some connections. > And that's not actually that hard to do, and we've got most of the code > written for that already. One more thought on that subject - not sure if it's a realistic concern or not. User secrets stored in gnome-keyring and equivalents are stored securely, in such a way that no other user (even root) can readily [1] obtain them. Can the same be done for user secrets stored at a system level, i.e preventing a privileged user on one system from stealing another user's credentials for a second system? My viewpoint on this is our workstations at work, where practically every developer has root access in order to do their job - that doesn't mean they should be able to bring up a VPN link to my system at home. [1] Yeah, I know that with enough work, a privileged user can get around that, patching NM binaries, etc. But that's no reason to make it easy... Simon. 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: [RFC] Fast-user-switching plans
On Fri, 2010-06-04 at 19:24 -0700, Dan Williams wrote: > On Wed, 2010-06-02 at 23:44 +1200, Simon Geard wrote: > > On Wed, 2010-06-02 at 00:45 -0700, Dan Williams wrote: > > > The one benefit of user connections is that they follow you if you back > > > up your homedir and switch machines :) I don't think that's enough of a > > > benefit to keep them around though. > > > > Also if you periodically update your OS - e.g installing a new Ubuntu > > release every six months. Stuff in $HOME stays - stuff in /etc doesn't. > > Yup. Though we could mitigate that by providing usable backup/restore > capability that dumps a bunch of keyfiles describing your connections > into a tarball or something. Is a user going to appreciate that, though? I.e, will they realise that their network settings are something that needs manually backing up? Or will they learn this out after installing an update, and finding they've lost the VPN settings they assumed were stored safely in $HOME? Actually, here's a thought - the login/password details for each connection are currently stored in the user's keyring. If you were to turn "user connections" into "system connections with ACL", how would that piece work? If system connections are removed or their permissions changed, are keys removed from the keyring? Simon. 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: [RFC] Fast-user-switching plans
On Wed, 2010-06-02 at 00:45 -0700, Dan Williams wrote: > The one benefit of user connections is that they follow you if you back > up your homedir and switch machines :) I don't think that's enough of a > benefit to keep them around though. Also if you periodically update your OS - e.g installing a new Ubuntu release every six months. Stuff in $HOME stays - stuff in /etc doesn't. Simon. 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: [RFC] Fast-user-switching plans
On Thu, 2010-05-27 at 17:19 +0100, Marc Herbert wrote: > Le 27/05/2010 15:26, José Queiroz a écrit : > > > > And that's the point. If the system offers us the separation of > > resources like files, why can't a network connection be personal? > > Simply because IP is not designed like this at all. NetworkManager's > scope is make IP networking easy; not to re-invent the Internet. Actually, couldn't something be done with Netfilter rules? The connection (a VPN, say) might technically be system-wide, but with rules enforcing that only applications running as a certain user could send and receive packets on it? Perhaps imperfect, but a starting point... Simon. 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: If wireless security information is not provided to the plug-in, will the default plug-in handle it?
On Thu, 2010-04-08 at 16:38 +0800, Mu Qiao wrote: > One more thing. I find that NetworkManager uses gnome keyring to store > keys. But I didn't find any code doing that. Could you please give me > some directions? NetworkManager doesn't use the gnome keyring itself - the Gnome network-manager-applet does. Simon. 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: gui design of nm-applet
On Thu, 2010-04-01 at 09:23 +0200, Torsten Spindler wrote: > Work on a re-design of a network connectivity applet has already been > started and some information can be found here: > https://wiki.canonical.com/Ubuntu/NetworkMenu > Your link doesn't seem to be publicly accessible - I get "You are not allowed to view this page" when I click on it... Simon. 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: Reboot for password to work
On Fri, 2010-03-19 at 01:04 -0300, José Queiroz wrote: > AES authenticate pairs of (user,password) against an authentication > server --- RADIUS, TACACS+, etc ---, in a way that if your costumer > don't pay another 15-minute session, you can log it off just > invalidating his/her username, without messing with the other users. Which has the downside of requiring an authentication server, and someone who knows how to maintain it. PSK works out of the box with the cheap access point bought from the local electronics store, and can be administered by a cafe owner with a minimum of technical knowledge... Simon. 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: The logic behind user/system settings
On Wed, 2010-03-10 at 11:26 +0100, Jirka Klimes wrote: > > Out of curiosity, how do you set the persistent hostname with the > > keyfile plugin? > > > > Keyfile plugin reads the hostname from 'hostname' key from [keyfile] section > of > NM configuration file: > [keyfile] > hostname= > > It is described on wiki: > http://live.gnome.org/NetworkManager/SystemSettings > Ah, useful, thanks. I see the docs have improved greatly since I last looked. Simon. 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: The logic behind user/system settings
On Tue, 2010-03-09 at 17:12 -0800, Dan Williams wrote: > They translate the distribution's native config file format (ifcfg files > for RH, /e/n/i for Debian/Ubuntu, etc) into system-wide configuration > that NetworkManager can use. They also provide the distro's configured > persistent hostname (/etc/hostname for Debian, /etc/sysconfig/network > for RH) to NetworkManager. > > If your distribution does not have a system settings plugin, you can use > the 'keyfile' plugin which reads/writes connections in a .ini-style > format in /etc/NetworkManager/system-connections. Out of curiosity, how do you set the persistent hostname with the keyfile plugin? Simon. 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: Online Status Design + Program Input
On Fri, 2009-12-04 at 07:22 +, Martin Owens wrote: > That's a completely different use case. What you want to tell client > programs needs to be different to what your telling users when your > unsure about what you've got. True, it's not quite the same, since existing implementations are triggered by the presence of any NM-managed network, rather than whether that network can see the rest of the world. Even so, if the information is there, people will likely use it for such purposes... Simon. 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: Online Status Design
On Thu, 2009-12-03 at 14:42 +, Martin Owens wrote: > I think proxies are going to be the tricky one, requires someone who > knows about them tbh. But in any case, reporting that your not online > when you are is slightly more desirable that reporting that your online > when your not. No. No, it's not. Not when software uses that information to change it's behavior. Like Firefox, which used to go into offline mode when NM said there wasn't a network connection, denying me access to my local web server. Or IM clients going offline because no internet connection is available. Much better to falsely report a working connection than to tell the user and their applications that they can't access the internet when they really can. Simon. 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: Online Status Design
On Wed, 2009-12-02 at 16:48 -0500, Darren Albers wrote: > 1) Sites that require a proxy or sites that use captive portals will > give inaccurate results Definitely a problem. On my workplace network, all external HTTP access must go through a proxy, which means that any tool must not only be proxy capable, but also configured to use that proxy. The Python example on the Launchpad page would fail that test, since while Firefox will have proxies configured, Gnome won't unless a user has configured it, and command line tools are pretty much guaranteed not to, since almost all of them do things there own way.. Simon. 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: (missing) pre-up and pre-down
On Wed, 2009-08-12 at 12:43 -0500, Dan Williams wrote: > On Sat, 2009-08-08 at 01:50 +0100, Graham Lyon wrote: > > Perhaps when a connection drops unexpectedly the pre-down scripts > > should be run with an argument of some kind to inform them that the > > interface has already dropped? That way they can clean up the mess > > that's created but avoid any action that requires the interface to > > still be up... > > That was my thinking too, and probably the right thing to do. Isn't that basically the same as a post-down script then? Even with such a flag, running the pre-down scripts after the connection has already gone down seems wrong... Seems to me that the way to handle pre-down scripts is with the very clear statement that they're run only on a manual disconnection, that being the only circumstance where NM (or any other hypothetical system) knows the connection is about to be dropped... Simon. 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: howto ignore rfkill switch
On Thu, 2009-07-23 at 10:16 -0500, Carl Karsten wrote: > Sounds like it would be good to just disable the switch, right? From > what I gather, the switch signals the OS, which then runs code to > disable the wifi hardware, so overriding that is very possible. Depends on the machine. On some machines the switch just sends a signal to software; on others it physically turns off the wireless. In the latter case (including my laptop), there's nothing you can do, since it's all in hardware... Simon. 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: debug tips
On Wed, 2009-06-03 at 15:42 -0500, Aaron Konstam wrote: > Well you are essentially correct . startx starts a normal r5 session but > runlevel claims that the system is still at rl3. Which seems strange to > me. I think you're misunderstanding what runlevels are - the fact is, they're nothing more than instructions to init, telling it to run a bunch of shell scripts to start and stop programs. That runlevel 5 happens to start an X server and 3 doesn't is purely a matter of convention - if you really wanted to be contrary, you could have 6 start an X server, and 5 reboot the machine. The LinuxFromScratch project has a decent overview of the subject at the link below - some of the details are LFS specific, but most of it is more generally applicable. http://www.linuxfromscratch.org/lfs/view/development/chapter07/usage.html Simon. 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: NetworkManager 0.7.1 rc1 release
On Wed, 2009-02-18 at 23:25 -0500, Dan Williams wrote: > Hi, > > I've tagged and uploaded the 0.7.1-rc1 release, with the version number > 0.7.0.97. I'd like to do rc2 in a few days (version 0.7.0.98), and then > a 0.7.1 release a few days after that. If we really need an rc3, I bet > you can guess what the version number will be. NM itself seems to work fine, but I found Evolution no longer started up after I upgraded NM from 0.7. It was linking against libnm-util.so.0, which appears to have been incremented to .1 in this release. Seems to work fine after recompiling it. Simon. 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: Bluetooth support
On Tue, 2008-12-23 at 23:00 +, Yosef Akhtman wrote: > It is surprising that something that can be relatively easily achieved > by editing a couple of config files plus running a couple of simple > instructions on the command line, may not be achieved with the whole > might of the NM framework. Not really. Hacking things to work on their own is relatively easy. Making them work as part of a framework with everything else is a much more difficult problem. Simon. 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: configure NetworkManger-0.7.0 fail, why?
On Wed, 2008-12-10 at 16:28 +0800, scott.lv wrote: >But I get error when I run pkg-config –modversion dbus-glib-1 > > Package dbus-glib-1 was not found in the pkg-config search path. > > Perhaps you should add the directory containing `dbus-glib-1.pc' > > to the PKG_CONFIG_PATH environment variable > > No package 'dbus-glib-1' found Have you tried doing what the error message says? Your message shows libdbus-glib.so is in /usr/local/lib, so the .pc file is probably in /usr/local/lib/pkgconfig or /usr/local/share/pkgconfig... Simon. 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: WPA Enterprise (EAP-TLS) system connection
On Tue, 2008-12-09 at 15:11 -0500, Dan Williams wrote: > On Tue, 2008-12-09 at 13:34 -0500, Dan Williams wrote: > > On Sat, 2008-12-06 at 21:33 +1300, Simon Geard wrote: > > > I know it's a minor thing, but by breaking convention, it makes > writing > > > an automated build just that little bit more complicated, where the > > > directory can't be predicted from the package name... > > > > Sure. > > Updated in trunk and stable (0.7). Thanks for that. Simon. 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: WPA Enterprise (EAP-TLS) system connection
On Fri, 2008-12-05 at 16:58 -0500, Dan Williams wrote: > That's mostly the problem. I fixed the issue in the applet svn this > morning. We're planning on doing a 0.7.1 pretty soon which will contain > this fix. Any chance that when you do, you can make the tarball name consistent with the contents directory, like most other packages out there? The applet tarball is network-manager-applet-0.7.0, but the contents are in nm-applet-0.7.0. I know it's a minor thing, but by breaking convention, it makes writing an automated build just that little bit more complicated, where the directory can't be predicted from the package name... Simon. 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: Static and dynamic wired interface
On Fri, 2008-09-12 at 10:21 -0700, Robert Smits wrote: > SCPM has been around for eons. Unlike network manager it actually does > look > after switching my nfs network settings between home, job, and an internet > cafe. I wish it did just work. Is the project actively maintained by Novell or anyone else? Your email inspired me to go and see what it was about, but their mailing list shows just a single post in the last year, an unanswered enquiry by yourself several months ago. The CVS repository hasn't been touched since this time last year either... Simon. 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: I might be asking for DHCP support, but I'm not sure
On Thu, 2008-05-08 at 15:56 -0500, Aaron Konstam wrote: > On Thu, 2008-05-08 at 14:04 -0400, Dan Williams wrote: > > Right; this is normal for DHCP depending on which client requests > > addresses at which times. If your laptop requests an address before the > > desktop, the laptop will generally get the lower address. > > > That is interesting because on my home network all machines get the same > address no matter in which order they are turned on. Does it continue to do so if the DHCP server is restarted? I imagine it's probably an implementation detail - whenever possible, try to assign a given MAC address the same IP it had previously. My DSL router does this, but may allocate different IPs after being restarted. Simon. 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: Is Ignore interfaces supported?
On Fri, 2008-04-25 at 09:55 -0400, Dan Williams wrote: > Yes, multiple active connections are supported in 0.7. This should > only have been an issue in 0.6.x which doesn't support more than one > active connection, and doesn't support static IPs very well. Haven't tried multiple connections yet, but the support for hand-configuring interfaces is a big improvement over 0.6. In particular, allowing the DNS addresses to be configured overriding the DHCP server - this is invaluable for me, since the DNS routing service on my DSL router tends to stop working periodically... Simon. 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: Is Ignore interfaces supported?
On Thu, 2008-04-24 at 09:22 -0500, Aaron Konstam wrote: > On Thu, 2008-04-24 at 11:45 +, Nick Byrne wrote: > > Hi list, > > > > I would like configure NM so that ignores my ethernet > > interfaces, is this possible? > > > > Thanks > > Nick > Why would you want to do that? I've encountered a similar need myself before, where on plugging in a crossover-cable to a machine without internet access, NM under no circumstances would allow me to continue using WiFi. Had to shut it down, and establish both ethernet and wireless connections by hand... Simon. 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: Network Manager Wifi thoughts
On Wed, 2008-04-02 at 02:01 -0400, Martin Owens wrote: > Thought 2 is the problematic difference between being connected to the > wifi network (or ethernet network) and actually being online. I got > court out today because the Tend City wifi public network required > that you agree to the terms and type in a guest user/password. now I'm > not suggesting that the network manager should fill these kinds of web > forms in automatically, but what I am suggesting is that a quick check > to see if google.com is really google.com would allow the gui to > display the signal strength in yellow for instance so we know the > connection is there but you not yet online. Two thoughts... - The status of my network connection has nothing to do with whether the network I'm connected to can access google.com (or any other arbitrary domain). Networks without internet connectivity are as valid a use case an any other. - What do you mean by "google.com is really google.com"? That it resolves to a known IP, or block of IPs? That you can connect to it via HTTP, and that the result looks like it should? Note that if I connect to 'google.com', it actually HTTP redirects me twice, first to 'www.google.com', and then to 'www.google.co.nz'. Not to mention the proxy that HTTP traffic has to go through... Simon. 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: nm-applet randomly fighting with dbus
On Tue, 2008-01-15 at 06:47 -0500, Peter Davoust wrote: > Ok, well I set that to 'allow' all the way through as well, but to no > avail. Is there anything else I can try? > > Thanks, > -Peter > > On Jan 15, 2008 5:11 AM, Simon Geard <[EMAIL PROTECTED]> wrote: > > If it's complaining about NetworkManagerInfo, it's nm-applet.conf you > > want, not NetworkManager.conf. I've no idea what this file looks like on > > Ubuntu, but the default is to allow ownership to root and any user 'at > > console'. > > > > Simon. > > No idea, sorry - like I said, I've no idea about Ubuntu, just that you were looking at the wrong file. I've put this message back on the mailing list in case anyone else can help... Simon. 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: nm-applet randomly fighting with dbus
On Mon, 2008-01-14 at 23:06 -0500, Peter Davoust wrote: > ** (nm-applet:12061): WARNING **: nma_dbus_init(): could not > acquire its service. dbus_bus_acquire_service() says: 'Connection > ":1.22" is not allowed to own the service > "org.freedesktop.NetworkManagerInfo" due to security policies in the > configuration file > > I've changed the /etc/dbus-1/system.d/NetworkManager.conf file so that > it allows in all cases, but it doesn't work. I've also tried nm-applet If it's complaining about NetworkManagerInfo, it's nm-applet.conf you want, not NetworkManager.conf. I've no idea what this file looks like on Ubuntu, but the default is to allow ownership to root and any user 'at console'. Simon. 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: GTK+ and libnotify requirements for 0.7 gnome applet
On Wed, 2008-01-09 at 10:35 -0500, Dan Williams wrote: > Two things... First, would anyone mind terribly if the GTK+ requirement > were bumped to GTK+ >= 2.10 ? This allows us to use GtkStatusIcon and > to get rid of the eggtrayicon.c code and the alternate packing model it > has to use. What distros are people running (if you're using NM 0.7), > and what version of GTK does that distro use? Still running 0.6, but that's against gtk+ 2.12. Seems to me that anyone sticking to elderly versions of gtk+ probably aren't going to go anywhere near NM 0.7... Simon. 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: NM 0.7 can't connect to WPA network
On Thu, 2007-12-13 at 18:26 -0400, Joel Goguen wrote: > For this, I was using wext. It seems that madwifi works fine for > WPA-Enterprise as of whatever the last update in Ubuntu is (0.9.3 > IIRC) Yeah, I found madwifi 0.9.3.3 is a *massive* improvement in reliability over any of it's predecessors. Used to get quite a lot of problems connecting to the local AP, but this latest version has been working almost faultlessly for about three weeks now. Very nice. Simon. 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: NetworkManager and Madwifi connection loss
On Tue, 2007-11-27 at 12:47 -0500, Darren Albers wrote: > I have been watching Ath5k development and I hope it will resolve > these > issues since the author's won't be tied into working with a closed HAL. > In the meantime I would try and steer clear of Atheros based cards if > possible. Speaking of those drivers, do you know what state they're in with regard to joining the mainline kernel? Was reading up on them recently, and noticed that while they were in the 2.6.23 -mm kernels, there's no mention of them in the 2.6.24 -mm patch list. Simon. 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: has anyone had a chance to look at my nm-applet patch?
On Wed, 2007-10-31 at 10:59 -0400, Katelin Ganzer wrote: > On 10/31/07, Simon Geard <[EMAIL PROTECTED]> wrote: > > Good idea, but it doesn't compile on my system, unable to find the > > function gtk_widget_set_tooltip_markup(). I think that's something new > > to gtk+ 2.12? I'm running 2.10.14... > > Oh. How do I make it work with gtk 2.10? It seems that all of the > tooltip APIs are from 2.12? No idea, sorry - I'm not a gtk+ coder. I understand a lot of work was done on providing good tooltip APIs in 2.12 - I assume the same effect could be done on previous versions, but might not be quite so easy. NM devs - what version of gtk+ do you officially require? Looking through the 0.6.5 configure.ac, there doesn't seem to be any check for a specific gtk+ version, so I assume it's implicit in whatever Gnome version is needed? Simon. 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: Merge network manager with network monitor
On Wed, 2007-10-31 at 12:34 +0100, Filip Sedivy wrote: > Hello all. > > I am sorry to post question this way. I was wondering if it is > possible to merge somehow functionality of network monitor to network > manager. It would be nice to see network traffic visually by flashing > of the icon with 2 computers. I know that you can install the network > monitor applet but I think this is something that network manager > should do by itself. I am using Gnome on Ubuntu 7.10. I'd second that request. Not so much interested in watching traffic, but more the connection status. I've got a wireless connection which drops out from time to time, but often recovering before NM notices. Obviously I'd rather that didn't happen at all, but when it does, the network monitor applet shows pretty much instantly when the connection is out, and when it comes back. So I keep both of them on the panel. Having just one would be nice... Simon. 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: has anyone had a chance to look at my nm-applet patch?
On Tue, 2007-10-30 at 20:40 -0400, Katelin Ganzer wrote: > It turns out that tooltips in Gtk aren't that hard, so I was able to > implement this fairly easily. Attached is a patch that displays this > information in a tooltip. Hopefully this will make it so that no one > feels that too much info is displayed in the menu =) > > I think my new patch makes it all nice and pretty =) Good idea, but it doesn't compile on my system, unable to find the function gtk_widget_set_tooltip_markup(). I think that's something new to gtk+ 2.12? I'm running 2.10.14... Simon. 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
Building NM 0.6.5 fails against Gnome 2.20?
I'm attempting to build NM on an LFS system, but getting compile errors out of vpn-properties. Basically, it's unable to find the GnomeDruid code, which has been deprecated in libgnomeui-2.20. The fix appears to simply to remove -DGNOME_DISABLE_DEPRECATED from gnome/vpn-properties/Makefile.am. A patch is added, although it's probably quicker to fix by hand... Simon. diff -Naur NetworkManager-0.6.5/gnome/vpn-properties/Makefile.am NetworkManager-0.6.5-new/gnome/vpn-properties/Makefile.am --- NetworkManager-0.6.5/gnome/vpn-properties/Makefile.am 2007-04-19 06:13:08.0 +1200 +++ NetworkManager-0.6.5-new/gnome/vpn-properties/Makefile.am 2007-10-01 22:00:31.0 +1200 @@ -26,7 +26,6 @@ -DGLADEDIR=\""$(gladedir)"\"\ -DG_DISABLE_DEPRECATED \ -DGDK_DISABLE_DEPRECATED\ --DGNOME_DISABLE_DEPRECATED \ -DGNOMELOCALEDIR=\"$(datadir)/locale\" \ -DVERSION=\"$(VERSION)\" \ $(NULL) 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: [PATCH 0.7] Fix WPA-PSK with certain passphrases
On Fri, 2007-09-28 at 22:34 -0400, Bill Nottingham wrote: > Passphrases are first hashed into hex, and then encoded with hexstr2bin > before being marshalled over to wpa_supplicant. Since they are a hex > hash, it's entirely possible that '00' will occur in the hash... which > means you can't depend on strlen to give the right length for the binary > encoding, and therefore must pass the length in explicitly. Sounds like a bug I raised and fixed earlier this year might have crept back in. Does the following bugzilla sound like the same thing? http://bugzilla.gnome.org/show_bug.cgi?id=394956 Simon. 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: wpa_supplicant options
On Tue, 2007-09-04 at 08:42 -0300, Joel Goguen wrote: > I'm trying to force NetworkManager to run wpa_supplicant with a > specific set of options (most importantly, -Dmadwifi) but it seems no > matter what files I edit, it always gets run with the same options. Why do you need to use -Dmadwifi? For a long time now, the madwifi drivers have provided sufficient support for wireless extensions that the default (-Dwext) ought to be fine. It's worked fine for me since at least last year some time... Simon. 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: Strange NetweorkManager behavior.
On Fri, 2007-06-22 at 17:40 -0500, Aaron Konstam wrote: > Has anyone else seen this. Sometimes when I am connected to a wireless > access point using nm-applet and NetworkManager the system in F7 says I > am connected to a wired network. Any comments out there? Seen something similar, not sure if it's related. I use a desktop machine connecting via wireless, never over ethernet. Normally, NM attempts to connect to wireless as soon as I log in, but on some occasions lately, it seems to think it's got a wired connection - nm-applet displays that icon, and it doesn't prompt for keyring password. It certainly doesn't have a wired connection - no cable is connected, and /sys/class/net/eth0/carrier reports 0. This is running NM 0.6.5 and nm-applet 0.6.5, both build from tarballs on an LFS system. I've been running those for a while though - the only things that have changed that might affect NM are a) rebuilding NM with the patch for Atheros signal strength, and b) upgrading kernel from 2.6.20.7 to to 2.6.21.5. Simon. 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: Question regarding Madwifi signal strength
On Fri, 2007-06-08 at 14:53 -0400, Darren Albers wrote: > If you use those packages make sure you remove network-manager and > network-manager-gnome first. > > Let me know if the patches bring things closer to normal for you. > Hmm. I've just rebuilt NM 0.6.5 with the Ubuntu patch. It *has* increased the signal strength reported by NM, but I don't think it's done so correctly - it's now reporting 100% strength for every access point listed (compared to the 65% reported by gnome's network monitor applet). Despite that, I'll leave the patch in place. I've had quite a few problems maintaining a connection to my access point lately, and this can hardly make things any worse. Simon. 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: Question regarding Madwifi signal strength
On Fri, 2007-06-08 at 10:21 -0400, Dan Williams wrote: > On Sat, 2007-06-09 at 00:11 +1200, Simon Geard wrote: > > 00:17:9A:12:31:72 : Quality=49/70 Signal level=-46 dBm Noise > level=-95 dBm > > This looks wrong > > Quality is supposed to be a linear value between 0 and max_qual.qual > inclusive. 49/70 = 70%; and with a signal of -46dBm and a noise of -95 > dBm, that seems bogus. It should be higher than that. -46 dBm is > _really good_. > > > 00:14:7C:AD:39:92 : Quality=120/70 Signal level=-256 dBm Noise > > level=-95 dBm > > This is wrong > > A value of 120 is clearly outside the bounds of 0, 70. I've actually seen *positive* dBm values reported by the drivers before, so yeah, not very good. Simon. 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: Question regarding Madwifi signal strength
On Fri, 2007-06-08 at 23:10 +1200, Simon Geard wrote: > On Thu, 2007-06-07 at 16:25 -0400, Darren Albers wrote: > > Do the above changes seem like they resolved these issues or maybe not > > affect it at all? I can dig out my atheros card (it's in the attic!) > > and find out if nobody knows but I figured it would save me the hassle > > of climbing up there if someone already has checked. > > I use an Atheros-based PCI card, so I'll try updating the drivers, see > if the signal strength is still an issue. As of whatever version I'm > running right now (SVN from about a month or two ago), NM reports about > 15% while the Gnome network applet shows about 60%. What would you > expect me to see on new drivers? Ok, running the latest madwifi driver from SVN now. Doesn't seem any different from previous versions - I'm seeing roughly the same signals in NM as before. Is the following output from iwlist of any interest to you? 00:17:9A:12:31:72 : Quality=49/70 Signal level=-46 dBm Noise level=-95 dBm 00:14:7C:AD:39:92 : Quality=120/70 Signal level=-256 dBm Noise level=-95 dBm 00:14:BF:3D:5F:ED : Quality=13/70 Signal level=-82 dBm Noise level=-95 dBm 00:18:4D:05:20:D0 : Quality=4/70 Signal level=-91 dBm Noise level=-95 dBm 00:16:E3:58:B0:C8 : Quality=3/70 Signal level=-92 dBm Noise level=-95 dBm 00:0F:3D:B3:F0:68 : Quality=10/70 Signal level=-85 dBm Noise level=-95 dBm Incidentally, I don't suppose you could point me to the patch for NM you referred to in your email? Simon. 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: Question regarding Madwifi signal strength
On Thu, 2007-06-07 at 16:25 -0400, Darren Albers wrote: > Do the above changes seem like they resolved these issues or maybe not > affect it at all? I can dig out my atheros card (it's in the attic!) > and find out if nobody knows but I figured it would save me the hassle > of climbing up there if someone already has checked. I use an Atheros-based PCI card, so I'll try updating the drivers, see if the signal strength is still an issue. As of whatever version I'm running right now (SVN from about a month or two ago), NM reports about 15% while the Gnome network applet shows about 60%. What would you expect me to see on new drivers? Simon. 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: NM and WEP
On Thu, 2007-05-31 at 09:18 -0700, Patton Echols wrote: > 1. I understand that for NM to use WPA, wpa_supplicant must be > installed. Does the process of coding the keys into wpa_supplicant.conf > need to be done too? It was in my case, and it works. But here is my > thinking. If NM generates and stores the key the first time (and does > not need to get that info from the .conf file) then could the presence > of the .conf file be messing things up? > > 2. Do I need to hard code the wep access information into > wpa_supplicant.conf? The wpa_supplicant.conf file is not used by NM. All the settings that might be stored in it come from NM itself. Simon. 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: different icons if internet is available
On Sat, 2007-05-19 at 09:29 +, yelo_3 wrote: > I didn't understand the first probelm. > And why are you talking about spyware? Because rightly or wrongly, it's going to be the immediate reaction of a lot of people if you put code into an application that causes it to periodically access arbitrary machines out on the internet. People get very paranoid over what information the program might be reporting. Simon. 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: different icons if internet is available
On Fri, 2007-05-18 at 10:30 +, yelo_3 wrote: > I've implemented the most code, except the function that decides if internet > is available or not. > In fact I'm thinking of this problem. > http://bugzilla.gnome.org/show_bug.cgi?id=439310 > an isolated network access cannot of course reach the most internet locations > > we could discuss on this... for instance in might be: > internet on if ubuntu.com and gnome.org are reachable > otherwise internet off. I suspect many people would be unhappy to find that NetworkManager appeared to be phoning home - a service for managing a local network interface really shouldn't be wandering out across the wider internet. Harmless though it might be, I can already picture the Slashdot crowd screaming about spyware... Simon. 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: different icons if internet is available
On Thu, 2007-05-17 at 20:12 +, yelo_3 wrote: > Hello, just a proposal: it would be great that NM-applet icon could > add a small world,located in a corner, if internet is reachable, > checked every N minutes... > > what do you think? it is not hard to implement it, am I right? Not hard? Well, the first thing is, what do you actually mean by "internet is reachable"? What's the difference between an isolated local network, and one with what a person might call 'internet access'? Simon. 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: NetworkManager and applet 0.6.5 Released
On Thu, 2007-04-19 at 23:24 -0400, Christopher Aillon wrote: > Hey all, > > It's been a while since we've had NM releases and after talking with > Dan, I just made a release of 0.6.5 based on the 0.6 branch. > > Downloads are available at: > > http://ftp.gnome.org/pub/gnome/sources/NetworkManager/0.6/ > http://ftp.gnome.org/pub/gnome/sources/network-manager-applet/0.6/ Just downloaded and installed it, seems to be working just fine. One note though - the directory inside the tarball is simply nm-applet-0.6.5, which doesn't match the name of the tarball, or the usual name of the package. Not a big deal, but the inconsistency forces me to put workarounds in the scripts I use to maintain my LFS-based system. Can the names be made consistent for future releases? Simon. 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: persistent "enable wireless"
On Tue, 2007-04-17 at 20:11 -0500, Marcin Wojdyr wrote: > BTW I tried to download source from CVS, following instructions on the > webpage, but I got "Unknown host anoncvs.gnome.org." Gnome doesn't use CVS anymore - you'll need to grab the code from Subversion instead. See the following page: http://developer.gnome.org/tools/svn.html Simon. 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: Current SVN broken?
On Wed, 2007-03-28 at 19:54 +1200, Simon Geard wrote: > On Tue, 2007-03-27 at 14:49 +0300, Tambet Ingo wrote: > > Can you debug it and see why and where it aborts? It's been working > > fine for me and Dan for the whole time so it's not going to get > > magically fixed unless we know what's going on. > > My C debugging skills are a little rusty, but I'll see what I can > find... Ok, I don't think this is the problem I saw last time, but the current failure is that in real_write_supplicant_config(), the call to nm_ap_security_get_key() is returning NULL, causing a segmentation fault on the call to strlen() on line 162. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1212537152 (LWP 27036)] 0xb7c321d3 in strlen () from /lib/libc.so.6 (gdb) bt #0 0xb7c321d3 in strlen () from /lib/libc.so.6 #1 0x08070748 in real_write_supplicant_config (instance=0x809c4c0, config=0x80c1740, adhoc=0) at nm-ap-security-wpa-psk.c:162 #2 0x0805cb25 in real_act_stage2_config (dev=0x80c0088, req=0x80bf7c8) at nm-device-802-11-wireless.c:2705 The reason for the NULL appears to be that nothing has ever called nm_ap_security_set_key(). Is this a consequence of the nm-applet issues you mentioned? I'm not manually doing anything, but I assume the applet is what's telling NM to actually connect to my AP... Interestingly, a message printed out a little earlier indicates it thinks my AP is unencrypted, which is not the case. Could that be relevant? NetworkManager: Activation (ath0/wireless): access point 'X' is unencrypted, no key needed. Simon. 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: Current SVN broken?
On Tue, 2007-03-27 at 14:49 +0300, Tambet Ingo wrote: > Can you debug it and see why and where it aborts? It's been working > fine for me and Dan for the whole time so it's not going to get > magically fixed unless we know what's going on. My C debugging skills are a little rusty, but I'll see what I can find... > > and right now doesn't build (nm-client.c can't find > nm-marshal.h). > > Sorry, that was my fault, should be fixed now. Yes, builds fine, now, will test it when I get a chance (only one machine, so can't test it and stay online at the same time). > The current SVN trunk should mostly work, except manual activation of > wireless devices from nm-applet. If there's info about preferred > networks in GConf NM will activate it successfully. VPN also works > now. It's still not meant to be used by anyone but developers though, > since the configuration work described at > http://live.gnome.org/NetworkManagerConfiguration still hasn't been > implemented (and that's the reason why activation of wireless devices > doesn't work from nm-applet). Ok, thanks for the warning. Simon. 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: Current SVN broken?
On Tue, 2007-02-20 at 06:29 -0500, Dan Williams wrote: > On Tue, 2007-02-20 at 20:45 +1300, Simon Geard wrote: > > On Mon, 2007-02-19 at 14:54 +0200, Tambet Ingo wrote: > > > Don't use the SVN head. We know it's completely unstable. We'll > let you > > > know when it's usable again. > > > > Ok, I'll do that. Do you have any rough idea how long that might take - > > I don't mean dates, just whether it's days, weeks, or at worst, months. > > Hopefully days... though I was able to get it to associate with > unencrypted yesterday OK. It should at least start up, find your > devices, and if you have an instance of the applet (or another > info-daemon) running, it should connect if it can see that network. Ok, is there any prospect that SVN head might be functional any time soon? Every now and then I try building it, but at best it aborts after start, and right now doesn't build (nm-client.c can't find nm-marshal.h). I'd like to have a go at making the changes I discussed back in January (dealing with non-string SSIDs), but since then I've not managed to get a usable code base to work with. Simon. 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: Why I can't use NM (but want to)
On Tue, 2007-02-27 at 00:47 -0500, David R. Litwin wrote: > > > On 26/02/07, Simon Geard <[EMAIL PROTECTED]> wrote: > > This part is most likely due to the madwifi drivers, which > don't report > signal strength the same way as most other drivers. > > How so? Do you mean reporting the strength out of ninty-four? The quality value reported by iwlist? Yeah - my nearby AP shows only 19/94 (which NM reports as 22%), while one elsewhere in the neighbourhood reports 172/94 (reported as 100%). > Tell me, since we seem to be experiencing the same phenomena, what is your > setup? I have a Toshiba A70 lappy with atheros AR5212 > wireless card inside. > > Fiddling with the antenna sometimes helps, not sure why, since > it makes little difference to reported signal... > > I take it, then, that your set up is a destop. Yes, it's a desktop machine, using a PCI adapter with a small antenna sticking out of the back of the card. I don't recall exactly what brand/model it was, but lscpi descripts it as "Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)". > > Why is it, though, that I won't get kicked off and stay off with out > NM? WIth NM, if I get kicked off, its happiness all round to be > reconnected. Can't help there, sorry. I've found NM a *little* less robust when things go flaky, but a setup with nothing more than wireless_tools and wpa_supplicant still had problems. The only difference is that where NM eventually gives up, wpa_supplicant keeps trying forever - leaving me with an intermittent, but workable connection. But I've not had such problems for ages - possibly a result of improving drivers, don't know for sure. Simon. 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: Why I can't use NM (but want to)
On Sun, 2007-02-25 at 18:19 -0500, David R. Litwin wrote: > address, if I remember correctly.). With NM, I can not do this. > KNetworkManager shows the establlishment of a connexion to be at 57% > (if I'm lucky and it makes it past 28%) and then, as it tries to get > an IP, fails. This part is most likely due to the madwifi drivers, which don't report signal strength the same way as most other drivers. I've got the same problem - NM is currently reporting 15%, even though I'm only 5 or 6 metres from the access point. Oddly, I've got several much more distant access points with > 100% signal reported, which seems more than a little dubious. Anyway, I occasionally have problems with it continuously losing the connection, but things mostly work fine despite the supposedly poor signal. Fiddling with the antenna sometimes helps, not sure why, since it makes little difference to reported signal... Simon. 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: NM -- does it actually work?
On Fri, 2007-02-23 at 15:56 -0500, Ryan Novosielski wrote: > Is your SSID really that cryptic? That's uncommon in my experience -- > looks more like a WEP key to me, but I suppose they can be whatever you > want. As discussed in another recent thread, it's actually valid to have an SSID consisting of nothing more than eight zero-bytes. It currently crashes NM (something I'm working on fixing), but it's apparently a legitimate SSID. Simon. 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: Current SVN broken?
On Tue, 2007-02-20 at 06:29 -0500, Dan Williams wrote: > Hopefully days... though I was able to get it to associate with > unencrypted yesterday OK. It should at least start up, find your > devices, and if you have an instance of the applet (or another > info-daemon) running, it should connect if it can see that network. Might give it another try again today... > What version of wpa_supplicant are you running? 0.5.7 Simon. 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: Current SVN broken?
On Mon, 2007-02-19 at 14:54 +0200, Tambet Ingo wrote: > On Mon, 2007-02-19 at 21:03 +1300, Simon Geard wrote: > > Ok, I've given this a couple of weeks for recent changes to settle, but > > still finding trunk (rev 2337) completely unstable. It takes about 10 > > seconds to start up, going through the business of reconnecting to the > > system bus before aborting with the stacktrace. > > Don't use the SVN head. We know it's completely unstable. We'll let you > know when it's usable again. Ok, I'll do that. Do you have any rough idea how long that might take - I don't mean dates, just whether it's days, weeks, or at worst, months. Simon. 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: Current SVN broken?
On Tue, 2007-02-06 at 17:03 +1300, Simon Geard wrote: > I've just grabbed the latest NM code from SVN (revision 2287), finding > it badly broken for me. It builds fine, but crashes shortly after > startup, apparently just after retrieving scan results from > wpa_supplicant. > > Anyone else having problems with this? It's a clean snapshot from SVN, > with none of my code changes in it. I've attached a log, if that > helps... Ok, I've given this a couple of weeks for recent changes to settle, but still finding trunk (rev 2337) completely unstable. It takes about 10 seconds to start up, going through the business of reconnecting to the system bus before aborting with the stacktrace. An updated log is attached. Can anyone offer any suggestions as to the cause? The libhal issues seem an obvious concern, though I've no problems with HAL on other packages, including NM 0.6.4... Simon. lt-NetworkManager: starting... lt-NetworkManager: eth0: Device is fully-supported using driver 'forcedeth'. lt-NetworkManager: Now managing wired Ethernet (802.3) device 'eth0'. lt-NetworkManager: Deactivating device eth0. lt-NetworkManager: ath0: Device is fully-supported using driver 'ath_pci'. lt-NetworkManager: Now managing wireless (802.11) device 'ath0'. lt-NetworkManager: Deactivating device ath0. lt-NetworkManager: (eth0) supplicant interface is now in state 2 (from 1). lt-NetworkManager: (ath0) supplicant interface is now in state 2 (from 1). lt-NetworkManager: disconnected by the system bus. libhal.c 3031 : Error unsubscribing to signals, error=Connection is closed lt-NetworkManager: nm_hal_deinit(): libhal shutdown failed - Connection is closed lt-NetworkManager: dispatch_signal: assertion `sender != NULL' failed lt-NetworkManager: reconnected to the system bus. lt-NetworkManager: nm_dbus_manager_init_bus(): DBus Manager already has a valid connection. lt-NetworkManager: disconnected by the system bus. (lt-NetworkManager:26687): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `' (lt-NetworkManager:26687): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed lt-NetworkManager: nm_signal_handler(): Caught signal 11. Generating backtrace... lt-NetworkManager: *** START ** lt-NetworkManager: Frame 0: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x806fb25] lt-NetworkManager: Frame 1: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x806fcae] lt-NetworkManager: Frame 2: [0xb7f15420] lt-NetworkManager: Frame 3: /usr/lib/libgobject-2.0.so.0 [0xb7e25ed7] lt-NetworkManager: Frame 4: /usr/lib/libdbus-glib-1.so.2 [0xb7e96369] lt-NetworkManager: Frame 5: /usr/lib/libgobject-2.0.so.0(g_object_unref+0xcb) [0xb7e2614b] lt-NetworkManager: Frame 6: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x80635a7] lt-NetworkManager: Frame 7: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x8063bd5] lt-NetworkManager: Frame 8: /usr/lib/libglib-2.0.so.0 [0xb7db4e56] lt-NetworkManager: Frame 9: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x181) [0xb7db4881] lt-NetworkManager: Frame 10: /usr/lib/libglib-2.0.so.0 [0xb7db785f] lt-NetworkManager: Frame 11: /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1a7) [0xb7db7c07] lt-NetworkManager: Frame 12: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager(main+0xa52) [0x806c312] lt-NetworkManager: Frame 13: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7c057cc] lt-NetworkManager: Frame 14: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x8055171] lt-NetworkManager: *** END ** 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: Current SVN broken?
On Mon, 2007-02-05 at 23:59 -0500, Darren Albers wrote: > I just looked and rev 2287 is definitely trunk, I would stick with the > Release branch until Dan mentions that Trunk is ready for testing. I know it's trunk - I'm trying to make some changes in it (see my previous emails about non-string SSIDs). Thought at first my changes were responsible, but found the problem occurs on a fresh checkout too. Simon. 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: Errors running current SVN code
On Tue, 2007-02-06 at 07:43 -0500, Dan Williams wrote: > On Tue, 2007-02-06 at 13:46 +0200, Tambet Ingo wrote: > > Why not use HAL UDI for device names to get at least some sort of > > human-readable names? > > We could provide mapping functions, but this is mostly for the D-Bus > object paths for objects. HAL UDIs have / in them, which are object > paths. The full UDI path does, yes, but the name component of it would be fine. E.g, my machine has card has the following UDIs for network interfaces: /org/freedesktop/Hal/devices/net_00_01_29_82_08_a3 (eth0) /org/freedesktop/Hal/devices/net_00_11_95_be_05_03 (ath0) so NM could quite easily use net_00_01_29_82_08_a3 and net_00_11_95_be_05_03 for internal device names. They appear to be based on the MAC address, so should be fairly robust against device renaming. Simon. 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
Current SVN broken?
I've just grabbed the latest NM code from SVN (revision 2287), finding it badly broken for me. It builds fine, but crashes shortly after startup, apparently just after retrieving scan results from wpa_supplicant. Anyone else having problems with this? It's a clean snapshot from SVN, with none of my code changes in it. I've attached a log, if that helps... Simon. lt-NetworkManager: starting... lt-NetworkManager: eth0: Device is fully-supported using driver 'forcedeth'. lt-NetworkManager: Now managing wired Ethernet (802.3) device 'eth0'. lt-NetworkManager: Deactivating device eth0. lt-NetworkManager: ath0: Device is fully-supported using driver 'ath_pci'. lt-NetworkManager: Now managing wireless (802.11) device 'ath0'. lt-NetworkManager: Deactivating device ath0. lt-NetworkManager: (eth0) supplicant interface is now in state 2 (from 1). lt-NetworkManager: (ath0) supplicant interface is now in state 2 (from 1). lt-NetworkManager: disconnected by the system bus. libhal.c 3031 : Error unsubscribing to signals, error=Connection is closed lt-NetworkManager: nm_hal_deinit(): libhal shutdown failed - Connection is closed lt-NetworkManager: dispatch_signal: assertion `sender != NULL' failed lt-NetworkManager: reconnected to the system bus. lt-NetworkManager: nm_dbus_manager_init_bus(): DBus Manager already has a valid connection. lt-NetworkManager: disconnected by the system bus. (lt-NetworkManager:26687): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `' (lt-NetworkManager:26687): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed lt-NetworkManager: nm_signal_handler(): Caught signal 11. Generating backtrace... lt-NetworkManager: *** START ** lt-NetworkManager: Frame 0: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x806fb25] lt-NetworkManager: Frame 1: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x806fcae] lt-NetworkManager: Frame 2: [0xb7f15420] lt-NetworkManager: Frame 3: /usr/lib/libgobject-2.0.so.0 [0xb7e25ed7] lt-NetworkManager: Frame 4: /usr/lib/libdbus-glib-1.so.2 [0xb7e96369] lt-NetworkManager: Frame 5: /usr/lib/libgobject-2.0.so.0(g_object_unref+0xcb) [0xb7e2614b] lt-NetworkManager: Frame 6: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x80635a7] lt-NetworkManager: Frame 7: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x8063bd5] lt-NetworkManager: Frame 8: /usr/lib/libglib-2.0.so.0 [0xb7db4e56] lt-NetworkManager: Frame 9: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x181) [0xb7db4881] lt-NetworkManager: Frame 10: /usr/lib/libglib-2.0.so.0 [0xb7db785f] lt-NetworkManager: Frame 11: /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1a7) [0xb7db7c07] lt-NetworkManager: Frame 12: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager(main+0xa52) [0x806c312] lt-NetworkManager: Frame 13: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7c057cc] lt-NetworkManager: Frame 14: /home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager [0x8055171] lt-NetworkManager: *** END ** 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: Errors running current SVN code
On Mon, 2007-02-05 at 08:16 -0500, Dan Williams wrote: > nminfotest.c will be talking to the info-daemon, which happens to be > implemented by applets. Ok, so in order for nminfotest to run, an up to date copy of the applet needs to be running? Simon. 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: Errors running current SVN code
On Fri, 2007-02-02 at 23:18 +1300, Simon Geard wrote: > On Thu, 2007-02-01 at 07:51 -0500, Dan Williams wrote: > > On Thu, 2007-02-01 at 21:49 +1300, Simon Geard wrote: > > > And as I think about it, is that a meaningful distinction if we're not > > > going to pretend SSID is a string? > > > > That's exactly the reason. Since we no longer care, orig_essid can go > > away and we'll just use ssid everywhere. > > Thought so. Ok, I'll look at it over the weekend... Ok, making progress on this - everything compiles, and NetworkManager starts. Can't do very much with it though, since the D-Bus interfaces between it and nm-applet are pretty thoroughly broken - basically, everything that passed essid as DBUS_TYPE_STRING is now DBUS_TYPE_ARRAY, DBUS_TYPE_BYTE. Incidentally, what's happening with nm-applet at the moment? I went to try fixing the interfaces, but found everything had disappeared, apparently into a separate project? Is the network-manager-applet project in SVN basically everything that was in gnome/applet previously? One other question too - what exactly is the program nminfotest.c talking to? For example, if it complains that it can't find getNetworkEssid on org.freedesktop.NetworkManagerInfo, what should actually be providing that method when I run the test? Simon. 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: Errors running current SVN code
On Thu, 2007-02-01 at 07:51 -0500, Dan Williams wrote: > On Thu, 2007-02-01 at 21:49 +1300, Simon Geard wrote: > > And as I think about it, is that a meaningful distinction if we're not > > going to pretend SSID is a string? > > That's exactly the reason. Since we no longer care, orig_essid can go > away and we'll just use ssid everywhere. Thought so. Ok, I'll look at it over the weekend... Simon. 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: Errors running current SVN code
On Thu, 2007-02-01 at 21:44 +1300, Simon Geard wrote: > Incidentally, what's the difference between essid and orig_essid in that > struct? Is it simply that essid is guaranteed to be in UTF8 and > orig_essid might not be? And as I think about it, is that a meaningful distinction if we're not going to pretend SSID is a string? Simon. 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: Errors running current SVN code
On Wed, 2007-01-31 at 10:07 -0500, Dan Williams wrote: > We can change the internal stuff in 0.6, but we cannot change the DBus > interface. No problem there - 0.6 works fine for me, since I don't care about it ignoring the odd access point, as long as it can connect to my own without crashing. > See above. SSID will not and should not be part of the object path in > D-Bus, nor in GConf. Ok, that re-working this sounds a little beyond the scope of this bug. For the time being, I might settle for making sure the SSID always gets encoded correctly so as not to crash D-Bus. > Sure! I think the first step is to change NMAccessPoint so that the > 'ssid' member is a u8[32]. I'd also like to change 'essid' to 'ssid' > for NMAccessPoint too. No problem with the rename - that way any code that doesn't get changed doesn't compile, ensuring nothing accidentally gets missed. Incidentally, what's the difference between essid and orig_essid in that struct? Is it simply that essid is guaranteed to be in UTF8 and orig_essid might not be? > Furthermore, I'd like to change the name of NMAccessPoint, but I'm not > yet sure what to. NMBSSID is much more appropriate, but looks really > ugly. I'll leave that one for now... I'd rather not be making more changes at once than absolutely required, and I hate resolving merge conflicts... > Only for debugging output; since we won't be passing a "printable" SSID > outside of NM (it will always be a 32 item byte array over D-Bus), we > won't need to do this. Tools that interface with NM over D-Bus (the > applet) will of course need to figure out how to convert random SSIDs to > a printable string if only for a dropdown menu or entry of the SSID from > a CLI. In that case, Volker's suggestion of showing dots in place of unprintable characters is probably the most appropriate. I'll go with that, if there's no objections. Simon. 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: Errors running current SVN code
On Tue, 2007-01-30 at 12:13 -0500, Dan Williams wrote:
> Yeah; there are bits of NM that assume a string SSID, and those are
> going to get removed with 0.7 and the SSID will be a plain byte array.
More than just 'bits' of NM, so far as I can tell - pretty much every
piece of code I've encountered has assumed it's a string, starting with
the NMAccessPoint struct that gets passed around and accessed via
nm_ap_get_essid(). Much of it also does stuff like "if (essid)" to test
if one exists, all of that I guess broken. I guess the fix is to store
ssid_len in the struct, and add get/set functions for it.
Similar changes will be needed for the D-Bus interfaces, which
consistently treat the SSID as a string, and will presumably need to
treat it as a byte array instead?
They also use printf to format the SSID into the D-Bus paths for
invoking methods, which is what's causing my reported problem. E.g:
object_path = g_strdup_printf ("%s/%s/Networks/%s",
NM_DBUS_PATH_DEVICES,
nm_device_get_iface (dev),
nm_ap_get_essid (ap));
escaped_object_path = nm_dbus_escape_object_path (object_path);
g_free (object_path);
I assume some sort of encoding will be needed for the SSID passed here?
Would it be sufficient to use the same encoding as performed by
nm_dbus_escape_object_path, so that we end up with a value something
like
/org/freedesktop/NetworkManager/Devices/ath0/Networks/_0__0__0__0__0__0__0__0_ ?
Well, my C skills are a little rusty, but if nobody else has time to
pick this up, I can have a try.
> A blank SSID of all 0s is perfectly legal; we do need to figure out how
> to deal with this in UI. It's kind of an evil way of disguising your AP
> as a lot of user tools won't work with it. What does Windows and Mac OS
> X do here in their GUI bits? I don't mean the Linksys or DLink tools
> that you can install 3rd party, but what does the Airport menu show for
> this AP? If it doesn't show it, how do you connect to it on OS X?
It's not pretty, but how about the approach taken by wlanconfig? The
madwifi guys have basically declared that if the value is non printable
(any ASCII characters less than 0x20 or more than 0x7e), the whole thing
should just be rendered in hexadecimal. Is that practical for NM?
Anway, I'll update the bug (399292) I logged for this to reflect what
this discussion, to put a bit of detail in.
Simon.
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: Errors running current SVN code
On Tue, 2007-01-30 at 16:46 +1300, [EMAIL PROTECTED] wrote: > Dan Williams wrote: > > If you can build your own copy of wpa_supplicant, put some > > debugging prints in driver_wext.c in > > wpa_driver_wext_get_scan_results() in the 'case > > SIOCGIWESSID:' block to print out the code flow there. > > What's 'ssid_len'? Does the 'if (custom + ssid_len > > > end)' trigger? > > Will do. I'll also try using the same version of the > supplicant with NM 0.6.4, see if the problem occurs there, > see if it's the 0.5.7 supplicant in general, or just the > D-Bus code. Ok, I've done some experimenting, particularly on my currently working system - NM 0.6.4, wpa_supplicant 0.5.7, and various recent madwifi drivers. NM isn't crashing, but it looks like there might really be an access point out there with a blank ESSID - it shows up in wlanconfig (which shows it as 0x0), iwlist, and wpa_supplicant. NM doesn't show it at all. So, what does this suggest? Same versions of madwifi and wpa_supplicant, NM 0.6.4 works and 0.7 doesn't? Does the 0.6.4 code that talked to the supplicant do some kind of validation that 0.7 doesn't? Does 0.6.4 use strlen() to get the length of the ESSID string, instead of having it passed as a parameter? If it offers any ideas, the iwlist command reports the odd AP as: Cell 09 - Address: 00:40:96:37:3B:F4 ESSID:"" Mode:Master Frequency:2.447 GHz (Channel 8) Quality=3/94 Signal level=-92 dBm Noise level=-95 dBm Encryption key:off Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s Extra:bcn_int=100 Simon. 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: Errors running current SVN code
On Sat, 2007-01-27 at 07:14 -0500, Dan Williams wrote: > dbus-send --system --dest=org.freedesktop.NetworkManager \ > --print-reply /org/freedesktop/NetworkManager/Devices/ath0 \ > org.freedesktop.NetworkManager.Devices.getProperties > > See if any of the network object paths look funny. Indeed, they do - this command includes various normal networks, and sometimes (not consistently) includes the invalid one. Tracing back, it appears that the problem originates either in wpa_supplicant, or in the code that talks to it. My debugging shows supplicant_iface_scanned_ap_cb() in nm-device-802-11-wireless.c is being called where the ssid entry has entry.array_len equal to 8, but where the entire entry.bytearray_value is zeroed. Any ideas? This is running version 0.5.7 of wpa_supplicant, if that helps. Simon. 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
Errors running current SVN code
Trying to get the current NM code to work on my LFS system, with some custom code to support LFS. I've hit a couple of bugs which I've logged in Bugzilla. http://bugzilla.gnome.org/show_bug.cgi?id=394956 http://bugzilla.gnome.org/show_bug.cgi?id=399292 The first, 393956, I've included a patch for - I'd appreciate it if someone could review the change and commit it. The second I'm trying to investigate, and wondering if someone can offer some advice on where to look. Basically, nm-applet fails shortly after startup, killed due to libdbus asserting against an invalid parameter. The D-Bus call in question is getProperties on the interface org.freedesktop.NetworkManager.Devices. Monitoring D-Bus, I see three calls to this method, using the following paths: /org/freedesktop/NetworkManager/Devices/ath0/Networks/foo /org/freedesktop/NetworkManager/Devices/ath0/Networks/bar /org/freedesktop/NetworkManager/Devices/ath0/Networks/ The first two appear to be fine, but the third causes the assertion failure, presumably because it's calling without an essid appended. Can someone suggest where these path strings are being created, and where the essid is supposed to come from? Simon. 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: NetworkManager make errors and DBUS
On Thu, 2007-01-11 at 10:28 +0100, Timo Hoenig wrote: > That's why closing a shared connection shall not be done but is alright > for a private connection. > Ah, I see now. Thanks for the clarification. Simon. 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: NetworkManager make errors and DBUS
On Wed, 2007-01-10 at 11:00 -0500, Dan Williams wrote: > Except that dbus_connection_close() is deprecated and you'll get a > message yelling at you (and possibly a crash) when it's used. The > stable branch tip has the correct fixes for that: Oh, ok, hadn't heard that one. So, dbus_connection_disconnect() became _close(), and has now been replaced with _unref()? It's a straight name change, nothing else needed to fix the code that calls the wrong version? Simon. 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: NetworkManager make errors and DBUS
On Tue, 2007-01-09 at 22:44 +, Eugéne Suter wrote:
> The OP was told that DBUS 1.0 needs a patch, but I'm using DBUS 1.0.1,
> so shouldn't that already be fixed?
It's not that D-Bus 1.0 needs a patch - it's that NM needs a patch in
order to work with the newer D-Bus.
> If I do need to apply the patch, where can I get it and how can I
> apply it to the dbus source, so that I can rebuild my DBUS package?
I've attached the one I've been using, which fixes a couple of D-Bus
compatibility issues. To apply it, save it somewhere, and run the
following command from within the NM source tree:
patch -Np1 -i /path/to/patch/NetworkManager-0.6.4-dbus_api.patch
Then configure and build as normal.
Simon.
diff -Naur NetworkManager-0.6.4/gnome/libnm_glib/libnm_glib.c NetworkManager-0.6.4-new/gnome/libnm_glib/libnm_glib.c
--- NetworkManager-0.6.4/gnome/libnm_glib/libnm_glib.c 2006-05-06 03:36:46.0 +1200
+++ NetworkManager-0.6.4-new/gnome/libnm_glib/libnm_glib.c 2006-07-27 21:37:45.0 +1200
@@ -230,7 +230,7 @@
{
/* Try to reactivate our connection to dbus on the next pass through the event loop */
ctx->nm_state = LIBNM_NO_DBUS;
- dbus_connection_disconnect (ctx->dbus_con);
+ dbus_connection_close (ctx->dbus_con);
libnm_glib_schedule_dbus_watcher (ctx);
}
else if (dbus_message_is_signal (message, DBUS_INTERFACE_DBUS, "NameOwnerChanged"))
@@ -444,7 +444,7 @@
g_main_loop_unref (ctx->g_main_loop);
if (ctx->dbus_con)
- dbus_connection_disconnect (ctx->dbus_con);
+ dbus_connection_close (ctx->dbus_con);
if (ctx->callbacks_lock)
g_mutex_free (ctx->callbacks_lock);
diff -Naur NetworkManager-0.6.4/src/NetworkManagerDbus.c NetworkManager-0.6.4-new/src/NetworkManagerDbus.c
--- NetworkManager-0.6.4/src/NetworkManagerDbus.c 2006-05-22 05:28:02.0 +1200
+++ NetworkManager-0.6.4-new/src/NetworkManagerDbus.c 2006-11-13 19:37:05.0 +1300
@@ -831,10 +831,10 @@
}
dbus_error_init (&error);
-#if (DBUS_VERSION_MAJOR == 0) && (DBUS_VERSION_MINOR >= 60)
- flags = DBUS_NAME_FLAG_DO_NOT_QUEUE; /* Prohibit replacement is now the default */
-#else
+#if (DBUS_VERSION_MAJOR == 0) && (DBUS_VERSION_MINOR < 60)
flags = DBUS_NAME_FLAG_PROHIBIT_REPLACEMENT;
+#else
+ flags = DBUS_NAME_FLAG_DO_NOT_QUEUE; /* Prohibit replacement is now the default */
#endif
ret = dbus_bus_request_name (connection, NM_DBUS_SERVICE, flags, &error);
if (dbus_error_is_set (&error))
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: No icon on update notifier aera
On Sun, 2006-12-10 at 18:09 -0500, Dan Williams wrote: > Right; that's the crux of the problem. Nothing is authorized to access > NetworkManager. It won't work until we get some of the security access > files in place in /etc/dbus-1/system.d. > > The files you attached appear to be blank. Can you verify that they are > indeed present on your computer? Dan - are you using Evolution to read mail? They're not blank, but Evolution (for me) is identifying them as HTML files for some reason, and attempting to display them as such. Opened in a text editor, they're fine. Jerume - by the look of the file, the NM dbus services are accessible by members of a 'netdev' group. Try add your user to this group, log out, and try again. Simon. 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
Compile error in HEAD, deprecated dbus_message_iter_get_array_len
Trying to build NM from HEAD, getting the following complaint: cc1: warnings being treated as errors dbus-dict-helpers.c: In function '_nmu_dbus_dict_entry_get_array': dbus-dict-helpers.c:652: warning: 'dbus_message_iter_get_array_len' is deprecated (declared at /usr/include/dbus-1.0/dbus/dbus-message.h:176) I can build by disabling -Werror, but since this option is enabled by default, has anyone got a fix for the problem? It's building against dbus 1.0.1. Simon. 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: NetworkManager + Madwifi in Debian - Can't Get IP
On Sun, 2006-11-26 at 15:38 -0500, Carlos Moffat wrote: > Also, is -iwifi0 the correct interface, or is it -iath0? I have both... NM (and anything else) should be using ath0. Not sure what the wifi0 interface is, but it's not something I've ever needed to look at either... Simon. 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: AW: AW: Error during compiling: g_slice_alloc0
On Thu, 2006-08-31 at 08:43 +0200, "Weßeling, Christofer" wrote: > I've still done: > > ./configure > make > make install > > with the glib-2.12.2 package, but I still get this error... It should be > more new than 2.10 But if i type: "/opt/gnome/bin/glib-config --version" I > get 1.2.10 Forget glib-config - it's a relic from the older glib1, which isn't relevant. What's probably at issue is that while you've installed glib-2.12.2 to /usr/local, the version provided by your distro is probably in /usr, and is being seen first. Try running: pkg-config --variable=prefix --modversion glib-2.0 and see what returns. Chances are it's something like 2.10.0 and /usr. Simon. 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: [Patch] dbus sysconfdir default value
On Fri, 2006-07-07 at 20:26 +0200, Timothée Lecomte wrote: > Hmm, actually please forget this patch. Even if it is the right place to > install the dbus configuration files, it will break 'make distcheck' and > more generally any non-root install (even if a non-root install does not > make much sense for NetworkManager, right ?). > > Too bad that there isn't a nicer "autotools-way" to deal with these system > paths, but the explicit --sysconfdir seems to be the right solution. You could try using pkg-config to identify the sysconfdir used for dbus pkg-config dbus-1 --variable=sysconfdir Simon. 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: Association timeout with madwifi
On Wed, 2006-06-28 at 23:03 -0400, Tom Diehl wrote: > I also added the following to /etc/sysconfig/wpa_supplicant: > INTERFACES="-iath0" > DRIVERS="-Dmadwifi" > > I do not recall if that was really necessary but I looked in my working > config and it is in there. Does that work if you use -Dwext instead? I was unable to use NM for ages due to madwifi's lack of support for the latest extensions, and had to use wpa_supplicant manually with -Dmadwifi. As of a couple of months ago though, they fixed the drivers enough that -Dwext worked with them, and thus NM started working. Simon. 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: Backends and OO principles
On Mon, 2006-05-29 at 11:52 +0200, Ikke wrote: > Everyone's allowed to dream once in a while ;-). Whilst the idea is > good, I dont think it'll happen soon: every distro thinks their system > is best suited for their userbase I guess? Yup, which is why I'm using LFS in the first place... I *could* have just modified my system to be compatible with Redhat or any of the others, but thought it'd be more interesting to try porting NM to LFS. Simon. 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: Backends and OO principles
On Sat, 2006-05-27 at 14:43 +0200, Ikke wrote: > If the NM devs 'd think this is a good idea, I'd be willing to work on > implementing this, as long as my SoC mentor agrees :-) I'm not an NM dev, but it seems reasonable to me. I've done a bit of work getting NM to work on my LFS box, and most of my patches consist of duplicating the contents of the Redhat backend and changing a few things to suit the different /etc layout. It'd be a lot easier to maintain if I could simply override a few functions in the Redhat one. Of course, another school of thought says it's ridiculous having half a dozen different backends in the first place and that things would be a lot easier if distros could be a bit more consistent. But that's just crazy talk... :) Simon. 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: [patch] my latest wireless drivers workaround patch.
On Thu, 2006-05-11 at 15:52 -0400, Robert Love wrote: > Here it is. A bunch of crap we sadly should never need but > unfortunately do. Is it still necessary to include special-casing for madwifi, given their newer drivers appear to work pretty well on wext? Apart from the signal strength reporting issue, I'm pretty happy with how NM is working on my Atheros-based card... Simon. 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: DHCP transaction timing out, even though working
On Mon, 2006-04-24 at 21:04 +1200, Simon Geard wrote: > Hi all... > > I've spent a little effort lately in getting NetworkManager to work on a > LinuxFromScratch-based desktop, using a variant of the Redhat backend. I > don't think this is the area failing, I mention it only as background. > > > When I try to connect to an AP, I get the password prompt, then I see a > lot of output from wpa_supplicant. That settles down, then sometime > later I get: > > NetworkManager:Device 'ath0' DHCP transaction took too > long (>45s), stopping it. In case I've trimmed that too much to be useful, here's a bit more of the output... NetworkManager:Device 'ath0' DHCP transaction took too long (>45s), stopping it. NetworkManager:Activation (ath0) Stage 4 of 5 (IP Configure Timeout) scheduled... NetworkManager:DHCP daemon state is now 14 (normal exit) for interface ath0 NetworkManager:DHCP daemon state is now 14 (normal exit) for interface ath0 NetworkManager:Activation (ath0) Stage 4 of 5 (IP Configure Timeout) started... NetworkManager: [1145867955.378318] real_act_stage4_ip_config_timeout (): Activation (ath0/wireless): could not get IP configuration info for 'XYZZY', asking for new key. NetworkManager:Activation (ath0) New wireless user key requested for network 'XYZZY'. NetworkManager:Activation (ath0) Stage 4 of 5 (IP Configure Timeout) complete. NetworkManager:Activation (ath0) New wireless user key request for network 'XYZZY' was canceled. NetworkManager:Deactivating device ath0. Simon. 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
DHCP transaction timing out, even though working
Hi all... I've spent a little effort lately in getting NetworkManager to work on a LinuxFromScratch-based desktop, using a variant of the Redhat backend. I don't think this is the area failing, I mention it only as background. When I try to connect to an AP, I get the password prompt, then I see a lot of output from wpa_supplicant. That settles down, then sometime later I get: NetworkManager:Device 'ath0' DHCP transaction took too long (>45s), stopping it. However, this appears spurious, since before it gives up with the timeout, the dhclient process has been started (by dhcdbd), and the connection is working fine. So, can anyone suggest why NM is timing out? This is NM 0.6.2, running on madwifi drivers (recent enough to run wpa_supplicant with the wext driver). Everything works fine if I run things manually instead of using NM. Simon Geard. 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
