Re: Disable prompting when connection attempt fails?
On Dec 24, 2007 6:00 PM, Dan Williams <[EMAIL PROTECTED]> wrote: > I'm starting to > think that the security dialog should only really come up during the > connection process if the connection failed, not if the AP terminated > you or the card just randomly decided you were connected and now you > aren't. That would be the ideal behavior, but if that's difficult to implement then simply retrying every few minutes and presenting the security dialog only when asked (for example only when "Connect to Other Wireless Network" is selected) would be much better than what happens at present. Sometimes a network is temporarily flaky and it's necessary to retry five or ten times. Right now each time requires clicking and waiting. That's frustrating. Jeff ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Roaming to (none) ((none))
On Wed, 2007-12-19 at 05:15 +0100, Michael Biebl wrote: > Dan Williams schrieb: > > On Tue, 2007-12-18 at 21:28 +0100, Michael Biebl wrote: > >> Michael Biebl schrieb: > >>> Michael Biebl schrieb: > >>> > So, NM is obviously getting the wrong freq from the card. > >>> Narrowed the problem further: > >>> iw_get_ext() in nm_device_802_11_wireless_get_frequency() sets > >>> wrq.u.freq to 0. > >> Actually, it's 1.0 > > > > Hmm; it could be that NM needs to do channel -> freq conversion here. > > It's a bit undefined whether drivers pass back the channel or the > > frequency. So I guess NM needs to handle both. There's defined > > semantics in the iw_float part to flag whether the returned value is a > > channel or a frequency. > > You were completey right. I switched the ap to channel 6, > now freq is 6.0. So indeed, it seems to return the channel, not the > frequency directly. Can you try SVN r3189 and let me know if that works for you? Thanks, Dan > > > > Another possibility is that the driver has some issue with getting the > > frequency off the card periodically. > > Doesn't seem to be the case. > > Cheers, > Michael > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: USB WLAN device does not show up
On Tue, 2007-12-25 at 00:48 +0100, Philipp Hagemeister wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> [Resend because I forgot to confirm subscription]
>
> Hi there,
>
> when I attach my USB WLAN stick (Netgear WG111v2), I can see it with the
> commands iwconfig/ifconfig, but not in NetworkManager.
I believe this is an rtl8187 device. What's the output of
'/sbin/iwconfig' ? Does the device show up there?
Also make sure you've removed that interface
from /etc/network/interfaces because having it there makes it invisible
to NetworkManager on Ubuntu platforms.
Dan
> I am using NetworkManager 0.6.5 as bundled in Ubuntu.
>
> I attached a few debugging information files:
>
> * nm-tool: Output of nm-tool, just to illustrate wlan0 is missing.
> * NetworkManager: partial output of sudo NetworkManager --no-daemon when
> connecting and disconnecting the stick
> * hal-device-diff: A diff of hal-device with stick attached and off
>
> The strange thing is, I could have sworn it worked perfectly before I
> rebooted the machine and reconnected the USB WLAN stick. Furthermore, in
> the manual settings configuration of knetworkmanager, the stick *does*
> show up (Does anyone know why?). I attached a log of its debugging
> information (knetworkmanager).
>
> Any ideas? How can I completely reset every setting of NetworkManager?
> (I tried apt-get purge network-manager) Did I miss a more useful
> debugging tool?
>
> Thanks in advance,
>
> Philipp Hagemeister
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.7 (GNU/Linux)
>
> iD8DBQFHcEVj9eq1gvr7CFwRCkG4AJ43Pk3WaANBj5RPgtdEGjJXLGYdngCgrYxJ
> +C/duvHDTn5TTV81SKrqnLw=
> =JdzT
> -END PGP SIGNATURE-
> plain text document attachment (nm-tool)
> NetworkManager Tool
>
> State: connected
>
> - Device: eth0
>
> NM Path: /org/freedesktop/NetworkManager/Devices/eth0
> Type: Wired
> Driver:forcedeth
> Active:yes
> HW Address:00:1D:92:00:A5:C2
>
> Capabilities:
> Supported: yes
> Carrier Detect: yes
> Speed: 100 Mb/s
>
> Wired Settings
> Hardware Link: yes
>
> IP Settings:
> IP Address: 192.168.0.151
> Subnet Mask: 255.255.255.0
> Broadcast: 192.168.0.255
> Gateway: 192.168.0.100
> Primary DNS: 192.168.0.100
> Secondary DNS: 0.0.0.0
>
>
>
> plain text document attachment (NetworkManager)
> NetworkManager: [1198537840.267460] nm_hal_device_added(): New device
> added (hal udi is
> '/org/freedesktop/Hal/devices/usb_device_846_4240_3887_').
> NetworkManager: [1198537840.366612] nm_hal_device_added(): New device
> added (hal udi is
> '/org/freedesktop/Hal/devices/usb_device___noserial').
> NetworkManager: [1198537840.740842] nm_hal_device_added(): New device
> added (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c').
> NetworkManager: [1198537840.745545] nm_hal_device_added(): New device
> added (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c_0').
>
> (NetworkManager:8978): GLib-GObject-CRITICAL **: g_signal_handler_disconnect:
> assertion `handler_id > 0' failed
> NetworkManager: [1198537840.776236] nm_hal_device_added(): New device
> added (hal udi is
> '/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw').
>
>
> (Removing the adapter)
>
> NetworkManager: [1198537858.894226] nm_hal_device_removed(): Device
> removed (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c_0').
> NetworkManager: [1198537858.922817] nm_hal_device_removed(): Device
> removed (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c').
> NetworkManager: [1198537858.945460] nm_hal_device_removed(): Device
> removed (hal udi is
> '/org/freedesktop/Hal/devices/usb_device___noserial').
> NetworkManager: [1198537858.948899] nm_hal_device_removed(): Device
> removed (hal udi is
> '/org/freedesktop/Hal/devices/usb_device_846_4240_3887_').
> NetworkManager: [1198537858.953607] nm_hal_device_removed(): Device
> removed (hal udi is
> '/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw').
>
> plain text document attachment (hal-device-diff)
> --- hal-device-before 2007-12-25 00:11:52.624269962 +0100
> +++ hal-device-after2007-12-25 00:12:04.618953841 +0100
> @@ -1,4 +1,119 @@
> -0: udi = '/org/freedesktop/Hal/devices/acpi_P001'
> +0: udi = '/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw'
> + linux.device_file = '/dev/bus/usb/002/021' (string)
> + usbraw.device = '/dev/bus/usb/002/021' (string)
> + info.capabilities = { 'usbraw' } (string list)
> + info.udi =
> '/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw' (string)
> + linux.subsystem = 'usb_device' (string)
> + info.product = 'USB Raw Device Access' (string)
> + linux.hotplug_type = 2 (0x2) (int
USB WLAN device does not show up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[Resend because I forgot to confirm subscription]
Hi there,
when I attach my USB WLAN stick (Netgear WG111v2), I can see it with the
commands iwconfig/ifconfig, but not in NetworkManager.
I am using NetworkManager 0.6.5 as bundled in Ubuntu.
I attached a few debugging information files:
* nm-tool: Output of nm-tool, just to illustrate wlan0 is missing.
* NetworkManager: partial output of sudo NetworkManager --no-daemon when
connecting and disconnecting the stick
* hal-device-diff: A diff of hal-device with stick attached and off
The strange thing is, I could have sworn it worked perfectly before I
rebooted the machine and reconnected the USB WLAN stick. Furthermore, in
the manual settings configuration of knetworkmanager, the stick *does*
show up (Does anyone know why?). I attached a log of its debugging
information (knetworkmanager).
Any ideas? How can I completely reset every setting of NetworkManager?
(I tried apt-get purge network-manager) Did I miss a more useful
debugging tool?
Thanks in advance,
Philipp Hagemeister
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHcEVj9eq1gvr7CFwRCkG4AJ43Pk3WaANBj5RPgtdEGjJXLGYdngCgrYxJ
+C/duvHDTn5TTV81SKrqnLw=
=JdzT
-END PGP SIGNATURE-
NetworkManager Tool
State: connected
- Device: eth0
NM Path: /org/freedesktop/NetworkManager/Devices/eth0
Type: Wired
Driver:forcedeth
Active:yes
HW Address:00:1D:92:00:A5:C2
Capabilities:
Supported: yes
Carrier Detect: yes
Speed: 100 Mb/s
Wired Settings
Hardware Link: yes
IP Settings:
IP Address: 192.168.0.151
Subnet Mask: 255.255.255.0
Broadcast: 192.168.0.255
Gateway: 192.168.0.100
Primary DNS: 192.168.0.100
Secondary DNS: 0.0.0.0
NetworkManager: [1198537840.267460] nm_hal_device_added(): New device
added (hal udi is '/org/freedesktop/Hal/devices/usb_device_846_4240_3887_').
NetworkManager: [1198537840.366612] nm_hal_device_added(): New device
added (hal udi is
'/org/freedesktop/Hal/devices/usb_device___noserial').
NetworkManager: [1198537840.740842] nm_hal_device_added(): New device
added (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c').
NetworkManager: [1198537840.745545] nm_hal_device_added(): New device
added (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c_0').
(NetworkManager:8978): GLib-GObject-CRITICAL **: g_signal_handler_disconnect:
assertion `handler_id > 0' failed
NetworkManager: [1198537840.776236] nm_hal_device_added(): New device
added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw').
(Removing the adapter)
NetworkManager: [1198537858.894226] nm_hal_device_removed(): Device
removed (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c_0').
NetworkManager: [1198537858.922817] nm_hal_device_removed(): Device
removed (hal udi is '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c').
NetworkManager: [1198537858.945460] nm_hal_device_removed(): Device
removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device___noserial').
NetworkManager: [1198537858.948899] nm_hal_device_removed(): Device
removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_846_4240_3887_').
NetworkManager: [1198537858.953607] nm_hal_device_removed(): Device
removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw').
--- hal-device-before 2007-12-25 00:11:52.624269962 +0100
+++ hal-device-after2007-12-25 00:12:04.618953841 +0100
@@ -1,4 +1,119 @@
-0: udi = '/org/freedesktop/Hal/devices/acpi_P001'
+0: udi = '/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw'
+ linux.device_file = '/dev/bus/usb/002/021' (string)
+ usbraw.device = '/dev/bus/usb/002/021' (string)
+ info.capabilities = { 'usbraw' } (string list)
+ info.udi =
'/org/freedesktop/Hal/devices/usb_device_846_4240_3887__usbraw' (string)
+ linux.subsystem = 'usb_device' (string)
+ info.product = 'USB Raw Device Access' (string)
+ linux.hotplug_type = 2 (0x2) (int)
+ linux.sysfs_path = '/sys/class/usb_device/usbdev2.21' (string)
+ info.category = 'usbraw' (string)
+ info.parent = '/org/freedesktop/Hal/devices/usb_device_846_4240_3887_'
(string)
+
+1: udi = '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c_0'
+ net.arp_proto_hw_id = 801 (0x321) (int)
+ net.physical_device =
'/org/freedesktop/Hal/devices/usb_device___noserial' (string)
+ net.address = '00:09:5b:b9:96:8c' (string)
+ info.capabilities = { 'net', 'net.80211control' } (string list)
+ info.udi = '/org/freedesktop/Hal/devices/net_00_09_5b_b9_96_8c_0' (string)
+ linux.subsystem = 'net' (string)
+ net.originating_device =
'/org/freedesktop/Hal/devices/usb_device
Re: NM 0.7 on Fedora 8 with 3G USB Modems
On Thu, 2007-12-20 at 19:13 +, Peter Robinson wrote: > Hi All, > > Been reading through the list for details of the 3G modem support in > Fedora8/NM. It seems like its almost there, and from my playing it > seems like I've got it almost working :) > > Its one of the seemingly infamous Huawei E220's and a bit of a search > I got it ready to go, and added the problems I had to the RH BZ ticket > here https://bugzilla.redhat.com/show_bug.cgi?id=253096 (I added a > blacklist to the /etc/modprobe.d dir for the USB device). Is that all sorted out now? I seem to recall there was a bunch of traffic on the E220 on the Linux Kernel Mailing List with patches to make it work better. Whether those patches have been incorporated into the Fedora kernels already might make a difference. > I then added the .fdi file mentioned on the list earlier in the month > and restarted hal. NM now detects the modem but wouldn't connect. I > first discovered that the NM ppp plugin in the F8 rpm was looking for > /usr/lib64/NetworkManager/nm-pppd-plugin.so where as it was located in > /usr/lib64. A quick symlink fixed that. Which version of NM are you currently using? The output of 'rpm -qv NetworkManager' is what you want here. There's been a few changes recently in the plugin path of the ppp plugin. > I've attached the relevent portion of /var/log/messages which includes > a crash from NM as well. It looks like its almost successful but > there's a selinux message although the system is configured for > permissive (I think it might be a log). I didn't see an attachment, can you resend? dan > Any ideas or details that I've missed. Is there any config needed that > isn't in a GUI somewhere? > > BTW The network is the Three network in the UK. > > Cheers, > Peter > ___ > 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: NM in Fedora 8 wont connect to wired network
On Thu, 2007-12-20 at 00:29 +, mark lee wrote: > Hi all, > > Having a strange problem using Networkmanager in Fedora 8 - the > wireless works fine so far (an improvement for me over Fedora 7) - but > now the wired ethernet won't work! The wired connection is not > activated either when the ethernet is plugged in while wireless is > operating, or even when i turn the wireless off, so that the wired > network is the only one available. Clicking the "wired" connection in > the applet seems to do nothing (can't even detect that in the logs as > far as i can see). The ethernet connection is definitely working as > it can be brought up manually.Attached at the bottom of this email > is a few lines from /var/log/messages which occur about eth0, and some > configuration info. Are you running SELinux in Enforcing mode? When you plug in the cable, what is the output of both (as root): /sbin/mii-tool ethX /sbin/ethtool ethX (where ethX is your wired interface name) dan > Thanks for any help! > > Mark > > details: > -- > rpm -qa | grep NetworkManager: > > NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8 > NetworkManager-openvpn-0.7.0-2.svn3047.fc8 > NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 > NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8 > NetworkManager-0.7.0-0.6.6.svn3109.fc8 > > kernel: 2.6.23.8-63.fc8 > and its a Samsung Q35 if that helps. > > /var/log/messages: > --- > > Dec 19 23:54:30 localhost NetworkManager: starting... > Dec 19 23:54:30 localhost NetworkManager: Found radio > killswitch /org/fr > eedesktop/Hal/devices/ipw_wlan_switch > Dec 19 23:54:30 localhost NetworkManager: eth0: Device is > fully-supporte > d using driver 'b44'. > Dec 19 23:54:30 localhost NetworkManager: (eth0): exporting > device as /o > rg/freedesktop/NetworkManager/Device/4 > Dec 19 23:54:30 localhost NetworkManager: Now managing wired > Ethernet (8 > 02.3) device 'eth0'. > Dec 19 23:54:30 localhost NetworkManager: Bringing up device > eth0 > Dec 19 23:54:30 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is > not ready > Dec 19 23:54:30 localhost NetworkManager: Deactivating device > eth0. > Dec 19 23:54:33 localhost kernel: b44: eth0: Link is up at 100 Mbps, > full duplex. > Dec 19 23:54:33 localhost kernel: b44: eth0: Flow control is off for > TX and off for RX. > Dec 19 23:54:33 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth0: link > becomes ready > Dec 19 23:54:34 localhost kernel: [drm] Initialized drm 1.1.0 20060810 > Dec 19 23:54:34 localhost kernel: [drm] Initialized i915 1.6.0 > 20060119 on minor 0 > Dec 19 23:54:35 localhost avahi-daemon[]: Registering new address > record for fe80::213:77ff:fe28:75eb on eth0.*. > Dec 19 23:54:36 localhost NetworkManager: Trying to start the > supplicant... > Dec 19 23:54:36 localhost NetworkManager: (eth0) supplicant > interface is now in state 1 (from 0). > Dec 19 23:54:36 localhost NetworkManager: (wlan0) supplicant > manager is now in state 1 (from 0). > Dec 19 23:54:36 localhost NetworkManager: (eth0) supplicant > interface is now in state 2 (from 1). > Dec 19 23:54:36 localhost NetworkManager: (wlan0) supplicant > interface is now in state 2 (from 1). > > > > > > > > > > > > __ > Sent from Yahoo! - a smarter inbox. > ___ > 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: NM dont work in fc8 + madwifi
On Sun, 2007-12-23 at 16:20 -0200, Juliano Rodrigues wrote: > Hello, > > I compiled ath_pci version svn r3065. yum madwifi rpms drivers dont > work in an fresh install of fc8 with a AR5418 (Generic Macbook > Hardware) > (after fc8 fresh install I did 'yum update' at all) > > Now if I do 'ifup ath0' I have my internet access 100% stable and OK. Can you try using the ath5k driver that comes in the F8 kernels? madwifi is usually tempermental when used with wpa_supplicant and the standard WEXT driver. If ath5k doesn't work for you, let me know. Dan > NM output: > > NetworkManager: eth0: Device is fully-supported using driver > 'sky2'. > NetworkManager: (eth0): exporting device > as /org/freedesktop/Hal/devices/net_00_1b_63_32_fb_32 > NetworkManager: Now managing wired Ethernet (802.3) device > 'eth0'. > NetworkManager: Bringing up device eth0 > NetworkManager: Deactivating device eth0. > NetworkManager: ath0: Device is fully-supported using driver > 'ath_pci'. > NetworkManager: (ath0): exporting device > as /org/freedesktop/Hal/devices/net_00_1c_b3_be_9c_2d_0 > NetworkManager: Now managing wireless (802.11) device 'ath0'. > NetworkManager: Bringing up device ath0 > NetworkManager: Deactivating device ath0. > NetworkManager: (eth0) supplicant interface is now in state 2 > (from 1). > NetworkManager: (ath0) supplicant interface is now in state 2 > (from 1). > NetworkManager: SWITCH: no current connection, found better > connection 'Auto Emilio (ath0)'. > NetworkManager: Activating device ath0 > NetworkManager: Activation (ath0) Stage 1 of 5 (Device > Prepare) scheduled... > NetworkManager: Activation (ath0) Stage 1 of 5 (Device > Prepare) started... > NetworkManager: Activation (ath0) Stage 2 of 5 (Device > Configure) scheduled... > NetworkManager: Activation (ath0) Stage 1 of 5 (Device > Prepare) complete. > NetworkManager: Activation (ath0) Stage 2 of 5 (Device > Configure) starting... > NetworkManager: Activation (ath0/wireless): connection 'Auto > Emilio' requires no security. No secrets needed. > NetworkManager: Config: added 'ssid' value 'Emilio' > NetworkManager: Config: added 'key_mgmt' value 'NONE' > NetworkManager: Activation (ath0) Stage 2 of 5 (Device > Configure) complete. > NetworkManager: Config: set interface ap_scan to 1 > NetworkManager: (ath0) Supplicant interface state change: 0 -> > 2 > NetworkManager: (ath0) Supplicant interface state change: 2 -> > 3 > NetworkManager: (ath0) Supplicant interface state change: 3 -> > 0 > NetworkManager: (ath0) Supplicant interface state change: 0 -> > 2 > NetworkManager: (ath0) Supplicant interface state change: 2 -> > 3 > NetworkManager: Activation (ath0/wireless): association took > too long, failing activation. > NetworkManager: Activation (ath0) failed for access point > (Emilio) > NetworkManager: Marking connection 'Auto Emilio' invalid. > NetworkManager: Activation (ath0) failed. > > Can anyone helpme ? > > Thanks, Juliano. > ___ > 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: NM & NetScreen VPN
On Mon, 2007-12-24 at 17:23 +0100, Cyril Jaquier wrote: > Hi all, > > > At work, we have a Juniper firewall (NetScreen). Version 0.4.0 of vpnc > > is able to connect to such firewalls and has a specific option for this: > > > > Vendor netscreen > > > > Using vpnc directly works perfectly. I tried with networkmanager-vpnc. > > However, it is not possible to select this option in the wizard. So I > > set the option with gconf-editor. But then, NM exits with this message: > > > > Aug 26 17:56:26 [NetworkManager] > > nm_vpn_service_stop_connection(): (VPN Service > > org.freedesktop.NetworkManager.vpnc): could not stop connection '' > > because service was 6._ > > Aug 26 17:56:26 [NetworkManager] file nm-vpn-service.c: line 475 > > (nm_vpn_service_stage3_connect_cb): assertion failed: (service != NULL) > > > > Any chance to get support for NetScreen firewall? Is it possible to set > > vpnc option manually? > > > > Sorry but as I never received any answers to this e-mail, I just try > again ;) I'm probably not the only one how would like to use > network-manager-vpnc with NetScreen/Juniper firewalls. I'm sorry but my > knowledge of C, dbus, gnome and gtk+ programming is really poor :( But I > will probably take a look at the code and try something ;) Yay! vpnc now has options for the specific vendor you're trying to talk to. That just makes me sad :( No, NM vpnc plugin doesn't support that option yet... Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet not starting
On Mon, 2007-12-24 at 19:11 +0530, vikram b wrote: > Hi , >I have installed nm-applet from svn and when trying to run > got following error > > > #sudo nm-applet > > ** (nm-applet:12956): WARNING **: applet_dbus_manager_start > _service(): Could not acquire the NetworkManagerUserSettings service. > Message: 'Connection ":1.28 " is not allowed to own the service " > org.freedesktop.NetworkManagerUserSettings" due to security policies > in the configuration file' Yes, you need to ensure that the dbus permissions file is in the right place (usually /etc/dbus-1/system.d/) and that it's configured correctly for your distribution. For example, debian-based distros use group-based dbus authentication, and the default config file uses at_console permissions. Try looking around for the file that debian/ubuntu use for NM 0.6.x and try copying that. Dan > > (nm-applet:12956): GLib-CRITICAL **: g_hash_table_destroy: assertion > `hash_table != NULL' failed > > (nm-applet:12956): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > > (nm-applet:12956): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > > > > any clues ? I have done make install on the default path > (/usr/local/bin) > > > > thanks > > > Vikram > > ___ > 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: device control/sharing
On Sun, 2007-12-23 at 22:30 -0800, Steve Morgan wrote: > Is there a way to disable NetworkManager from using eth0. I need to > share my wireless connection to eth0 and whenever I plug in a cable to > eth0, NetworkManager wants to drop wlan0 and configure eth0 as the > default device. Does the SVN releases have multiple device control > with static settings? If this was the case I could use iptables to SVN doesn't yet have multiple active device support. Some distributions allow you to hide a device from NM 0.6.x, in Fedora & SUSE it's adding NM_CONTROLLED=no to your /etc/sysconfig/network-scripts/ifcfg-ethX file. In ubuntu I think you add the interface to your /etc/network/interfaces file. > configure my NAT and problem solved. Is the something I will be able > to achieve or should I just configure each device manually and drop > NetworkManager? (which is hard to do because this is a setup for a > friends laptop that does not have any linux knowledge and needs to > share his wireless access through eth0 so he can use his xbox live in > another room in his house) > > Running Fedora 8. This'll be a bit complicated right now with NM 0.7.x in F8. You're probably best to turn of NM for now. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ksplash freezes when service network-manager is running
On Mon, 2007-12-24 at 01:02 +0100, George Ruinelli wrote: > When the service "network-manager" is running, KDE is not able to start. > It hangs in the ksplash screen, when it initialize the services: "setting up > interprocess communication". > > When I start the service "network-manager" after KDE is startet, it works > really great! > > Where could be the Problem? > And how can I isolate the problem? > Is there a log file i can study? Does the IPC try to resolve something using DNS? If so, you don't necessarily have a network available so it whatever that service is shouldn't be trying to resolve hostnames unless there's really a network around. Try letting it sit for 30s or so, which is the default timeout for gethostbyname(). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disable prompting when connection attempt fails?
On Wed, 2007-12-19 at 12:27 -0500, Jeff Gold wrote: > Is there a NetworkManager setting to disable prompting when a wireless > connection attempt fails? I'm using NetworkManage on Fedora 8 and I > find that when something goes wrong on a WEP network I get a dialog > box asking for configuration details. I know the WEP key I've already > supplied is correct and I can cancel the dialog and select the network > again. But this is decidedly not painless networking for me. I would > like NetworkManager to simply retry the connection without > intervention. I've searched the web and the mailing list archives but > have not found a clear answer. > > What is the best way to make that happen? There's no way to do this right now; NM should probably re-try a terminated connection once before asking you again. I'm starting to think that the security dialog should only really come up during the connection process if the connection failed, not if the AP terminated you or the card just randomly decided you were connected and now you aren't. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proposed ad-hoc channel bug patch
On Thu, 2007-12-20 at 10:55 +0200, Ohad Lutzky wrote: > Hi all, > > Apparently it's not a WPA issue after all. Please check patch attached here: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/112009/comments/12 Contrary to the bug report, it's _totally_ a wpa_supplicant issue. wpa_supplicant 0.6.x has the required config option, it needs to be backported to wpa_supplicant 0.5.x. NM should _not_ be setting any wireless attributes like channel, BSSID, or SSID itself. So the patch is wrong. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & NetScreen VPN
On Mon, 2007-12-24 at 17:23 +0100, Cyril Jaquier wrote: > Hi all, > > > At work, we have a Juniper firewall (NetScreen). Version 0.4.0 of vpnc > > is able to connect to such firewalls and has a specific option for this: > > > > Vendor netscreen > > > > Using vpnc directly works perfectly. I tried with networkmanager-vpnc. > > However, it is not possible to select this option in the wizard. So I > > set the option with gconf-editor. But then, NM exits with this message: > > > > Aug 26 17:56:26 [NetworkManager] > > nm_vpn_service_stop_connection(): (VPN Service > > org.freedesktop.NetworkManager.vpnc): could not stop connection '' > > because service was 6._ > > Aug 26 17:56:26 [NetworkManager] file nm-vpn-service.c: line 475 > > (nm_vpn_service_stage3_connect_cb): assertion failed: (service != NULL) > > > > Any chance to get support for NetScreen firewall? Is it possible to set > > vpnc option manually? > > > > Sorry but as I never received any answers to this e-mail, I just try > again ;) I'm probably not the only one how would like to use > network-manager-vpnc with NetScreen/Juniper firewalls. I'm sorry but my > knowledge of C, dbus, gnome and gtk+ programming is really poor :( But I > will probably take a look at the code and try something ;) > > Merry Christmas to everybody :) For Juniper you need to use the openvpn plugin.. At least I have in the past. The one client with that POS concentrator finally got rid of it thank god... ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & NetScreen VPN
Hi all, > At work, we have a Juniper firewall (NetScreen). Version 0.4.0 of vpnc > is able to connect to such firewalls and has a specific option for this: > > Vendor netscreen > > Using vpnc directly works perfectly. I tried with networkmanager-vpnc. > However, it is not possible to select this option in the wizard. So I > set the option with gconf-editor. But then, NM exits with this message: > > Aug 26 17:56:26 [NetworkManager] > nm_vpn_service_stop_connection(): (VPN Service > org.freedesktop.NetworkManager.vpnc): could not stop connection '' > because service was 6._ > Aug 26 17:56:26 [NetworkManager] file nm-vpn-service.c: line 475 > (nm_vpn_service_stage3_connect_cb): assertion failed: (service != NULL) > > Any chance to get support for NetScreen firewall? Is it possible to set > vpnc option manually? > Sorry but as I never received any answers to this e-mail, I just try again ;) I'm probably not the only one how would like to use network-manager-vpnc with NetScreen/Juniper firewalls. I'm sorry but my knowledge of C, dbus, gnome and gtk+ programming is really poor :( But I will probably take a look at the code and try something ;) Merry Christmas to everybody :) Cyril Jaquier ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-applet not starting
Hi , I have installed nm-applet from svn and when trying to run got following error #sudo nm-applet ** (nm-applet:12956): WARNING **: applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service. Message: 'Connection ":1.28" is not allowed to own the service " org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file' (nm-applet:12956): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed (nm-applet:12956): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:12956): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed any clues ? I have done make install on the default path (/usr/local/bin) thanks Vikram ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
