RE: From ethernet to PPP Internet access
That is good. Huawei E220 and Vodafone uses PPP protocol (the Huawei E220 driver is included in the 2.6 Kernel also). Regards. -Mensaje original- De: Dan Williams [mailto:[EMAIL PROTECTED] Enviado el: lunes, 04 de febrero de 2008 13:28 Para: Pedro Macanás CC: 'Gabriele Monti'; networkmanager-list@gnome.org Asunto: Re: From ethernet to PPP Internet access On Mon, 2008-02-04 at 13:14 +0100, Pedro Macanás wrote: Can I disable DHCP and ethernet access to the Internet using the network manager, because I now use PPP (HSDPA)in my Vodafone mobile internet (Huawei E220 USB modem wih wvdial). The development version of NetworkManager does have some support for GSM and CDMA mobile broadband cards. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] NM DBUS api documentation build system
On Feb 5, 2008 8:46 AM, Will Stephenson [EMAIL PROTECTED] wrote: snip I haven't actually added any api documentation yet. I'm working on supporting NM 0.7 in KDE 4 and would do so as I grok 0.7. The patch just replicates the status quo with the ability to add api docs. The system can also add a make check target to assure the docu generation is working but I haven't adapted/copied that yet. Another question is, are you interested in async glib binding support? The system can apparently generate separate async introspection xml but I haven't adapted that either yet as I'm not familiar with the glib bindings. I've tested this locally. Dan, Tambet: what do you think about integrating it? It would make NM client developement much easier. While I'd like to have always up to date documentation, I'm not sure I like this. The patch you sent only removes the introspection XML we currently have and adds some XSLT which I can't read (and thus maintain). It'll make development easier only if someone actually writes that documentation, just converting to more magic makes things harder to understand. And again, I like having documentation as much as anyone, but since we have two developers in total (who are busy with maintenance work for a lot of time), I personally would rather write code. So if anyone wants to help with documentation, it could live in a text file for now. When it has enough information, and if Dan feels comfortable maintaining XSLT, I wouldn't have anything against the proposed solution. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] NM DBUS api documentation build system
Hi Tambet, I haven't actually added any api documentation yet. I'm working on supporting NM 0.7 in KDE 4 and would do so as I grok 0.7. The patch just replicates the status quo with the ability to add api docs. The system can also add a make check target to assure the docu generation is working but I haven't adapted/copied that yet. Another question is, are you interested in async glib binding support? The system can apparently generate separate async introspection xml but I haven't adapted that either yet as I'm not familiar with the glib bindings. I've tested this locally. Dan, Tambet: what do you think about integrating it? It would make NM client developement much easier. While I'd like to have always up to date documentation, I'm not sure I like this. The patch you sent only removes the introspection XML we currently have and adds some XSLT which I can't read (and thus maintain). It'll make development easier only if someone actually writes that documentation, just converting to more magic makes things harder to understand. And again, I like having documentation as much as anyone, but since we have two developers in total (who are busy with maintenance work for a lot of time), I personally would rather write code. So if anyone wants to help with documentation, it could live in a text file for now. When it has enough information, and if Dan feels comfortable maintaining XSLT, I wouldn't have anything against the proposed solution. I must agree here. Something that generate the introspection is not helpful at all. It is hard enough to keep external introspection XML files in sync with the actual runtime introspection. Why should we have another thing to maintain. If you could generate the introspection files from within the source code, that is a different story. Something in combination with Doxygen. Regards Marcel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Wired NIC bridged through WLAN AP doesn't auto-connect
Platform: Intel Celeron, Ubuntu 7.10, linux-image-2.6.22-14-generic 2.6.22-14.51 network-manager0.6.5-0ubuntu16.7.10.0 network-manager-gnome 0.6.5-0ubuntu10 I have an ubuntu 7.10 machine that has a wired NIC. This wired NIC is connected to a WLAN that is set up for bridging with another AP connected to my home LAN. If I log into the Ubuntu machine, the nm-applet wired icon is displayed with a white-x-on-red marking its disconnected state. If I right click the icon and select the Wired network (which is always initially unchecked), the icon starts spinning, and eventually shows up as connected. The wired NIC is set up as Roaming. Does anyone have an idea why the Wired network isn't initially enabled when logging in? Does anyone have any theories? Could it be because the connection is through the bridged AP? Could it be because the (presumably old) NIC on the machine has a problem detecting a network connected state from the AP? Could it be because of a network manager setting? I have googled and read the logs, but I don't really know where the problem might be, so I'm flailing about in the dark. So... any hints, guesses, documentation pointers etc. are welcome! Thanx! - Steinar ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
