Re: [gentoo-user] nm-applet / vpnc / pptp / openvpn

2009-11-19 Thread SpaceCake
2009/11/18 Albert Hopkins mar...@letterboxes.org



  I've succesfullly installed Networkmanager and nm-applet with all the
  plugins under Gnome / Kde-4-3 using the instructions can be found at
  gentoo-wiki. It is working perfectly for wired and wireless LAN but
  not for any VPN (this part of the applet is grey
 
  I was searching the archive and googled this thing but I cannot find a
  solution, so I decided to ask you :)
 
  I suppose this is some problem with the dbus registration of the
  plugins, but I'm not sure

 Why do you suppose that?  Have you looked at the logs.  In my experience
 the NetworkManager daemon spits out plenty of info by default in syslog.
 Have a look at those.  Paste those so we're not wandering around in the
 dark.

 -a




 Here is my log after starting Networkmanager. It is not talking about any
vpnc or openvpn stuff...do you have any idea?


/etc/init.d/NetworkManager start
 * Starting NetworkManager ...
Nov 19 12:18:48 brutal NetworkManager: info
starting...
[ ok ]
brutal ~ # Nov 19 12:18:49 brutal NetworkManager: nm_device_ethernet_new:
assertion `driver != NULL'
failed

Nov 19 12:18:49 brutal NetworkManager: nm_device_ethernet_new: assertion
`driver != NULL'
failed

Nov 19 12:18:49 brutal NetworkManager: info  (eth0): new Ethernet device
(driver:
'tg3')

Nov 19 12:18:49 brutal NetworkManager: info  (eth0): exported as
/org/freedesktop/Hal/devices/net_00_26_55_c9_e5_22

Nov 19 12:18:49 brutal NetworkManager: info  (wlan0): driver supports SSID
scans (scan_capa
0x01).

Nov 19 12:18:49 brutal NetworkManager: info  (wlan0): new 802.11 WiFi
device (driver:
'iwlagn')

Nov 19 12:18:49 brutal NetworkManager: info  (wlan0): exported as
/org/freedesktop/Hal/devices/net_00_1e_65_72_ab_2e

Nov 19 12:18:49 brutal NetworkManager: info  (ttyS0): ignoring due to lack
of mobile broadband
capabilties

Nov 19 12:18:53 brutal kernel: tg3 :85:00.0: wake-up capability disabled
by
ACPI

Nov 19 12:18:53 brutal kernel: tg3 :85:00.0: PME#
disabled

Nov 19 12:18:53 brutal NetworkManager: info  (eth0): device state change:
1 -
2

Nov 19 12:18:53 brutal NetworkManager: info  (eth0): bringing up
device.

Nov 19 12:18:53 brutal kernel: tg3 :85:00.0: irq 32 for
MSI/MSI-X

Nov 19 12:18:53 brutal kernel: ADDRCONF(NETDEV_UP): eth0: link is not
ready

Nov 19 12:18:53 brutal NetworkManager: info  (eth0): preparing
device.

Nov 19 12:18:53 brutal NetworkManager: info  (eth0): deactivating device
(reason:
2).

Nov 19 12:18:53 brutal vmnetBridge: RTM_NEWLINK: name:eth0 index:3
flags:0x1003

Nov 19 12:18:53 brutal vmnetBridge: Can't remove interface eth0 3 (does not
exist).

Nov 19 12:18:53 brutal NetworkManager: info  (wlan0): device state change:
1 -
2

Nov 19 12:18:53 brutal NetworkManager: info  (wlan0): bringing up
device.

Nov 19 12:18:53 brutal vmnetBridge: RTM_NEWLINK: name:wlan0 index:5
flags:0x1003

Nov 19 12:18:53 brutal vmnetBridge: Can't remove interface wlan0 5 (does not
exist).

Nov 19 12:18:53 brutal kernel: ADDRCONF(NETDEV_UP): wlan0: link is not
ready

Nov 19 12:18:53 brutal NetworkManager: info  (wlan0): preparing
device.

Nov 19 12:18:53 brutal NetworkManager: info  (wlan0): deactivating device
(reason:
2).

Nov 19 12:18:53 brutal NetworkManager: info  (wlan0): device state change:
2 -
3

Nov 19 12:18:53 brutal vmnetBridge: RTM_NEWLINK: name:wlan0 index:5
flags:0x1003

Nov 19 12:18:53 brutal vmnetBridge: Can't remove interface wlan0 5 (does not
exist).

Nov 19 12:18:53 brutal NetworkManager: info  (wlan0): supplicant interface
state:  starting -
ready

Nov 19 12:18:54 brutal kernel: tg3: eth0: Link is up at 100 Mbps, full
duplex.

Nov 19 12:18:54 brutal kernel: tg3: eth0: Flow control is on for TX and on
for
RX.

Nov 19 12:18:54 brutal kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes
ready

Nov 19 12:18:54 brutal NetworkManager: info  (eth0): carrier now ON
(device state
2)

Nov 19 12:18:54 brutal NetworkManager: info  (eth0): device state change:
2 - 3
Nov 19 12:18:54 brutal NetworkManager: info  Activation (eth0) starting
connection 'Auto eth0'
Nov 19 12:18:54 brutal NetworkManager: info  (eth0): device state change:
3 - 4
Nov 19 12:18:54 brutal NetworkManager: info  Activation (eth0) Stage 1 of
5 (Device Prepare) scheduled...
Nov 19 12:18:54 brutal NetworkManager: info  Activation (eth0) Stage 1 of
5 (Device Prepare) started...
Nov 19 12:18:54 brutal NetworkManager: info  Activation (eth0) Stage 2 of
5 (Device Configure) scheduled...
Nov 19 12:18:54 brutal NetworkManager: info  Activation (eth0) Stage 1 of
5 (Device Prepare) complete.
Nov 19 12:18:54 brutal NetworkManager: info  Activation (eth0) Stage 2 of
5 (Device Configure) starting...
Nov 19 12:18:54 brutal NetworkManager: info  (eth0): device state change:
4 - 5
Nov 19 12:18:54 brutal vmnetBridge: RTM_NEWLINK: name:eth0 index:3
flags:0x00011043
Nov 19 12:18:54 brutal NetworkManager: info  Activation (eth0) Stage 2 of
5 (Device Configure) successful.
Nov 19 12:18:54 brutal NetworkManager: info  Activation 

Re: [gentoo-user] nm-applet / vpnc / pptp / openvpn

2009-11-19 Thread Albert Hopkins
On Thu, 2009-11-19 at 12:28 +0100, SpaceCake wrote:
  Here is my log after starting Networkmanager. It is not talking
 about any
 vpnc or openvpn stuff...do you have any idea? 

It doesn't talk about openvpn stuff until/unless you actually attempt to
open an openvpn connection.




Re: [gentoo-user] nm-applet / vpnc / pptp / openvpn

2009-11-19 Thread SpaceCake
yes, but as I told earlier in nm-applet this section is grey, so I cannot
add vpn configs. when I start vpnc with the correct config from root's
shell, it is working perfectly and connect me to the vpn gw I use, so this
is why I said the problem maybe in the deep somewhere around dbus
communication, but I'm not sure

Laszlo


2009/11/19 Albert Hopkins mar...@letterboxes.org

 On Thu, 2009-11-19 at 12:28 +0100, SpaceCake wrote:
   Here is my log after starting Networkmanager. It is not talking
  about any
  vpnc or openvpn stuff...do you have any idea?

 It doesn't talk about openvpn stuff until/unless you actually attempt to
 open an openvpn connection.





Re: [gentoo-user] nm-applet / vpnc / pptp / openvpn

2009-11-19 Thread Albert Hopkins
On Thu, 2009-11-19 at 15:55 +0100, SpaceCake wrote:
 yes, but as I told earlier in nm-applet this section is grey, so I
 cannot
 add vpn configs. when I start vpnc with the correct config from root's
 shell, it is working perfectly and connect me to the vpn gw I use, so
 this
 is why I said the problem maybe in the deep somewhere around dbus
 communication, but I'm not sure 

I don't know why these options would be greyed out.  Unless.. do you
actually have the plugins installed?

$ equery l networkmanager*
 * Searching for networkmanager* ...
[IP-] [ ~] net-misc/networkmanager-0.7.1_p20090824 (0)
[IP-] [ ~] net-misc/networkmanager-openvpn-0.7.1-r1 (0)
[IP-] [ ~] net-misc/networkmanager-vpnc-0.7.1 (0)

Does it even show up in nm-connection-editor?

AFAIK the UI just uses these plugins to create a vpn configuration. This
is long before actually talking to the nm daemon.  So the UI just
creates a config and stores it (in GNOME the non-system configs are
stored in gconf at /system/networking/connections.  Then when you want
to connect, the UI grabs whatever config and passes it to the nm daemon
(via dbus?).  Your issue seems to be with the first part of this process
(the UI), not the second.

-a








[gentoo-user] nm-applet / vpnc / pptp / openvpn

2009-11-18 Thread SpaceCake
Hi,

I've succesfullly installed Networkmanager and nm-applet with all the
plugins under Gnome / Kde-4-3 using the instructions can be found at
gentoo-wiki. It is working perfectly for wired and wireless LAN but not for
any VPN (this part of the applet is grey

I was searching the archive and googled this thing but I cannot find a
solution, so I decided to ask you :)

I suppose this is some problem with the dbus registration of the plugins,
but I'm not sure

This is my versions

[I] sys-apps/dbus
 Available versions:  1.2.3-r1 ~1.2.12 ~1.3.0 ~1.3.0-r1 {X debug doc
selinux test}
 Installed versions:  1.2.3-r1(16.09.48 2009-11-17)(X -debug -doc
-selinux)

[I] net-misc/networkmanager
 Available versions:  *0.6.5_p20070823 0.6.6 ~0.7.1-r3 0.7.1-r6
~0.7.1_p20090824 [M]**0.8.0_pre20090824 [M]**0.8.0_pre20091105 {avahi
bluetooth connection-sharing crypt debug dhclient dhcpcd doc gnome gnutls
nss resolvconf}
 Installed versions:  0.7.1-r6(18.16.04 2009-10-19)(gnutls resolvconf
-avahi -connection-sharing -dhclient -dhcpcd -doc -nss)
 Homepage:http://www.gnome.org/projects/NetworkManager/
 Description: Network configuration and management in an easy
way. Desktop environment independent.

[D] net-misc/networkmanager-openvpn
 Available versions:  ~0.3.2_p20070621 ~0.7.1-r1 {crypt debug doc gnome}
 Installed versions:  0.7.1-r1(16.02.50 2009-11-17)(-gnome)
 Homepage:http://www.gnome.org/projects/NetworkManager/
 Description: NetworkManager OpenVPN plugin.

[D] net-misc/networkmanager-pptp
 Available versions:  ~0.1.0_p20070726 ~0.7.0 ~0.7.1 {crypt debug doc
gnome}
 Installed versions:  0.7.1(16.03.03 2009-11-17)(-gnome)
 Homepage:http://www.gnome.org/projects/NetworkManager/
 Description: NetworkManager PPTP plugin.

[D] net-misc/networkmanager-vpnc
 Available versions:  ~0.6.4_p20070621 ~0.7.0 ~0.7.1 {crypt debug doc
gnome}
 Installed versions:  0.7.1(16.03.15 2009-11-17)(-gnome)
 Homepage:http://www.gnome.org/projects/NetworkManager/
 Description: NetworkManager VPNC plugin.

Do you have any idea?

Thank you
L:


Re: [gentoo-user] nm-applet / vpnc / pptp / openvpn

2009-11-18 Thread Albert Hopkins


 I've succesfullly installed Networkmanager and nm-applet with all the
 plugins under Gnome / Kde-4-3 using the instructions can be found at
 gentoo-wiki. It is working perfectly for wired and wireless LAN but
 not for any VPN (this part of the applet is grey
 
 I was searching the archive and googled this thing but I cannot find a
 solution, so I decided to ask you :)
 
 I suppose this is some problem with the dbus registration of the
 plugins, but I'm not sure

Why do you suppose that?  Have you looked at the logs.  In my experience
the NetworkManager daemon spits out plenty of info by default in syslog.
Have a look at those.  Paste those so we're not wandering around in the
dark.

-a