Re: ifcfg-rh and wpa_supplicant
On 05/19/2012 03:43 AM, Dan Williams wrote: On Fri, 2012-05-18 at 23:39 +0200, Oncaphillis wrote: On 05/18/2012 11:23 PM, Dan Williams wrote: On Thu, 2012-05-17 at 09:58 +0200, Oncaphillis wrote: Hi, I'm using Fedora16 and I'm trying to set up NetworkManager to connect to a wlan on startup via /etc/sysconfig/network-scrip/ifcfg-wlan0 or /etc/sysconfig/network-scrip/ifcfg-. It seems the settings in /etc/sysconfig/wpa_supplicant are ignored if wpa_supplicant is managed by the NetworkManager,but I don't see any option to pass the -D option to wpa_supplicant. Correct, the settings in /etc/sysconfig/wpa_supplicant can be harmful when NetworkManager is used, because NetworkManager figures out whether to use the wext, nl80211, or wired driver as appropriate. What's the reason you want to use a specific supplicant driver? Dan Simply the observation that wpa_supplicant fails to associate when not using -Dwext What wifi kernel driver? 04:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PC Subsystem: Device 1a3b:1067 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at febf (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Kernel driver in use: ath9k Kernel modules: ath9k I got the source rpm at hand. If someone points me to the position where the correct driver gets determined I can patch it. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ifcfg-rh and wpa_supplicant
On Fri, 2012-05-18 at 23:39 +0200, Oncaphillis wrote: > On 05/18/2012 11:23 PM, Dan Williams wrote: > > On Thu, 2012-05-17 at 09:58 +0200, Oncaphillis wrote: > >> Hi, > >> > >>I'm using Fedora16 and I'm trying to set up NetworkManager to connect > >> to a wlan on startup via /etc/sysconfig/network-scrip/ifcfg-wlan0 or > >> /etc/sysconfig/network-scrip/ifcfg-. It seems the settings in > >> /etc/sysconfig/wpa_supplicant are ignored if wpa_supplicant is managed > >> by the NetworkManager,but I don't see any option to pass the -D > >> option to wpa_supplicant. > > > > Correct, the settings in /etc/sysconfig/wpa_supplicant can be harmful > > when NetworkManager is used, because NetworkManager figures out whether > > to use the wext, nl80211, or wired driver as appropriate. What's the > > reason you want to use a specific supplicant driver? > > > > Dan > > > > Simply the observation that wpa_supplicant fails to associate when > not using -Dwext What wifi kernel driver? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ifcfg-rh and wpa_supplicant
On 05/18/2012 11:23 PM, Dan Williams wrote: On Thu, 2012-05-17 at 09:58 +0200, Oncaphillis wrote: Hi, I'm using Fedora16 and I'm trying to set up NetworkManager to connect to a wlan on startup via /etc/sysconfig/network-scrip/ifcfg-wlan0 or /etc/sysconfig/network-scrip/ifcfg-. It seems the settings in /etc/sysconfig/wpa_supplicant are ignored if wpa_supplicant is managed by the NetworkManager,but I don't see any option to pass the -D option to wpa_supplicant. Correct, the settings in /etc/sysconfig/wpa_supplicant can be harmful when NetworkManager is used, because NetworkManager figures out whether to use the wext, nl80211, or wired driver as appropriate. What's the reason you want to use a specific supplicant driver? Dan Simply the observation that wpa_supplicant fails to associate when not using -Dwext Thanks O. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ifcfg-rh and wpa_supplicant
On Thu, 2012-05-17 at 09:58 +0200, Oncaphillis wrote: > Hi, > > I'm using Fedora16 and I'm trying to set up NetworkManager to connect > to a wlan on startup via /etc/sysconfig/network-scrip/ifcfg-wlan0 or > /etc/sysconfig/network-scrip/ifcfg-. It seems the settings in > /etc/sysconfig/wpa_supplicant are ignored if wpa_supplicant is managed > by the NetworkManager,but I don't see any option to pass the -D > option to wpa_supplicant. Correct, the settings in /etc/sysconfig/wpa_supplicant can be harmful when NetworkManager is used, because NetworkManager figures out whether to use the wext, nl80211, or wired driver as appropriate. What's the reason you want to use a specific supplicant driver? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Debian testing + MM 0.5.2 + Huawei
Hi, I upgraded my debian based system (antix) today and I got MM 0.5.2 . My problem, seems modemmanager has issue with this modem, because it "restart" over and over again and cannot identify modem. Details: Bus 001 Device 002: ID 12d1:1c05 Huawei Technologies Co., Ltd. E173s 3G broadband stick (modem on) Modemmanager output (debug log, this part repeating again and again, continuously): [main.c:167] main(): ModemManager (version 0.5.2.0) starting... [mm-manager.c:120] load_plugin(): Loaded plugin MotoC [mm-manager.c:120] load_plugin(): Loaded plugin ZTE [mm-manager.c:120] load_plugin(): Loaded plugin Gobi [mm-manager.c:120] load_plugin(): Loaded plugin SimTech [mm-manager.c:120] load_plugin(): Loaded plugin Option High-Speed [mm-manager.c:120] load_plugin(): Loaded plugin Huawei [mm-manager.c:120] load_plugin(): Loaded plugin AnyData [mm-manager.c:120] load_plugin(): Loaded plugin Sierra [mm-manager.c:120] load_plugin(): Loaded plugin Nokia [mm-manager.c:120] load_plugin(): Loaded plugin Option [mm-manager.c:120] load_plugin(): Loaded plugin Samsung [mm-manager.c:120] load_plugin(): Loaded plugin Ericsson MBM [mm-manager.c:120] load_plugin(): Loaded plugin X22X [mm-manager.c:120] load_plugin(): Loaded plugin Generic [mm-manager.c:120] load_plugin(): Loaded plugin Linktop [mm-manager.c:120] load_plugin(): Loaded plugin Wavecom [mm-manager.c:120] load_plugin(): Loaded plugin Cinterion [mm-manager.c:120] load_plugin(): Loaded plugin Novatel [mm-manager.c:120] load_plugin(): Loaded plugin Longcheer [mm-manager.c:491] try_supports_port(): (Huawei): (ttyUSB1) deferring support check [mm-manager.c:491] try_supports_port(): (Huawei): (ttyUSB2) deferring support check [mm-manager.c:809] device_added(): (tty/ttyS0): port's parent platform driver is not whitelisted [mm-manager.c:809] device_added(): (tty/ttyS1): port's parent platform driver is not whitelisted [mm-manager.c:809] device_added(): (tty/ttyS2): port's parent platform driver is not whitelisted [mm-manager.c:809] device_added(): (tty/ttyS3): port's parent platform driver is not whitelisted [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB0) opening serial port... [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 1 (open) [mm-plugin-base.c:859] try_open(): (ttyUSB0): probe requested by plugin 'Huawei' [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GCAP' [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): +GCAP: +CGSM,+DS,+ESOK' [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 0 (close) [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB0) closing serial port... [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB0) serial port closed [main.c:167] main(): ModemManager (version 0.5.2.0) starting... [mm-manager.c:120] load_plugin(): Loaded plugin MotoC. /var/log/messages May 18 22:12:55 localhost kernel: [ 4.094733] usbcore: registered new interface driver usbserial May 18 22:12:55 localhost kernel: [ 4.094892] USB Serial support registered for generic May 18 22:12:55 localhost kernel: [ 4.095148] usbcore: registered new interface driver usbserial_generic May 18 22:12:55 localhost kernel: [ 4.095236] usbserial: USB Serial Driver core May 18 22:12:55 localhost kernel: [ 4.178926] USB Serial support registered for GSM modem (1-port) May 18 22:12:55 localhost kernel: [ 4.179251] option 1-2:1.0: GSM modem (1-port) converter detected May 18 22:12:55 localhost kernel: [ 4.244635] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0 May 18 22:12:55 localhost kernel: [ 4.244850] option 1-2:1.1: GSM modem (1-port) converter detected May 18 22:12:55 localhost kernel: [ 4.245289] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1 May 18 22:12:55 localhost kernel: [ 4.245468] option 1-2:1.2: GSM modem (1-port) converter detected May 18 22:12:55 localhost kernel: [ 4.247837] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2 May 18 22:12:55 localhost kernel: [ 4.248400] usbcore: registered new interface driver option May 18 22:12:55 localhost kernel: [ 4.248501] option: v0.7.2:USB Driver for GSM modems nmcli root@debian :~# nmcli dev ESZKÖZ TÍPUS ÁLLAPOT eth0 802-3-ethernet unmanaged root@debian :~# nmcli nm root@debian :~# nmcli nm FUT ÁLLAPOT WIFI-HARDVER WIFI WWAN-HARDVER WWAN run unattached enabled enabled enabld disabled cannot enable wwan, nothing happens for nmcli nm wwan on Any idea what to check? Thank you, István ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager IPv6 support
Hello, I'm afraid I have not yet introduced in the list. My name is Pavel Šimerda, I recently joined Red Hat and I'm currently working on NetworkManager's IPv6 support. I've already made some changes but I don't have yet access to the Git repository. For now you can see my changes at: http://git.pavlix.net/gitweb/?p=NetworkManager.git;a=summary Most of the changes are just cleaning up, removing unnecessary stuff, improving logging, you can see yourself. I don't know about any regressions right now. If you are curious, you can also see a short summary of basic scenarios that should work in NetworkManager and which of them actually work: https://fedoraproject.org/wiki/Tools/NetworkManager/IPv6 But note that these are very simple scenarios and I'm currently only testing by restarting the whole NetworkManager. Thanks to Dan Winship for providing help with getting into the code and to Jirka Klimes for helping me with my beginnings. Cheers, Pavel Simerda ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mm_serial_port_queue_process: (ttyUSB2) response array is not empty.....
>> May 18 07:53:52 localhost modem-manager[1998]: >> mm_serial_port_queue_process: (ttyUSB2) response array is not empty >> when >> usingcached reply, cleaning up 13 bytes >> >> >> What does it mean? I did not find any useful on the net. >> > > It means that array used to store the responses wasn't empty when an AT > command was requested and a previously cached reply used instead of > firing the new command. Whenever an AT command is sent, we expect the > response array to be empty; if it is not, it may be a leftover (e.g. > previously sent command timed out and response arrived afterwards), or > maybe some unexpected unsolicited indication not properly parsed. > > Could you get debug logs to see exactly where this is happening? > > -- > Aleksander > Hi Aleksander, Thank you for the info, ok, I try to collect debug data and send to here for analyzing. Bye now, István ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mm_serial_port_queue_process: (ttyUSB2) response array is not empty.....
> > I found this in my logs, a huge amount: > > May 18 07:52:40 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 26 bytes > May 18 07:52:56 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 26 bytes > May 18 07:53:08 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 13 bytes > May 18 07:53:13 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 26 bytes > May 18 07:53:19 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 13 bytes > May 18 07:53:24 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 13 bytes > May 18 07:53:30 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 26 bytes > May 18 07:53:41 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > using cached reply, cleaning up 65 bytes > May 18 07:53:52 localhost modem-manager[1998]: > mm_serial_port_queue_process: (ttyUSB2) response array is not empty when > usingcached reply, cleaning up 13 bytes > > > What does it mean? I did not find any useful on the net. > It means that array used to store the responses wasn't empty when an AT command was requested and a previously cached reply used instead of firing the new command. Whenever an AT command is sent, we expect the response array to be empty; if it is not, it may be a leftover (e.g. previously sent command timed out and response arrived afterwards), or maybe some unexpected unsolicited indication not properly parsed. Could you get debug logs to see exactly where this is happening? -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
mm_serial_port_queue_process: (ttyUSB2) response array is not empty.....
Hi, I found this in my logs, a huge amount: May 18 07:52:40 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 26 bytes May 18 07:52:56 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 26 bytes May 18 07:53:08 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 13 bytes May 18 07:53:13 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 26 bytes May 18 07:53:19 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 13 bytes May 18 07:53:24 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 13 bytes May 18 07:53:30 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 26 bytes May 18 07:53:41 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when using cached reply, cleaning up 65 bytes May 18 07:53:52 localhost modem-manager[1998]: mm_serial_port_queue_process: (ttyUSB2) response array is not empty when usingcached reply, cleaning up 13 bytes What does it mean? I did not find any useful on the net. Thank you, István ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet und PolicyKit: ** (nm-applet:8913): WARNING **: Failed to add/activate connection: (32) Insufficient privileges.
Dear Dan, thank you for your quick response. Am Donnerstag, den 17.05.2012, 13:08 -0500 schrieb Dan Williams: > On Thu, 2012-05-17 at 19:40 +0200, Paul Menzel wrote: > > when using nm-applet with an alternative window manager besides GNOME > > there seems to be a problem that `polkit-gnome-authentication-agent-1` > > is not started and therefore no new connections can be added [1][2]. > > > > Strangely > > > > /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop > > > > contains > > > > OnlyShowIn=GNOME;XFCE;Unity; > > > > so the PolicyKit “wrapper” is not started for other window managers or > > desktop environments than listed there. > > > > This has the effect, that nm-applet does not work fully. > > > > Besides that this problem should probably be fixed directly in > > PolicyKit, could nm-applet warn, if the PolicyKit stuff is not setup > > correctly, sot that the user has a clue what to look for. Currently only > > the following message is displayed in a box. > > Unfortunately we can't determine from PK whether an authorization agent > is registered or not. That sounds strange. From my noob perspective there should be a way to query if an agent is running or not. But I do not know about PolicyKit and authorization agents either. > But what we could do is update the error message to possibly point out > that either you couldn't authenticate yourself, or no PK > authentication agent was available. Yeah. That would be a good idea. Could you cook up a patch or would it just be elaborating the error message? Then I could do that. > > Failed to add/activate connection: (32) Insufficient privileges. > > > > Lastly, or am I mistaken and other window manager can provide a > > PolicyKit alternative so they should not rely on > > `polkit-gnome-authentication-agent-1.desktop`? > > Each DE can provide their own. KDE provides one, GNOME provides one, > and other DEs can use the one you show here or create their own. It looks like quite a hassle to list *every* desktop environment in that whitelist. Even if it is only needed when certain applications or applets or started. > Basically, if you've built NM with PolicyKit support, then it depends on > PolicyKit being set up correctly, of course. Of course. But a way to verify this would be even better. ;-) Thanks, Paul signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
