Re: iPass Integration
On Tue, 2009-05-19 at 09:26 -0400, Brian Long wrote: > I was wondering if anyone has considered how to take advantage of > iPass hotspots on Linux systems. Could a plugin be written for > NetworkManager that would allow for iPass authentication at their > supported hotspots? Do these require a re-DHCP after authenticating? If not, they could work transparently using dispatcher scripts, or a program listening on D-Bus for new network connections to known SSIDs, then performing the auto-login with stored credentials. This has already been proven to work for various AT&T wifi hotspots, there are some links around for it. Dan > As it stands, Linux users must follow various convoluted steps to try > to get web authentication working since iPass does not provide a > native Linux client. Those steps seem to vary by location. I was > just wondering if anyone has considered this Linux limitation and is > working on a solution. > > /Brian/ > ___ > 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: Network Manager's supported Modem list
On Fri, 2009-05-22 at 11:01 +0200, Herriot, Nicholas, VF-Group wrote: > I guess my question has already been answered. > Network Manager does not have a strategy for testing and integration with > different USB Modems to ensure compatibility. Which is understandable given > the remit. There is a testing strategy, which is essentially whenever we make changes to device detection or to core mobile broadband code, we test the code with as many devices as we can to ensure that it works. However, there are limitations to this strategy as we only have so many devices, so much $$, and so many people actively participating in the testing. We also rely on the kernel community for testing of the USB stack, but in general we assume that the kernel + USB stack will work reliably (which is not always the case [1]). The ideal testing strategy would be to have agreements with hardware manufacturers and network operators for pre-release hardware to ensure compatibility. Second, obtain agreements with the OEMs for hardware documentation to assure that their devices are supported more fully than can be determined by reverse-engineering or USB sniffing their Windows drivers. Third, obtain plans/SIMs with major network operators to ensure that we can test with a specific operator/card combination. Fourth, integrate unit tests including modem-behavior modeling into the NetworkManager unit test framework to reduce the need for actual hardware when doing primary validation on code changes. > I guess this should be work carried out between Hardware manufacturer and > Network operators. What would be better would be: Obviously the NM developers are never going to get as much access to hardware as the OEMs and the operators themselves, or as much lead-time for testing. > 1)A list of devices that have been tested and verified to work, with a > list of tests that were carried out. (Community members could help with this.) I just posted my list in this thread. My basic validation includes multiple runs of device recognition (ie hotplug), connection to the network, basic browsing, device disconnection, repeat. > 2)A list of devices that have unique 'code' in the application that are > needed to handle them, coupled with the generic list. That list is essentially: Huawei E160/169 Huawei EC121 Ericsson F3507g Option 'hso' cards Sierra AC860 > It's a shame there is no way for plugins to be written to cope with USB modem > card differences as is done for the Betavine.net linux driver. (e.g. The > product ID/ Vendor ID on some Huawei cards which are incorrect in purpose to > get round an issue on Window machines.) This kind of thing could be handled > in plugin maybe! .. ;-) ... That is incorrect. ModemManager is built around a generic plugin architecture specifically for this reason, and there are already plugins for a variety of different card manufacturers. Most attention is now directed at ModemManager and bringing up MM support for the oddball cards that were hacked into NetworkManager 0.7.1. Dan > > I agree, it would help support guys everywhere. > > > Kind regards, Nicholas. > > > -Original Message- > From: Peteris Krisjanis [mailto:pec...@gmail.com] > Sent: 22 May 2009 08:46 > To: Dan Williams > Cc: Herriot, Nicholas, VF-Group; networkmanager-list@gnome.org > Subject: Re: Network Manager's supported Modem list > > But it would be hard to make such list looking at the code? If not, I could > try to make such list. It would help Linux support guys everywhere. > > Cheers, > Peter > > 2009/5/21 Dan Williams : > > On Wed, 2009-05-20 at 14:11 +0200, Herriot, Nicholas, VF-Group wrote: > >> Hi, > >> > >> Is there such a thing as Network Manager's supported USB Modem list? > >> And if this is a 'no' what part of the code base do I look at to find > >> out the supported modems? > > > > It depends on a few things... first, the kernel drivers having the > > IDs for the modems. In general, NM will support generic modems that > > use ATDT-style connection setup (ie, PPP). It also supports Option > > 'hso'-style modems that use OWAN-style call setup. > > > > As of 0.7.1, I think we've got support for most of the modems that are > > currently in wide use. We do occasionally find quirks (like Huawei > > CDMA modems from Reliance India that return "COMMAND NOT SUPPORT" > > instead of "ERROR", for example). > > > >> i.e. is there a 'conf' file with scripts for each modem? > > > > Nope, they are handled automatically in the code. Scripts aren't > > really flexible enough, or if they are, they turn into a programming > > language anyway. > > > > Dan > > > >> Kind regards, Nicholas. > >> > >> > >> Nicholas Herriot > >> > >> Web Technologies Researcher > >> Vodafone Group R&D - UK > >> > >> www.betavine.net > >> www.betavine.mobi (from mobile) > >> > >> Mobile: +44 (0) 7717275049 > >> Fax: +44 (0) 1635 686484 > >> > >> Vodafone Group Service Limited > >> Registered Office: Vodafone Hous
Re: Network Manager's supported Modem list
On Fri, 2009-05-22 at 10:45 +0300, Peteris Krisjanis wrote: > But it would be hard to make such list looking at the code? If not, I > could try to make such list. It would help Linux support guys > everywhere. It would be somewhat hard, since the code doesn't mention most modems specifically. I or Tambet have tested NetworkManager 0.7.0 and/or 0.7.1 with at least the following devices. I have *-ed the ones I personally own. * Sony Ericsson F3507g (aka Dell 5530) Sony Ericsson MD300 * Sony Ericsson TM-506 (via USB cable) * LG PM325 (via USB cable) * BUSlink SCWi275u * Option iCON 225 * Option ICON 7.2 * Option GT MAX 3.6 (aka Option GT Ultra) Sierra Wireless AirCard 580 (Sprint) Sierra Wireless AirCard 881 (use latest AT&T firmware) * Sierra Wireless AirCard 860 Sierra Wireless AirCard 595U (Sprint/Verizon) * Sierra Wireless MC8775 * Huawei E160G Huawei E220 * Novatel Merlin S720 (Sprint/Verizon) * Novatel Merlin XU870 (aka Dell 5510) Novatel Ovation U727 (Sprint/Verizon) Novatel Merlin S620 (Sprint) * Qualcomm Gobi (GSM firmware) Kyocera KPC650 (Verizon) Verizon Wireless PC5750 Verizon Wireless UM175 Verizon Wireless KPC680 I have heard that NM works with the following additional devices: Huawei E169 Huawei EC121 (Reliance India) Huawei E168 (Reliance India) Option Nozomi (others I can't remember) In general, devices supported by the Linux 'option', 'hso', 'sierra', and 'nozomi' drivers will work with NetworkManager. Dan > Cheers, > Peter > > 2009/5/21 Dan Williams : > > On Wed, 2009-05-20 at 14:11 +0200, Herriot, Nicholas, VF-Group wrote: > >> Hi, > >> > >> Is there such a thing as Network Manager's supported USB Modem list? > >> And if this is a 'no' what part of the code base do I look at to find > >> out the supported modems? > > > > It depends on a few things... first, the kernel drivers having the IDs > > for the modems. In general, NM will support generic modems that use > > ATDT-style connection setup (ie, PPP). It also supports Option > > 'hso'-style modems that use OWAN-style call setup. > > > > As of 0.7.1, I think we've got support for most of the modems that are > > currently in wide use. We do occasionally find quirks (like Huawei CDMA > > modems from Reliance India that return "COMMAND NOT SUPPORT" instead of > > "ERROR", for example). > > > >> i.e. is there a 'conf' file with scripts for each modem? > > > > Nope, they are handled automatically in the code. Scripts aren't really > > flexible enough, or if they are, they turn into a programming language > > anyway. > > > > Dan > > > >> Kind regards, Nicholas. > >> > >> > >> Nicholas Herriot > >> > >> Web Technologies Researcher > >> Vodafone Group R&D - UK > >> > >> www.betavine.net > >> www.betavine.mobi (from mobile) > >> > >> Mobile: +44 (0) 7717275049 > >> Fax: +44 (0) 1635 686484 > >> > >> Vodafone Group Service Limited > >> Registered Office: Vodafone House, The Connection, Newbury, Berkshire, > >> RG14 2FN > >> Registered in England No 3802001 > >> ___ > >> 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 > > > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Why wireless is disable by radio killswitch?
On Fri, 2009-05-22 at 17:40 +0800, Bin Li wrote:
> Hi,
>
> I've use NM 0.7.0.r4359, and from the lshal I could found "killswitch".
> $ lshal --version
> lshal version 0.5.12
>
> udi = '/org/freedesktop/Hal/devices/dell_wlan_switch'
> info.capabilities = {'killswitch'} (string list)
> info.category = 'killswitch' (string)
> info.interfaces = {'org.freedesktop.Hal.Device.KillSwitch'} (string list)
> info.parent = '/org/freedesktop/Hal/devices/platform_dcdbas' (string)
> info.product = 'Dell WLAN Switch' (string)
> info.subsystem = 'unknown' (string)
> info.udi = '/org/freedesktop/Hal/devices/dell_wlan_switch' (string)
> killswitch.access_method = 'dell' (string)
> killswitch.type = 'wlan' (string)
> org.freedesktop.Hal.Device.KillSwitch.method_argnames = {'power',
> ''} (string list)
> org.freedesktop.Hal.Device.KillSwitch.method_execpaths =
> {'hal-system-killswitch-set-power', 'hal-system-killswitch-get-power'}
> (string list)
> org.freedesktop.Hal.Device.KillSwitch.method_names = {'SetPower',
> 'GetPower'} (string list)
> org.freedesktop.Hal.Device.KillSwitch.method_signatures = {'b', ''}
> (string list)
>
> But when I run "NetowrkManager --no-daemon" with root permission, it prompt:
>
> NetworkManager: eth1: driver is 'wl'.
> NetworkManager: eth1: driver does not support SSID scans
> (scan_capa 0x00).
> NetworkManager: Found new 802.11 WiFi device 'eth1'.
> NetworkManager: (eth1): exported as
> /org/freedesktop/Hal/devices/net_00_22_5f_53_60_01
> NetworkManager: Wireless now disabled by radio killswitch
>
> And I've check the switch is on, the wireless led is light.
>
> When I use the wireless-tools, the iwlist and iwconfig, the wireless
> card could be configured successfully, and works fine.
>
> Any ideas?
What have you got in /sys/class/rfkill? What's the output of both:
cat /sys/class/rfkill/*/type
cat /sys/class/rfkill/*/state
Next, we need to ask HAL what its killswitch state is:
dbus-send --system --print-reply --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/dell_wlan_switch
org.freedesktop.Hal.Device.KillSwitch.GetPower
If that returns 'int32 0', then HAL believes your killswitch to be
turned on, and your radio should be disabled. That would be a HAL bug
then.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: VPN connections in NetworkManager have strange behaviour
Le 18/05/2009 18:02, Dan Williams a écrit : Ugh. Since it is a TUN device, we probably should be defaulting to a /32 in NetworkManager-vpnc. Any chance you could ask your admin to fix the VPN settings? Technically it is a bug in the setup; no way to know what the netmask is if the admin doesn't pass one. Dan Should not NetworkManager reproduce the vpnc behaviour, since it works (at least in my case) ? Anyway, it seems to be not the only problem. (or maybe not this problem at all). I modified the script (described in your first answer) to use 255.255.255.255 as the netmask, given with the INTERNAL_IP4_NETMASK variable. Using vpnc : [r...@axel-asus libexec]# LANG="C" netstat -aren Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 62.39.X.X 192.168.246.254 255.255.255.255 UGH 0 00 eth0 192.168.246.0 0.0.0.0 255.255.255.0 U 1 00 eth0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 00 virbr0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tun0 [r...@axel-asus libexec]# ifconfig tun0 tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet adr:10.240.200.10 P-t-P:10.240.200.10 Masque:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1412 Metric:1 [r...@axel-asus libexec]# ping 10.240.62.13 PING 10.240.62.13 (10.240.62.13) 56(84) bytes of data. 64 bytes from 10.240.62.13: icmp_seq=1 ttl=121 time=22.5 ms ^C --- 10.240.62.13 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 550ms rtt min/avg/max/mdev = 22.578/22.578/22.578/0.000 ms And using NetworkManager, the routes are the same. The interface configuration is the same too now, with the same netmask. [r...@axel-asus libexec]# LANG="C" netstat -aren Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 62.39.X.X 192.168.246.254 255.255.255.255 UGH 0 00 eth0 192.168.246.0 0.0.0.0 255.255.255.0 U 1 00 eth0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 00 virbr0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tun0 [r...@axel-asus libexec]# ifconfig tun0 tun0 inet adr:10.240.200.10 P-t-P:10.240.200.10 Masque:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1412 Metric:1 [r...@axel-asus libexec]# ping 10.240.62.13 PING 10.240.62.13 (10.240.62.13) 56(84) bytes of data. ^C --- 10.240.62.13 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3406ms So, with same routes, same interface configuration, the results are different. Is there something I could do to debug that ? (tcpdump traces, debug level to enable, and so on..) Thanks Axel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Why wireless is disable by radio killswitch?
Hi,
I've use NM 0.7.0.r4359, and from the lshal I could found "killswitch".
$ lshal --version
lshal version 0.5.12
udi = '/org/freedesktop/Hal/devices/dell_wlan_switch'
info.capabilities = {'killswitch'} (string list)
info.category = 'killswitch' (string)
info.interfaces = {'org.freedesktop.Hal.Device.KillSwitch'} (string list)
info.parent = '/org/freedesktop/Hal/devices/platform_dcdbas' (string)
info.product = 'Dell WLAN Switch' (string)
info.subsystem = 'unknown' (string)
info.udi = '/org/freedesktop/Hal/devices/dell_wlan_switch' (string)
killswitch.access_method = 'dell' (string)
killswitch.type = 'wlan' (string)
org.freedesktop.Hal.Device.KillSwitch.method_argnames = {'power',
''} (string list)
org.freedesktop.Hal.Device.KillSwitch.method_execpaths =
{'hal-system-killswitch-set-power', 'hal-system-killswitch-get-power'}
(string list)
org.freedesktop.Hal.Device.KillSwitch.method_names = {'SetPower',
'GetPower'} (string list)
org.freedesktop.Hal.Device.KillSwitch.method_signatures = {'b', ''}
(string list)
But when I run "NetowrkManager --no-daemon" with root permission, it prompt:
NetworkManager: eth1: driver is 'wl'.
NetworkManager: eth1: driver does not support SSID scans
(scan_capa 0x00).
NetworkManager: Found new 802.11 WiFi device 'eth1'.
NetworkManager: (eth1): exported as
/org/freedesktop/Hal/devices/net_00_22_5f_53_60_01
NetworkManager: Wireless now disabled by radio killswitch
And I've check the switch is on, the wireless led is light.
When I use the wireless-tools, the iwlist and iwconfig, the wireless
card could be configured successfully, and works fine.
Any ideas?
Thanks!
Sincerely Yours,
Bin Li
http://cn.opensuse.org
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Network Manager's supported Modem list
I guess my question has already been answered. Network Manager does not have a strategy for testing and integration with different USB Modems to ensure compatibility. Which is understandable given the remit. I guess this should be work carried out between Hardware manufacturer and Network operators. What would be better would be: 1) A list of devices that have been tested and verified to work, with a list of tests that were carried out. (Community members could help with this.) 2) A list of devices that have unique 'code' in the application that are needed to handle them, coupled with the generic list. It's a shame there is no way for plugins to be written to cope with USB modem card differences as is done for the Betavine.net linux driver. (e.g. The product ID/ Vendor ID on some Huawei cards which are incorrect in purpose to get round an issue on Window machines.) This kind of thing could be handled in plugin maybe! .. ;-) ... I agree, it would help support guys everywhere. Kind regards, Nicholas. -Original Message- From: Peteris Krisjanis [mailto:pec...@gmail.com] Sent: 22 May 2009 08:46 To: Dan Williams Cc: Herriot, Nicholas, VF-Group; networkmanager-list@gnome.org Subject: Re: Network Manager's supported Modem list But it would be hard to make such list looking at the code? If not, I could try to make such list. It would help Linux support guys everywhere. Cheers, Peter 2009/5/21 Dan Williams : > On Wed, 2009-05-20 at 14:11 +0200, Herriot, Nicholas, VF-Group wrote: >> Hi, >> >> Is there such a thing as Network Manager's supported USB Modem list? >> And if this is a 'no' what part of the code base do I look at to find >> out the supported modems? > > It depends on a few things... first, the kernel drivers having the > IDs for the modems. In general, NM will support generic modems that > use ATDT-style connection setup (ie, PPP). It also supports Option > 'hso'-style modems that use OWAN-style call setup. > > As of 0.7.1, I think we've got support for most of the modems that are > currently in wide use. We do occasionally find quirks (like Huawei > CDMA modems from Reliance India that return "COMMAND NOT SUPPORT" > instead of "ERROR", for example). > >> i.e. is there a 'conf' file with scripts for each modem? > > Nope, they are handled automatically in the code. Scripts aren't > really flexible enough, or if they are, they turn into a programming > language anyway. > > Dan > >> Kind regards, Nicholas. >> >> >> Nicholas Herriot >> >> Web Technologies Researcher >> Vodafone Group R&D - UK >> >> www.betavine.net >> www.betavine.mobi (from mobile) >> >> Mobile: +44 (0) 7717275049 >> Fax: +44 (0) 1635 686484 >> >> Vodafone Group Service Limited >> Registered Office: Vodafone House, The Connection, Newbury, >> Berkshire, >> RG14 2FN >> Registered in England No 3802001 >> ___ >> 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 > -- mortigi tempo Pēteris Krišjānis ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager's supported Modem list
But it would be hard to make such list looking at the code? If not, I could try to make such list. It would help Linux support guys everywhere. Cheers, Peter 2009/5/21 Dan Williams : > On Wed, 2009-05-20 at 14:11 +0200, Herriot, Nicholas, VF-Group wrote: >> Hi, >> >> Is there such a thing as Network Manager's supported USB Modem list? >> And if this is a 'no' what part of the code base do I look at to find >> out the supported modems? > > It depends on a few things... first, the kernel drivers having the IDs > for the modems. In general, NM will support generic modems that use > ATDT-style connection setup (ie, PPP). It also supports Option > 'hso'-style modems that use OWAN-style call setup. > > As of 0.7.1, I think we've got support for most of the modems that are > currently in wide use. We do occasionally find quirks (like Huawei CDMA > modems from Reliance India that return "COMMAND NOT SUPPORT" instead of > "ERROR", for example). > >> i.e. is there a 'conf' file with scripts for each modem? > > Nope, they are handled automatically in the code. Scripts aren't really > flexible enough, or if they are, they turn into a programming language > anyway. > > Dan > >> Kind regards, Nicholas. >> >> >> Nicholas Herriot >> >> Web Technologies Researcher >> Vodafone Group R&D - UK >> >> www.betavine.net >> www.betavine.mobi (from mobile) >> >> Mobile: +44 (0) 7717275049 >> Fax: +44 (0) 1635 686484 >> >> Vodafone Group Service Limited >> Registered Office: Vodafone House, The Connection, Newbury, Berkshire, >> RG14 2FN >> Registered in England No 3802001 >> ___ >> 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 > -- mortigi tempo Pēteris Krišjānis ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
