Re: Asus EeePC
On Thu, 2007-12-27 at 01:45 -0500, Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anyone used one of these things yet? I'm curious whether NetworkManager 0.6.5 could be easily made to work on it. It runs Xandros, with some sort of custom IceWM for a Window manager. Someone I know bought one and wants me to get them on a WPA-Enterprise network... just looking for the easiest path. I've seen/used one with a Fedora 8 install on it (reformatted/reinstalled of course) and NM works there. One issue is that neither wired nor wireless card is yet supported by upstream in-kernel drivers. The wired card driver (atl2 I think?) is in the process of being upstreamed, and the ath5k driver doesn't yet support PCI-E which is the Atheros part's connection method on the EeePC. Out of the box, I'd imagine NM would work presuming a sufficient D-Bus version was installed, the wireless driver supports WEXT correctly, and there was a place to put a notification area (or you run knetworkmanager). Dan =R - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHc0ojmb+gadEcsb4RAhvwAJ9I+xMz2xvgDTsDdh2gw6ZZFS/lhQCfYt+v bKkHV3+6zUDdU5ZMECO8a40= =xz8H -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proposed ad-hoc channel bug patch
On Tue, 2007-12-25 at 18:22 +0200, Ohad Lutzky wrote: On Dec 25, 2007 4:03 PM, Dan Williams [EMAIL PROTECTED] wrote: On Tue, 2007-12-25 at 10:29 +0200, Ohad Lutzky wrote: Hi Dan, Thanks for the info. A few questions - * Is there any chance indeed that the feature will be backported into wpa_supplicant 0.5.x? Or is it a big restructuring of wpa_sup which will make this very difficult? No, it's pretty easy and fairly contained. It's just the config option and the driver hooks for setting the frequency. * Which version of NM uses wpa_supplicant 0.6.x, with the new feature? Is a GUI for setting the channel present? Is any sort of channel set for ad-hoc mode? No version of NM requires 0.6.x. All the D-Bus interface work has been done on wpa_supplicant 0.5.7 and later but the changes also get applied to the 0.6.x branch. NM does not yet honor the channel setting for either adhoc or infrastructure mode because the backend wpa_supplicant support is not yet there. I'm not sure I understand... is the wpa_supplicant support for channel setting there in 0.6.x or not? When can we expect NM to use this support? I'm trying to use NM from my application which uses ad-hoc networking heavily (a port of a Windows application, specifically), and current behavior is completely broken for all of the cards I have. Would it be acceptable to use this patch downstream (Debian, Ubuntu) for the time being? Assuming you have the patch I previously sent applied to your wpa_supplicant, NetworkManager and the NM gnome applet from SVN now support creating Ad-Hoc networks. I haven't tested WEP or WPA security yet but it works so far to create an open Ad-Hoc network with an ipw2200 card. Dan Dan Much thanks, Ohad. On Dec 25, 2007 12:57 AM, Dan Williams [EMAIL PROTECTED] wrote: On Thu, 2007-12-20 at 10:55 +0200, Ohad Lutzky wrote: Hi all, Apparently it's not a WPA issue after all. Please check patch attached here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/112009/comments/12 Contrary to the bug report, it's _totally_ a wpa_supplicant issue. wpa_supplicant 0.6.x has the required config option, it needs to be backported to wpa_supplicant 0.5.x. NM should _not_ be setting any wireless attributes like channel, BSSID, or SSID itself. So the patch is wrong. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
OpenVPN with DHCP
Hi list, I'm trying to connect to a openvpn server. This server is set up to use the companies DHCP server (dnsmasq) to provide IPs to the VPN clients. From what I understand (reading the error message of nm-applet) NetworkManager currently relies on using OpenVPNs internal DHCP server. Is that true? I use OpenVPN to establish a connection and provide me a tap0 interface. After that I use a DHCP-client to get an adress for the tap0. Is NetworkManager able to use OpenVPN just as a transport layer? - Example client configuration: - remote XXX proto tcp-client port 1194 client dev tap0 verb 3 persist-tun persist-key status /tmp/openvpn-status.log log-append /var/log/openvpn.log ca /etc/openvpn/XXX/ca.crt cert /etc/openvpn/XXX/YYY.crt key /etc/openvpn/XXX/YYY.key pull resolv-retry infinite ns-cert-type server tls-remote XXX - Example server configuration: - proto tcp-server port 1194 mode server dev tap0 verb 3 persist-tun persist-key user openvpn group openvpn tls-server status /tmp/openvpn-status.log log-append /var/log/openvpn.log ca /etc/openvpn/XXX/ca.crt cert /etc/openvpn/XXX/YYY.crt key /etc/openvpn/XXX/YYY.key dh /etc/openvpn/XXX/YYY.pem client-to-client push dhcp-option DNS 192.X.Y.Z push dhcp-option DOMAIN XXX.YYY.ZZZ keepalive 10 120 max-clients 20 Thanks and keep up the good work, Christoph Brill ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Asus EeePC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Thu, 2007-12-27 at 01:45 -0500, Ryan Novosielski wrote: Anyone used one of these things yet? I'm curious whether NetworkManager 0.6.5 could be easily made to work on it. It runs Xandros, with some sort of custom IceWM for a Window manager. Someone I know bought one and wants me to get them on a WPA-Enterprise network... just looking for the easiest path. I've seen/used one with a Fedora 8 install on it (reformatted/reinstalled of course) and NM works there. One issue is that neither wired nor wireless card is yet supported by upstream in-kernel drivers. The wired card driver (atl2 I think?) is in the process of being upstreamed, and the ath5k driver doesn't yet support PCI-E which is the Atheros part's connection method on the EeePC. Out of the box, I'd imagine NM would work presuming a sufficient D-Bus version was installed, the wireless driver supports WEXT correctly, and there was a place to put a notification area (or you run knetworkmanager). Well, I'll try to take a good look at this thing when I get it. Maybe the information can be of help in some way. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHc7dgmb+gadEcsb4RAr0BAKDYXndUm4ljf2meETlrvxyl+13mdgCfVt1L AV5HnBJ+sIx7fnfHk5WuovI= =PKEh -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer III tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Surprise - olpc sugar uses NM
I was surprised to see that the olpc running the sugar operating system runs NM. olpc (product of the one computer one child project) if MIT's Negroponte. The idea is to mass produce cheap computers for children in third world countries. The connection interface is interesting. It is a screen of colored dots each one a AP or a mesh connection, which is a connection to another olpc.It is more colorful than NM-applet. -- === Common sense is the most evenly distributed quantity in the world. Everyone thinks he has enough. -- Descartes, 1637 === Aaron Cost telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Surprise - olpc sugar uses NM
On Thu, Dec 27, 2007 at 09:53:25AM -0600, Aaron Konstam wrote: I was surprised to see that the olpc running the sugar operating system runs NM. olpc (product of the one computer one child project) if MIT's Negroponte. The idea is to mass produce cheap computers for children in third world countries. The connection interface is interesting. It is a screen of colored dots each one a AP or a mesh connection, which is a connection to another olpc.It is more colorful than NM-applet. I just received one of these but have not had much time with it. I did notice that the display showed my local access points, but also displayed a few mesh connections. I doubt that there are really any around. In my quick attempt I was not able to get the wireless to work on my WPA-enabled access point. Do you have any tips? -- Bill Moseley [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Surprise - olpc sugar uses NM
On Thu, Dec 27, 2007 at 10:15:57AM -0800, Bill Moseley wrote: On Thu, Dec 27, 2007 at 09:53:25AM -0600, Aaron Konstam wrote: I was surprised to see that the olpc running the sugar operating system runs NM. olpc (product of the one computer one child project) if MIT's Negroponte. The idea is to mass produce cheap computers for children in third world countries. Not such a big surpise. One of the upstream authors of NM used to work on the OLPC project :) The connection interface is interesting. It is a screen of colored dots each one a AP or a mesh connection, which is a connection to another olpc.It is more colorful than NM-applet. I just received one of these but have not had much time with it. I did notice that the display showed my local access points, but also displayed a few mesh connections. I doubt that there are really any around. There are always three mesh connections available in the meshview. Those represent mesh networks on different channels (if you hover over it, you'll see).. Mesh networks are created as soon as one or more nodes ``join'' one. In my quick attempt I was not able to get the wireless to work on my WPA-enabled access point. Do you have any tips? There are/were some issues with WPA and WEP. I'm not sure in which builds these problems occur. Search for WEP and WPA on dev.laptop.org, it should have the needed information. Sjoerd -- We warn the reader in advance that the proof presented here depends on a clever but highly unmotivated trick. -- Howard Anton, Elementary Linear Algebra ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
getting VPN passwords from a script?
I'm using a Softoken one-time key generator to access a VPN. I'm using KNetworkManager. To start the VPN, I run Softoken under Wine, see the key, and type both that and the Group Password into KNetworkManager. (For some reason, KNetMan doesn't do cut and paste, though nm-applet does.) Is it possible, using KNetMan or any other UI, to get NetworkManager to run an arbitrary script to acquire the VPN's password and group password? I don't mind some coding, but could use some suggestions on where to start. Thanks. -- Bob Miller Kbob [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proposed ad-hoc channel bug patch
Thank you dan! We will probably be testing those this week as well. On Dec 27, 2007 10:16 AM, Dan Williams [EMAIL PROTECTED] wrote: On Tue, 2007-12-25 at 18:22 +0200, Ohad Lutzky wrote: On Dec 25, 2007 4:03 PM, Dan Williams [EMAIL PROTECTED] wrote: On Tue, 2007-12-25 at 10:29 +0200, Ohad Lutzky wrote: Hi Dan, Thanks for the info. A few questions - * Is there any chance indeed that the feature will be backported into wpa_supplicant 0.5.x? Or is it a big restructuring of wpa_sup which will make this very difficult? No, it's pretty easy and fairly contained. It's just the config option and the driver hooks for setting the frequency. * Which version of NM uses wpa_supplicant 0.6.x, with the new feature? Is a GUI for setting the channel present? Is any sort of channel set for ad-hoc mode? No version of NM requires 0.6.x. All the D-Bus interface work has been done on wpa_supplicant 0.5.7 and later but the changes also get applied to the 0.6.x branch. NM does not yet honor the channel setting for either adhoc or infrastructure mode because the backend wpa_supplicant support is not yet there. I'm not sure I understand... is the wpa_supplicant support for channel setting there in 0.6.x or not? When can we expect NM to use this support? I'm trying to use NM from my application which uses ad-hoc networking heavily (a port of a Windows application, specifically), and current behavior is completely broken for all of the cards I have. Would it be acceptable to use this patch downstream (Debian, Ubuntu) for the time being? Assuming you have the patch I previously sent applied to your wpa_supplicant, NetworkManager and the NM gnome applet from SVN now support creating Ad-Hoc networks. I haven't tested WEP or WPA security yet but it works so far to create an open Ad-Hoc network with an ipw2200 card. Dan Dan Much thanks, Ohad. On Dec 25, 2007 12:57 AM, Dan Williams [EMAIL PROTECTED] wrote: On Thu, 2007-12-20 at 10:55 +0200, Ohad Lutzky wrote: Hi all, Apparently it's not a WPA issue after all. Please check patch attached here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/112009/comments/12 Contrary to the bug report, it's _totally_ a wpa_supplicant issue. wpa_supplicant 0.6.x has the required config option, it needs to be backported to wpa_supplicant 0.5.x. NM should _not_ be setting any wireless attributes like channel, BSSID, or SSID itself. So the patch is wrong. Dan -- Man is the only animal that laughs and weeps, for he is the only animal that is struck with the difference between what things are and what they ought to be. - William Hazlitt Ohad Lutzky ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
