Re: Two networks with the same SSID
2008/10/13 Tambet Ingo <[EMAIL PROTECTED]>: > The BSSID entry is what you need to use. See the tooltips of text > entry widgets to get more information what MAC and BSSID fields do. Thank you! It would be helpful if network-manager displayed the MAC of the AP in connection details, so one does not have to resort to terminal commands (iwconfig, dmesg). Now it displays only the MAC of the local network card. -- Marcin Kowalczyk [EMAIL PROTECTED] http://qrnik.knm.org.pl/~qrczak/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Networkmanager 0.7
I hav'nt tried setting the network entry, the last version i had that was not active. In the uk with three, the 2G and 3G services are provided by two different providers with separate network numbers, both networks are "available", and the module will often lock onto the one with the highest signal strength. Here Three does the 3G whilst Orange does the 2G fallback. This means that without a "kick" it often wont lock onto the right network. On 13 Oct 2008, at 19:58, Dan Williams wrote: On Mon, 2008-10-13 at 19:51 +0100, Tim Hawkins wrote: I have the 169G which is basically a very similar device with the same command language produced by the same manufacturer, and I have the same problem. The 169G is detected as a Huawei 620 I use a small script file with echo "AT+COPS=1,2,23420" > /dev/ttyUSB2 to achieve the same result. "23420" is the network number for 3 UK. Does the module not automatically register with the home network? Also, does setting "23420" in the connection editor's "Network:" entry not work for you? dan After using this command the modem switches from green flashing (GSM) to Blue Flashing (3G) , and network manager can dial and connect. To find the network number i use minicom with "AT+COPS=?" which returns a list of available networks. On 13 Oct 2008, at 19:36, Dan Williams wrote: On Mon, 2008-10-13 at 10:42 +0800, Ronald Wiplinger (Lists) wrote: Ronald Wiplinger (Lists) wrote: The latest version worked for me, but stopped working. I think I found a way that it works. I have to use first wvdial hspda, which gets my E220 to flash (slow) in blue and then the Network manager can connect. I tested this way several times on two different notebooks and it worked each time. Is there a special AT command that the modem needs to be put into data mode or something? Could you paste the wvdial config (ie, modem init strings) into a reply? Tambet: you've got an E220, right? Thanks, Dan bye Ronald I got a message entry (I agree with it, it is true ;-) ): /home/adamm/git/ubuntu-hardy/debian/buld/custom-source-eeepc/ drivers/hid/usbhid/hid-core.c: event field not found There is not even a /home/adamm on my system ;-) Another questions: 1. How can I switch back to a previous (working) version? On one of my EeePCs the user accidently upgraded, now he cannot connect anymore. Would be great if there would be a way to switch back. 2. I would need following configuration, how can I set this up: Connect via EeePC to the Internet, and because there is no Wireless lan provide wireless connection to other notebooks in that area. bye R. ___ 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: ZTE MF622 in CTBC Telecom Brazil
If you're using NetworkManager 0.7.0, simply create a Mobile Broadband connection - or, even better, NM will create an "automatic GSM connection" when it notes that there's a 3G modem plugged. What's the version of the NM on your system? (BTW, ZTE MF622 also, Brasil Telecom) - "Paulo Braganholo" <[EMAIL PROTECTED]> escreveu: > Hi, > > I have the the ZTE MF622 working in the kppp, but it does not work in > Network Manager. > > Here is the daemon.log: > > Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) starting > connection 'CTBC' > Oct 13 16:05:53 dv6604 NetworkManager: (ttyUSB0): device state > change: 3 -> 4 > Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) scheduled... > Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) started... > Oct 13 16:05:53 dv6604 NetworkManager: [1223924753.216701] > nm_serial_device_open(): (ttyUSB0) opening device... > Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) complete. > Oct 13 16:05:53 dv6604 NetworkManager: (ttyUSB0): powering up... > Oct 13 16:05:53 dv6604 NetworkManager: Registered on Roaming network > > Oct 13 16:05:53 dv6604 NetworkManager: Associated with network: > +COPS: 0,0,"CTBC",2 > Oct 13 16:06:54 dv6604 NetworkManager: dial_done(): Dialing timed > out > Oct 13 16:06:54 dv6604 NetworkManager: (ttyUSB0): device state > change: 4 -> 9 > Oct 13 16:06:54 dv6604 NetworkManager: [1223924814.003608] > nm_serial_device_close(): Closing device 'ttyUSB0' > Oct 13 16:06:54 dv6604 NetworkManager: Marking connection 'CTBC' > invalid. > Oct 13 16:06:54 dv6604 NetworkManager: Activation (ttyUSB0) failed. > > Oct 13 16:06:54 dv6604 NetworkManager: (ttyUSB0): device state > change: 9 -> 3 > Oct 13 16:06:54 dv6604 NetworkManager: (ttyUSB0): deactivating > device. > Oct 13 16:06:54 dv6604 NetworkManager: > nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx>= > 0' failed > Oct 13 16:06:54 dv6604 NetworkManager: > nm_system_device_flush_ip4_addresses_with_iface: assertion > `iface_idx>= 0' failed > > I think the problem is that the modem is waiting a dial tone, i don > know if this is a correct act. > > Thanks > > Paulo Braganholo > _ > Conheça o Windows Live Spaces, a rede de relacionamentos do > Messenger! > http://www.amigosdomessenger.com.br/ > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Cesar Cardoso http://fudeblog.zyakannazio.eti.br http://meadiciona.com/cesarcardoso ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
ZTE MF622 in CTBC Telecom Brazil
Hi, I have the the ZTE MF622 working in the kppp, but it does not work in Network Manager. Here is the daemon.log: Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) starting connection 'CTBC' Oct 13 16:05:53 dv6604 NetworkManager: (ttyUSB0): device state change: 3 -> 4 Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Oct 13 16:05:53 dv6604 NetworkManager: [1223924753.216701] nm_serial_device_open(): (ttyUSB0) opening device... Oct 13 16:05:53 dv6604 NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Oct 13 16:05:53 dv6604 NetworkManager: (ttyUSB0): powering up... Oct 13 16:05:53 dv6604 NetworkManager: Registered on Roaming network Oct 13 16:05:53 dv6604 NetworkManager: Associated with network: +COPS: 0,0,"CTBC",2 Oct 13 16:06:54 dv6604 NetworkManager: dial_done(): Dialing timed out Oct 13 16:06:54 dv6604 NetworkManager: (ttyUSB0): device state change: 4 -> 9 Oct 13 16:06:54 dv6604 NetworkManager: [1223924814.003608] nm_serial_device_close(): Closing device 'ttyUSB0' Oct 13 16:06:54 dv6604 NetworkManager: Marking connection 'CTBC' invalid. Oct 13 16:06:54 dv6604 NetworkManager: Activation (ttyUSB0) failed. Oct 13 16:06:54 dv6604 NetworkManager: (ttyUSB0): device state change: 9 -> 3 Oct 13 16:06:54 dv6604 NetworkManager: (ttyUSB0): deactivating device. Oct 13 16:06:54 dv6604 NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx>= 0' failed Oct 13 16:06:54 dv6604 NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx>= 0' failed I think the problem is that the modem is waiting a dial tone, i don know if this is a correct act. Thanks Paulo Braganholo _ Conheça o Windows Live Spaces, a rede de relacionamentos do Messenger! http://www.amigosdomessenger.com.br/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Networkmanager 0.7
I have the 169G which is basically a very similar device with the same command language produced by the same manufacturer, and I have the same problem. The 169G is detected as a Huawei 620 I use a small script file with echo "AT+COPS=1,2,23420" > /dev/ttyUSB2 to achieve the same result. "23420" is the network number for 3 UK. After using this command the modem switches from green flashing (GSM) to Blue Flashing (3G) , and network manager can dial and connect. To find the network number i use minicom with "AT+COPS=?" which returns a list of available networks. On 13 Oct 2008, at 19:36, Dan Williams wrote: On Mon, 2008-10-13 at 10:42 +0800, Ronald Wiplinger (Lists) wrote: Ronald Wiplinger (Lists) wrote: The latest version worked for me, but stopped working. I think I found a way that it works. I have to use first wvdial hspda, which gets my E220 to flash (slow) in blue and then the Network manager can connect. I tested this way several times on two different notebooks and it worked each time. Is there a special AT command that the modem needs to be put into data mode or something? Could you paste the wvdial config (ie, modem init strings) into a reply? Tambet: you've got an E220, right? Thanks, Dan bye Ronald I got a message entry (I agree with it, it is true ;-) ): /home/adamm/git/ubuntu-hardy/debian/buld/custom-source-eeepc/ drivers/hid/usbhid/hid-core.c: event field not found There is not even a /home/adamm on my system ;-) Another questions: 1. How can I switch back to a previous (working) version? On one of my EeePCs the user accidently upgraded, now he cannot connect anymore. Would be great if there would be a way to switch back. 2. I would need following configuration, how can I set this up: Connect via EeePC to the Internet, and because there is no Wireless lan provide wireless connection to other notebooks in that area. bye R. ___ 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: Problems with Networkmanager 0.7
On Mon, 2008-10-13 at 19:51 +0100, Tim Hawkins wrote: > I have the 169G which is basically a very similar device with the same > command language produced by the same manufacturer, and I have the > same problem. The 169G is detected as a Huawei 620 > > I use a small script file with > > echo "AT+COPS=1,2,23420" > /dev/ttyUSB2 > > to achieve the same result. "23420" is the network number for 3 UK. Does the module not automatically register with the home network? Also, does setting "23420" in the connection editor's "Network:" entry not work for you? dan > After using this command the modem switches from green flashing (GSM) > to Blue Flashing (3G) , and network manager can dial and connect. > > To find the network number i use minicom with "AT+COPS=?" which > returns a list of available networks. > > On 13 Oct 2008, at 19:36, Dan Williams wrote: > > > On Mon, 2008-10-13 at 10:42 +0800, Ronald Wiplinger (Lists) wrote: > >> Ronald Wiplinger (Lists) wrote: > >>> The latest version worked for me, but stopped working. > >>> > >>> > >> > >> I think I found a way that it works. > >> I have to use first wvdial hspda, which gets my E220 to flash > >> (slow) in > >> blue and then the Network manager can connect. > >> > >> I tested this way several times on two different notebooks and it > >> worked > >> each time. > > > > Is there a special AT command that the modem needs to be put into data > > mode or something? Could you paste the wvdial config (ie, modem init > > strings) into a reply? > > > > Tambet: you've got an E220, right? > > > > Thanks, > > Dan > > > >> bye > >> > >> Ronald > >> > >> > >>> I got a message entry (I agree with it, it is true ;-) ): > >>> > >>> /home/adamm/git/ubuntu-hardy/debian/buld/custom-source-eeepc/ > >>> drivers/hid/usbhid/hid-core.c: > >>> event field not found > >>> > >>> There is not even a /home/adamm on my system ;-) > >>> > >>> > >>> Another questions: > >>> > >>> 1. How can I switch back to a previous (working) version? > >>> On one of my EeePCs the user accidently upgraded, now he cannot > >>> connect > >>> anymore. Would be great if there would be a way to switch back. > >>> > >>> 2. I would need following configuration, how can I set this up: > >>> Connect via EeePC to the Internet, and because there is no > >>> Wireless lan > >>> provide wireless connection to other notebooks in that area. > >>> > >>> > >>> bye > >>> > >>> R. > >>> > >>> ___ > >>> 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: How do I use 2 interfaces for different applications?
On Fri, 2008-10-10 at 14:43 -0700, defcon wrote: > I have a work-internal access point and a work-public access point and > I want to be able to browse the internet on the work-internal > accesspoint with my zd1211 wireless card and download files via > torrent with the work-public interface. I am able to connect to both > at the same time but how do I use 1 interface per application or > specify which application gets which interface. Any documentation > would be appreciated This would require support from the application itself to bind to a specific local IP address. You can't use IP routing here because with bittorrent, you'll be trying to contact a huge number of IP addresses in all different subnets. Thus, the application itself has to be smart enough to do the required magic at a socket/TCP level I think. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: OK button of "Mobile Broadband"
On Fri, 2008-10-10 at 23:33 -0300, Roberson Carlos wrote: > It is my impression or the OK button of "Mobile Broadband" > is not getting active. You mean in the connection editor? What package or SVN version of NM do you have, and what settings are you entering into the window? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet and NetworkManager svn after 29 Sept
On Sat, 2008-10-11 at 19:10 +1100, James . wrote: > > > On Sat, Oct 11, 2008 at 7:07 PM, James . <[EMAIL PROTECTED]> wrote: > I use a couple of laptops with iwl3945 and one with rt2860sta > and I connect to three wireless access points on a daily > basis. One is WEP, one is WPA Personal and one is WPA > Enterprise with PEAP (university). > > With previous versions of Networkmanager before around 29th of > September, connections to WEP and WPA Personal through > nm-applet worked fine. Recently I noticed that I can only > connect to wireless access points with security of WEP or less > through nm-applet gui. If I click on the wireless connection > through clicking on the icon and selecting a WPA security > connection, the following error results: > > > "Couldnt create default connection" in activate helper function. > > I discovered was that NetworkManager or nm-applet is no longer passing > correct security flags, and the function get_secrets falls through to > the end, resulting in the error. Could you paste in the output of '/sbin/iwlist wlan0 scan' for the block describing your AP? Thanks! Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Networkmanager 0.7
On Mon, 2008-10-13 at 10:42 +0800, Ronald Wiplinger (Lists) wrote: > Ronald Wiplinger (Lists) wrote: > > The latest version worked for me, but stopped working. > > > > > > I think I found a way that it works. > I have to use first wvdial hspda, which gets my E220 to flash (slow) in > blue and then the Network manager can connect. > > I tested this way several times on two different notebooks and it worked > each time. Is there a special AT command that the modem needs to be put into data mode or something? Could you paste the wvdial config (ie, modem init strings) into a reply? Tambet: you've got an E220, right? Thanks, Dan > bye > > Ronald > > > > I got a message entry (I agree with it, it is true ;-) ): > > > > /home/adamm/git/ubuntu-hardy/debian/buld/custom-source-eeepc/drivers/hid/usbhid/hid-core.c: > > event field not found > > > > There is not even a /home/adamm on my system ;-) > > > > > > Another questions: > > > > 1. How can I switch back to a previous (working) version? > > On one of my EeePCs the user accidently upgraded, now he cannot connect > > anymore. Would be great if there would be a way to switch back. > > > > 2. I would need following configuration, how can I set this up: > > Connect via EeePC to the Internet, and because there is no Wireless lan > > provide wireless connection to other notebooks in that area. > > > > > > bye > > > > R. > > > > ___ > > 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: Preventing automatic DHCP requests
On Mon, 2008-10-13 at 12:30 +0200, Sverre Bakke wrote: > Hi > > I was wondering if there are any way to prevent Network Manager from > automatically send a DHCP request upon connecting to a (any) network? > What I want to achieve is so that every time I connect to a network > (using NM), network manager just waits for me to manually ask for the > IP settings through dhclient or similar. You can set up a static IP connection with NM 0.7 and set it to not autoconnect, at which point you can manually choose which connection you'd like to make from the menu whenever you want to do so. Then you can delete the "Auto Ethernet" connection and you can have complete manual control over when and what your network settings for the ethernet card are. Dan > I tried looking for the documentation, but could not find anything > about this neither on the NM website or on google so I was hoping > anyone here could either point me in the right direction or confirm > whether its even possible or not so I can stop wasting my time if its > not possible. I appreciate all answers to this question, both positive > and negative. > > Thank you > > -- Sverre Bakke > ___ > 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
Preventing automatic DHCP requests
Hi I was wondering if there are any way to prevent Network Manager from automatically send a DHCP request upon connecting to a (any) network? What I want to achieve is so that every time I connect to a network (using NM), network manager just waits for me to manually ask for the IP settings through dhclient or similar. I tried looking for the documentation, but could not find anything about this neither on the NM website or on google so I was hoping anyone here could either point me in the right direction or confirm whether its even possible or not so I can stop wasting my time if its not possible. I appreciate all answers to this question, both positive and negative. Thank you -- Sverre Bakke ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: dispatcher issue
On Mon, 2008-10-13 at 10:52 +0200, Andreas Neiser wrote: > Steve wrote: > > [The dispatcher in NN 0.7 and scripts from <0.7, right?] > > Dumb question, I'm sure you tried that: > Put a small test script in /etc/networkmanager/dispatcher.d which just > writes its arguments to a file, maybe including a timestamp. AFAIK the > dispatcher in 0.7 was rewritten so that more parameters are given to the > dispatcher script. Since you have an if-statement in your script, it > could be that the paramater $2 is not always up or down but something else. Correct, it's either "up", "down", "vpn-up", "vpn-down", or "hostname". Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: dispatcher issue
Steve wrote: > [The dispatcher in NN 0.7 and scripts from <0.7, right?] Dumb question, I'm sure you tried that: Put a small test script in /etc/networkmanager/dispatcher.d which just writes its arguments to a file, maybe including a timestamp. AFAIK the dispatcher in 0.7 was rewritten so that more parameters are given to the dispatcher script. Since you have an if-statement in your script, it could be that the paramater $2 is not always up or down but something else. Hth Andreas ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
