Trouble waking from sleep

[Neal Becker]

NetworkManager-0.7.0.99-5.git20090326.fc10.x86_64

After being connected to wired enet, going to sleep, and waking without 
wired enet, results are random.  Sometimes wlan is connected seemlessly, 
other times not.

In those cases restarting NetworkManager does not fix anything.

Logging out/in always fixes it.


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

nm-tool doesn't show my mobile broadband card

[Jochen Wiedmann]

Hi,

I have a so-called web'n'walk stick. I managed to have it reported not as a
USB drive, but as a modem by using usb_modeswitch:

[...@mcjwi ~]$ hal-find-by-capability --capability=modem
   
/org/freedesktop/Hal/devices/usb_device_af0_6971_Serial_Number_if0_serial_unknown_0
   
/org/freedesktop/Hal/devices/usb_device_af0_6971_Serial_Number_if0_serial_unknown_1

I also have created an entry under "Mobile Broadband" using
nm-connection-editor. However, I can't get the stick to do any dial
attempts. A possible reason might be, that nm-tool shows the Ethernet and
Wireless devices, but not my modem.

Any ideas, what might be wrong?

Thanks,

Jochen

Additional information:

[...@mcjwi ~]$ lsusb
...
Bus 003 Device 003: ID 0af0:6971 Option 
...

Matching entry from 10-modem.fdi:

 
  


  
GSM-07.07
GSM-07.05
  



-- 
View this message in context: 
http://www.nabble.com/nm-tool-doesn%27t-show-my-mobile-broadband-card-tp23448718p23448718.html
Sent from the Gnome - NetworkManager mailing list archive at Nabble.com.

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

nm-applet loosing state

[Geoffrey Leach]

nm-applet is how the problem manifests itself; I'm presuming that the 
problem is really in NetworkManager.

All of this is in runlevel 5. Release on Fedora 10 is 
NetworkManager-0.7.0.99-5.git20090326.fc10.i386

The system in question does networking _only_ via a USB-connected 
wireless adapter. The driver for the device has a problem resuming, so 
it must be unplugged before hibernating the box. All of this is with 
the router up and running.

The sequence of events is as follows:

o Unplug wireless adapter
o Disable networking (via nm-applet)
o Hibernate
o Power off
o Power on => resume
o Plug in wireless adapter once resume is completed

At this point nm-applet shows no networking (white X in red box).

Here's the problem. Sometimes nm-applet has the Enable networking, 
sometimes not. Sometimes just passing the mouse over the icon will 
start the search process, sometimes not. Sometimes clicking enable 
networking will result in success (connection to the router), sometimes 
not. Sometimes it will prompt for the key and that will result in a 
connection.

Unplug - plug in of the wireless adapter usually works. 

Thanks for reading this far! So, is there a recipe for getting the 
connection every time, without all this fooling around?


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Diskless clients and NetworkManager

[Marc Herbert]

Dan Williams a écrit :

> if NM is not managing your default internet connection, then you
> should probably turn NM off when setting up the machine.

This "take it or leave it" philosophy is quite disappointing.


> But the core problem is that network management is a *system-wide*
> problem, and you can't just write one component and call it a day.  The
> policy needs to make informed choices based on the entire network state
> of the machine.  And the configuration of all the network connections
> needs to be in *one* place, with *one* format, not spread around in 3
> different locations because you're trying to put 2 or 3 connection
> managers on the same machine.  There should only be one connection
> manager running at any given time, or else you've just (a) doubled your
> work and QA, and (b) made it suck for users because configuration is
> split up, and (c) behavior is different than they expect.

In an ideal world this is definitely what you want, but the reality
unfortunately often departs from this. No matter your (impressive)
efforts, NM will by nature always be catching up with the latest
technologies or new fancy ways people configure their network.
And we do not even know if there will be enough will and development
manpower to make NM compatible with every latest connectivity
invention.

So I think assuming NM will always know about everything in the system
is not realistic. There will always be exceptions. If your answer to
this is "not supported, not interested, bye", then it is quite
disappointing (but the mere existence of "NM_CONTROLLED=no" suggests
otherwise). An alternative answer is: "graceful degradation". That is:
if you really think you know everything, then fine be the Oracle. But
otherwise be more modest and reduce the number of features _without_
getting rid of all of them!


About this more specific "online/offline" issue, you must consider
that there was a time before NetworkManager even existed, and that
there are systems where NM will probably never run on. Because of this
legacy, every single network application and every single end user is
assuming "online" status by default and prepared to catch possible
network errors. In other words, everyone is prepared to deal with
wrong online status. On the other hand, no one is prepared to handle
wrong offline status (how could that be?).

When NM sees "NM_CONTROLLED=no", reporting "offline" or "online" are
admittedly both lies (the accurate answer is "unknown").  But there is
a huge difference. Reporting "online" is a lie that everyone is used
to live with since ages, whereas reporting "offline" is a lie that
breaks everything. Pick one.

Making the simple easy AND the complex possible sometimes costs more,
but in this simple, specific case I really doubt it.

NM is great for many OTHER features than just (abusively) reporting
offline status, and I fail to see why users should give up on all
these other great features just because they sometimes want to connect
using a connection not controlled by NetworkManager.


> Why do we have more than one program that controls 3G connections?

Because it is Linux, not Windows. It is a free country, take it or
leave it?


> There's a lot more to the problem than online/offline.

Well, you can design beautiful and advanced software architecture(s)
with multiple modules exchanging very fine-grained connection
information, I still think this will never change anything to the
simple online/offline problem described above.



Cheers,

Marc


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Moving ppp-manager into ModemManager

[Pablo Martí Gamboa]

2009/5/8 Marcel Holtmann 

> Hi Pablo,


Hi Marcel,


>
>
> > what do you guys think about moving the ppp-manager part from
> > NetworkManager into ModemManager?
> >
> > What is the actual reason why ModemManager doesn't handle the
> > PPP part
> > of a data connection?
> >
> > Because NetworkManager also happens to support pppoe and friends
>
> and with the same argument the support for DSL modems etc. could also be
> moved into ModemManager.
>
> My problem is that if ModemManager as a standalone can not deal with the
> PPP portion of a dialup connection, then it is nothing more than an AT
> command parser with D-Bus interface. I am failing to see the point why
> this code was ever moved outside NetworkManager to begin with then.


Well, ModemManager can be think of as a NetworkManager plugin, without
ModemManager NetworkManager is still functional for all the
ethernet/wifi/vpn operations. I guess that the goal is to keep a lean
NetworkManager core; all this modems require special at commands (most of
them proprietary) to configure and talk to them. NetworkManager is not
interested in all those details, it just wants to configure a device with
some given settings and connect to Internet.

By having it as a separate piece of code, other applications can depend on
ModemManager and talk to 3g devices without having to install NetworkManager
and its dependencies. Also, there are some alternative ModemManager
implementations, like Wader, and bundling ModemManager with NetworkManager
would defeat one of ModemManager's original purposes: Having a spec'ed API
allows for different implementations that can be seamlessly swapped.

Best regards,
Pablo


-- 
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

About log message "-- Error received: Numerical result out of range"

[cee1]

Hi all,

Wandering log of NM (NM-0.7.1, run with "--no-daemon"), I see some log
messages:

NetworkManager:   Activation (wlan0) successful, device activated.
NetworkManager:   Activation (wlan0) Stage 5 of 5 (IP Configure
Commit) complete.
NetworkManager:   (wlan0): device state change: 8 -> 3
NetworkManager:   (wlan0): deactivating device (reason: 38).
NetworkManager:   wlan0: canceled DHCP transaction, dhcp client pid
1642
-- Error received: Numerical result out of range
-- Original message: type=0x19 length=56 flags=
sequence-nr=1241771452 pid=4195938
NetworkManager:   check_one_route(): (wlan0) error -34 returned from
rtnl_route_del(): Sucess

What happend to "-- Error received: Numerical result out of range"? Invaild
dbus package? Just curious, thanks
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Moving ppp-manager into ModemManager

[Marcel Holtmann]

Hi Pablo,

> what do you guys think about moving the ppp-manager part from
> NetworkManager into ModemManager?
> 
> What is the actual reason why ModemManager doesn't handle the
> PPP part
> of a data connection?
> 
> Because NetworkManager also happens to support pppoe and friends

and with the same argument the support for DSL modems etc. could also be
moved into ModemManager.

My problem is that if ModemManager as a standalone can not deal with the
PPP portion of a dialup connection, then it is nothing more than an AT
command parser with D-Bus interface. I am failing to see the point why
this code was ever moved outside NetworkManager to begin with then.

Regards

Marcel


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Problem of associated pre-suspend AP showing up in NM's AP list after resume has returned in 2.6.30-rc4

[Peter Roediger]

I don't really know, how can I check this? When looking at /var/log/syslog I
get the following output right before suspending to ram:

May  8 07:47:55 debian kernel: [63778.728835] CPU0 attaching NULL
sched-domain.
May  8 07:47:55 debian kernel: [63778.728838] CPU1 attaching NULL
sched-domain.
May  8 07:47:55 debian kernel: [63778.733189] CPU0 attaching sched-domain:
May  8 07:47:55 debian kernel: [63778.733192]  domain 0: span 0-1 level MC
May  8 07:47:55 debian kernel: [63778.733194]   groups: 0 1
May  8 07:47:55 debian kernel: [63778.733197] CPU1 attaching sched-domain:
May  8 07:47:55 debian kernel: [63778.733199]  domain 0: span 0-1 level MC
May  8 07:47:55 debian kernel: [63778.733200]   groups: 1 0
May  8 07:47:55 debian kernel: [63778.751046] usb 4-2: USB disconnect,
address 20
May  8 07:47:55 debian NetworkManager:   Sleeping...
May  8 07:47:55 debian NetworkManager:   (eth0): now unmanaged
May  8 07:47:55 debian NetworkManager:   (eth0): device state change:
2 -> 1
May  8 07:47:55 debian NetworkManager:   (eth0): cleaning up...
May  8 07:47:55 debian NetworkManager:   (eth0): taking down device.
May  8 07:47:55 debian NetworkManager:   (wlan0): now unmanaged
May  8 07:47:55 debian NetworkManager:   (wlan0): device state change:
8 -> 1
May  8 07:47:55 debian NetworkManager:   (wlan0): deactivating device
(reason: 37).
May  8 07:47:55 debian kernel: [63778.819285] PM: Syncing filesystems ...
done.




and the NetworkManager related stuff after:

May  8 09:20:09 debian NetworkManager:   check_one_route(): (wlan0)
error -34 returned from rtnl_route_del(): Sucess#012
May  8 09:20:09 debian NetworkManager:   (wlan0): cleaning up...
May  8 09:20:09 debian NetworkManager:   (wlan0): taking down device.
.
.
.
May  8 09:20:10 debian NetworkManager:   Waking up...
May  8 09:20:10 debian NetworkManager:   (eth0): now managed
May  8 09:20:10 debian NetworkManager:   (eth0): device state change:
1 -> 2
May  8 09:20:10 debian NetworkManager:   (eth0): bringing up device.
.
.
.
May  8 09:20:10 debian NetworkManager:   (eth0): preparing device.
May  8 09:20:10 debian NetworkManager:   (eth0): deactivating device
(reason: 2).
May  8 09:20:10 debian NetworkManager:   (wlan0): now managed
May  8 09:20:10 debian NetworkManager:   (wlan0): device state change:
1 -> 2
May  8 09:20:10 debian NetworkManager:   (wlan0): bringing up device.
.
.
.
May  8 09:20:10 debian NetworkManager:   (wlan0): preparing device.
May  8 09:20:10 debian NetworkManager:   (wlan0): deactivating device
(reason: 2).
May  8 09:20:10 debian kernel: [63785.077638] wlan0: direct probe to AP
00:1d:68:6b:b4:99 try 1
May  8 09:20:10 debian NetworkManager:   (wlan0): device state change:
2 -> 3
May  8 09:20:10 debian NetworkManager:   (wlan0): supplicant interface
state:  starting -> ready
May  8 09:20:10 debian wpa_supplicant[14746]: CTRL-EVENT-SCAN-RESULTS
May  8 09:20:10 debian NetworkManager:   Activation (wlan0) starting
connection 'WLAN-Caste'
May  8 09:20:10 debian NetworkManager:   (wlan0): device state change:
3 -> 4
May  8 09:20:10 debian NetworkManager:   Activation (wlan0) Stage 1 of
5 (Device Prepare) scheduled...
May  8 09:20:10 debian NetworkManager:   Activation (wlan0) Stage 1 of
5 (Device Prepare) started...
May  8 09:20:10 debian NetworkManager:   Activation (wlan0) Stage 2 of
5 (Device Configure) scheduled...
May  8 09:20:10 debian NetworkManager:   Activation (wlan0) Stage 1 of
5 (Device Prepare) complete.
May  8 09:20:10 debian NetworkManager:   Activation (wlan0) Stage 2 of
5 (Device Configure) starting...
May  8 09:20:10 debian NetworkManager:   (wlan0): device state change:
4 -> 5
May  8 09:20:10 debian NetworkManager:   Activation (wlan0/wireless):
connection 'WLAN-Caste' has security, and secrets exist. No new secrets
needed.
May  8 09:20:10 debian NetworkManager:   Config: added 'ssid' value
'WLAN-Caste'
May  8 09:20:10 debian NetworkManager:   Config: added 'scan_ssid'
value '1'
May  8 09:20:10 debian NetworkManager:   Config: added 'key_mgmt'
value 'WPA-PSK'
May  8 09:20:10 debian NetworkManager:   Config: added 'auth_alg'
value 'OPEN'
May  8 09:20:10 debian NetworkManager:   Config: added 'psk' value
''
May  8 09:20:10 debian NetworkManager:   Activation (wlan0) Stage 2 of
5 (Device Configure) complete.
May  8 09:20:10 debian NetworkManager:   Config: set interface ap_scan
to 1
May  8 09:20:10 debian NetworkManager:   (wlan0): supplicant
connection state:  scanning -> disconnected
May  8 09:20:10 debian wpa_supplicant[14746]: Failed to initiate AP scan.
May  8 09:20:10 debian NetworkManager:   (wlan0): supplicant
connection state:  disconnected -> scanning

This is the output when resuming at work. Note that "WLAN-Caste" is my home
AP and should not be in the list anymore or even attempted to be associated
to.

Any suggestions?

Peter

On Thu, May 7, 2009 at 17:08, Dan Williams  wrote:

> On Wed, 2009-05-06 at 09:18 +0200, Peter Roediger wrote:
> > I'm using a self-compiled kernel version 2.6.30-rc4 on an intel 5300
> > w

Re: Moving ppp-manager into ModemManager

[Pablo Martí Gamboa]

2009/5/8 Marcel Holtmann 

> Hi guys,
>
> what do you guys think about moving the ppp-manager part from
> NetworkManager into ModemManager?
>
> What is the actual reason why ModemManager doesn't handle the PPP part
> of a data connection?


Because NetworkManager also happens to support pppoe and friends


>
> Regards
>
> Marcel
>
>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>



-- 
Pablo Martí
http://www.linkedin.com/in/pmarti || http://www.warp.es
python -c "print '706d6172746940776172702e6573'.decode('hex')"
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list