about HAL and USB EVDO usbserial problem
hi,all! Now i met a problem with usb evdo card! When i insmod usbserial with vendor id and product id,pppd connect OK with ttyUSB1 and can access internet with ppp0! But I want to use Networkmanager with ppp,because ppp0 isn't a standard platform device ,it is kernel virtual net (/sys/device/virtual/net/ppp0),causes HAL can't know it is a real network,Networkmanager depend on HAL! Serveral days ago i have fix marvell8686 driver kernel hotplug bug,does usbserial driver miss similiar issue ? Thanks all! Platform :ARM11 Linux kernel version:2.6.24.2 to...@china ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bug report for connecting to eap-tls wireless network with a CA chain
On Wed, Sep 9, 2009 at 05:05, zignz...@zign.cn wrote: Hi, I think I got a bug in network-manager 7.0.100 and 7.1 when connecting to eap-tls wireless network with a CA chain. I found that the Network-manager only pass the the first CA cert to the wpa_supplicant if you have more than one CA cert in the file, which may result in the connection failure. https://bugzilla.gnome.org/show_bug.cgi?id=594466 The description there is probably not very clear, but it's the same thing. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager ignores virtual tap0 device
The tap0 device is created by openvpn but not pushed any network details - openvpn expects a dhcp client to lease an IP. When NetworkManager sees the device: Sep 9 11:41:09 cinnabar nm-system-settings: Added default wired connection 'Auto tap0' for /org/freedesktop/Hal/devices/net_de_c1_d5_98_e6_52 According to nm-connection-editor, aside from MAC addresses 'Auto tap0' is exactly like 'Auto eth0' However when restarting NetworkManager, it attempts to start up the disconnected eth0 and then deactivates it, but doesn't touch tap0. With one failed assertion? Sep 9 12:08:13 cinnabar NetworkManager: info Found radio killswitch /org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan Sep 9 12:08:13 cinnabar NetworkManager: nm_device_ethernet_new: assertion `driver != NULL' failed Sep 9 12:08:13 cinnabar NetworkManager: info (eth0): new Ethernet device (driver: 'b44') And nm-tool lists only eth0 and wlan0. I also haven't found any HAL or PolicyKit policies that are preventing NetworkManager from managing the tap0 device. Some details about the tap0 device: net.originating_device = '/org/freedesktop/Hal/devices/computer' (string) net.interface = 'tap0' (string) linux.sysfs_path = '/sys/devices/virtual/net/tap0' (string) info.parent = '/org/freedesktop/Hal/devices/computer' (string) The convenience of NetworkManager managing the tap0 device is that it properly updates /etc/resolv.conf and doesn't mangle my routes (and also doesnt require sudo) thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
