Re: netowork manager doesn't know it has connected

2006-09-18 Thread Dan Williams
On Sun, 2006-09-17 at 22:41 +0200, Anze Slosar wrote:
> Hi, 
> 
> I am using ubuntu dapper. On a fresh install I used network manager
> for a while, but since it didn't have a static IP, I went back to a
> home-cooked solution using whereami, ifplugd, etc. Now I wanted to go
> back to the network manager, and now it doesn't work any more... I
> just use a normal package, nothing fancy, no wpa, nothing just eth0
> and ath0. Asked for help on ubuntu forums and no luck. Specifically,
> my problem is as follows: 
> 
> Below is what happens when I plug in the cable (i.e. not a wireless
> problem and not a hardware problem, the same thing happens with
> ath0). 
> 
> At the point where I added " WORKING" to the log, the eth0 network
> is up and running, I can connect to various sites, etc. Looks like
> system configured succesfully via DHCP. However, network manager still
> thinks it is down, the dots keep rotating in the applet, and after a
> while it times out and then it sets eth0 to some stupid default IP at
> which point I (of course) loose connectivity. 
> Any ideas for debugging? I am really desperate...

Does your system actually use DHCP or static IP?  If DHCP, something is
not getting to NetworkManager.  Be sure you have the correct 'dbus-send'
magic at the top of the dhclient script (possibly
in /sbin/dhclient-script).  The fact that NM is attempting to do autoip
here means that DHCP is clearly not succeeding, and that NM is told that
the interface requires static IP configuration.

Dan

> 
> [EMAIL PROTECTED]:/home/anze# NetworkManager --no-daemon
> NetworkManager:  starting...
> NetworkManager:  main (): nm_data_new: Setting up dbus filter
> NetworkManager:  eth0: Device is fully-supported using
> driver 'e1000'.
> NetworkManager:  nm_device_init(): waiting for device's
> worker thread to start
> NetworkManager:  nm_device_init(): device's worker thread
> started, continuing.
> NetworkManager:  Now managing wired Ethernet (802.3)
> device 'eth0'.
> NetworkManager:  ath0: Device is fully-supported using
> driver 'ath_pci'.
> NetworkManager:  nm_device_init(): waiting for device's
> worker thread to start
> NetworkManager:  nm_device_init(): device's worker thread
> started, continuing.
> NetworkManager:  Now managing wireless (802.11) device
> 'ath0'.
> NetworkManager:  Updating allowed wireless network lists.
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  nm_dbus_get_networks_cb ():
> nm-dbus-nmi.c:522 (nm_dbus_get_networks_cb): error received:
> org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless
> networks stored..
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  Will activate wired connection 'eth0'
> because it now has a link.
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  SWITCH: no current connection, found
> better connection 'eth0'.
> NetworkManager:  Will activate connection 'eth0'.
> NetworkManager:  Device eth0 activation scheduled...
> NetworkManager:  Activation (eth0) started...
> NetworkManager:  Activation (eth0) Stage 1 of 5 (Device
> Prepare) scheduled...
> NetworkManager:  Activation (eth0) Stage 1 of 5 (Device
> Prepare) started...
> NetworkManager:  match
> NetworkManager:  Activation (eth0) Stage 2 of 5 (Device
> Configure) scheduled...
> NetworkManager:  Activation (eth0) Stage 1 of 5 (Device
> Prepare) complete.
> NetworkManager:  Activation (eth0) Stage 2 of 5 (Device
> Configure) starting...
> NetworkManager:  Activation (eth0) Stage 2 of 5 (Device
> Configure) successful.
> NetworkManager:  Activation (eth0) Stage 3 of 5 (IP
> Configure Start) scheduled.
> NetworkManager:  Activation (eth0) Stage 2 of 5 (Device
> Configure) complete.
> NetworkManager:  Activation (eth0) Stage 3 of 5 (IP
> Configure Start) started...
> NetworkManager:  match
> NetworkManager:  match
> NetworkManager:  Activation (eth0) Beginning DHCP
> transaction.
> NetworkManager:  Activation (eth0) Stage 3 of 5 (IP
> Configure Start) complete.
> NetworkManager:  DHCP daemon state is now 12
> (successfully started) for interface eth0
> NetworkManager:  Old device 'eth0' activating, won't
> change.
> NetworkManager:  match
> NetworkManager:  Old device 'eth0' activating, won't
> change.
> 
> **WORKING
> 
> NetworkManager:  Device 'eth0' DHCP transaction took too
> long (>45s), stopping it.
> NetworkManager:  Activation (eth0) Stage 4 of 5 (IP
> Configure Timeout) scheduled...
> NetworkManager:  DHCP daemon state is now 14 (normal
> exit) for interface eth0
> NetworkManager:  DHCP daemon state is now 14 (normal
> exit) for interface eth0
> NetworkManager:  Activation (eth0) Stage 4 of 5 (IP
> Configure Timeout) started...
> NetworkManager:  No DHCP reply received. Automatically
> obtaining IP via Zeroconf.
> NetworkManager:  autoip: Sending probe #0 for IP address
> 169.254.223.103.
> NetworkManager:  autoip: Wait

Re: How can I make the nm_debug available

2006-09-18 Thread Dan Williams
On Sat, 2006-09-16 at 22:17 +0800, Dawei Pang wrote:
> Hello,
>I want to learn the nm how to work.Now, I can only get the nm_info
> printed infromation, but I can not print the nm_debug which existed in
> the program, although I change the  nm_debug to  nm_info.
>I want to get  the  result of nm_debug ,please help me , thank
> you. 

It should be controlled with syslog logging settings.  nm_debug logs
stuff to syslog with debug priority, which I believe (?) is lower
priority than info.  Tune syslog and I think they will show up.

Dan

> ___
> 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: vpnc Plugin Help

2006-09-18 Thread Dan Williams
On Fri, 2006-09-15 at 20:36 -0400, Adam Pavelec wrote:
> I wrote:
> > It works perfectly with another configuration I connect to that requires 
> > a username/password.  It just took me a few moments to figure out that I 
> > had to decode the GroupPwd from the .pcf file.  At any rate, the 
> > connection I'm still trying to get to work /doesn't/ require a 
> > username/password -- any hints?
> >   
> 
> Hrm -- it looks like I need to use the --enable-1des option to connect 
> in this manner.  Is it possible to do this with the vpnc plugin?

If you patch it, yes.  But the question is why you'd want to do that
since it apparently weakens security.  Ideally you could talk to your
network admins and figure out why they require single DES in 2006...
However, if all else fails, then yes it would need to be a config option
and likely edited in with gconf-editor.  I'd rather not give it UI since
this is the first I've heard of anyone needing to use it.

Dan

> -Adam
> ___
> 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