On Thu, 2011-02-10 at 08:33 +0800, ms zaryna wrote:
> Hi,
> I'm running Ubuntu 10.10 on my laptop, and been using network manager
> for couple of years. It's been working just fine until several days
> ago. I'm using mobile broadband with USB modem(Vodafone K-3565-Z), and
> it was able to detect an
Hi,
I'm running Ubuntu 10.10 on my laptop, and been using network manager for
couple of years. It's been working just fine until several days ago. I'm
using mobile broadband with USB modem(Vodafone K-3565-Z), and it was able to
detect and connect to internet ok, but then after like 2 minutes, it l
On 09.02.2011 18:40, Dan Williams wrote:
In current NM 0.8.x git, if you uncheck "Enable Wireless" from the menu,
NM writes that to the state file. That will then be in-force until you
re-check "Enable Wireless", even across reboots. This takes precedence
over rfkill because it was an explici
On Wed, 2011-02-09 at 16:47 +, Marc Herbert wrote:
> Le 09/02/2011 15:39, Shawn J. Goff a écrit :
> > I'm on a network with two DHCP servers and can't connect using Network
> > Manager. I performed a Wireshark capture and saw a DHCP request from me
> > followed by a DHCP ack from one server a
On Sat, 2011-02-05 at 22:00 -0800, Dan O'Connor wrote:
> Can you clarify what I need to do in my driver's config.mk file? The
> only reference to network manager I saw was the following:
>
>
>
> # Support Native WpaSupplicant for Network Maganger [sic]
> HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
Corr
On Mon, 2011-02-07 at 22:45 +0200, Ozan Çağlayan wrote:
> Correct logging domain for RFKILL is RFKILL not RKILL.
Pushed:
e9c8ba4e3dde7332fb1002fa54cda93166aa04cb (master)
49bdcc31bed237619aa28c814ee52e371c79aada (0.8.x)
Thanks!
Dan
> Also fix the man page.
> ---
> man/NetworkManager.conf.5.in
On Mon, 2011-02-07 at 22:45 +0200, Ozan Çağlayan wrote:
> syslog already ensures that the messages are splitted by \n
> boundaries. Appending another \n in NM pollutes the logging:
Pushed:
90493585795d8b60eab91bd1ed359d61b57617c6 (master)
251731ef5b17394fb0e99e8636672b9e6a5bb404 (0.8.4)
Thanks!
Le 09/02/2011 15:39, Shawn J. Goff a écrit :
> I'm on a network with two DHCP servers and can't connect using Network
> Manager. I performed a Wireshark capture and saw a DHCP request from me
> followed by a DHCP ack from one server and a DHCP nak from the other. I
> did the same thing with dhcl
On Mon, 2011-01-31 at 17:43 +0100, toabctl wrote:
> Hi,
>
> i ude NetworkManager on an embedded device and don't need policykit.
> Is it possible to use network-manager without policykit?
>
> I've written a Client with libnm-glib and libnm-util and when i want
> to use the client, i get:
>
> WA
On Thu, 2011-02-03 at 13:00 +0200, Ozan Çağlayan wrote:
> Hi,
>
> I have bug reports about some inconsistencies caused by the state file and
> rfkill
> interactions like when the user kills the radio and then re-enables it, the
> WLAN can't be enabled
> unless the state file is edited manually a
On Tue, 2011-02-08 at 18:05 +0100, Harald Jung wrote:
> Hi,
>
> the networkmanager i've built from the current git isn't able to get the
> aviable access points via the new wpa_supplicant api (0.7.3).
>
> The scan request is initiated via dbus, but i think it doesn't listen for
> dbus
> events
Hi,
the networkmanager i've built from the current git isn't able to get the
aviable access points via the new wpa_supplicant api (0.7.3).
The scan request is initiated via dbus, but i think it doesn't listen for dbus
events from wpa_supplicant.
dbus: fi.w1.wpa_supplicant1.Interface.Scan
(/fi
Can you clarify what I need to do in my driver's config.mk file? The only
reference to network manager I saw was the following:
# Support Native WpaSupplicant for Network Maganger [sic]
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
I have not tried the rt2x00 driver, the wiki main page does not mention my
I'm on a network with two DHCP servers and can't connect using Network
Manager. I performed a Wireshark capture and saw a DHCP request from me
followed by a DHCP ack from one server and a DHCP nak from the other. I
did the same thing with dhclient and saw the exact same packets, but
then dhclie
14 matches
Mail list logo