Invitation to connect on LinkedIn
LinkedIn Sanjeev Sharma requested to add you as a connection on LinkedIn: -- Trey, I'd like to add you to my professional network on LinkedIn. - Sanjeev Accept invitation from Sanjeev Sharma http://www.linkedin.com/e/UhWALb2cmzSf_dT_CirVab2MoQS4NOgDnhS8UdbL8q6T/blk/I2112291098_2/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYOnPwVc34Vcz8Ncj99bPdnq6hctmphbPkVdzARdPgTcP4LrCBxbOYWrSlI/EML_comm_afe/ View invitation from Sanjeev Sharma http://www.linkedin.com/e/UhWALb2cmzSf_dT_CirVab2MoQS4NOgDnhS8UdbL8q6T/blk/I2112291098_2/39ve3AMcjAOcz4NcAALqnpPbOYWrSlI/svi/ -- (c) 2010, LinkedIn Corporation___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Best Connection for wifi
Hi all, Does the NM always connected to the last connected AP in case of system Reboot.? For example Network Manager discovers three APs. one of those APs do not have auto-connect profiles in Network Manager, so Network Manager would never auto-connect to them. However, two of the APs do have auto-connect profiles.Then on which basis NM find out best connection out of two connection which has auto-connect profiles. Does it differentiate on basis of signal strength or on the basis of last connected AP. These Scenario i have been trying on Fedora 9 system. Sanjeev ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Unable to Auto Connect with Hidden Wireless Network automatically first time.
Hi All, I have problem in Auto connecting With my Hidden Wireless first time when I configured through "Connect to Hidden Wireless Network" . Step to Reproduce. 1:Connect to Hidden SSID through "Connect to Hidden Wireless Network." first time after reboot. 2:Unchecked Enable NetworkIng option. 3:Hidden SSID which was connected earlier will not "Auto Connect". 4:If i will repeat step 1 to 3 again it will start Auto Connecting. So First time it doesn't get Best auto Connection and fails while Auto Connect. One more thing What I observed that while trying First Connection It goes into nm_ap_check_compatible() function inside NetworkManagerAp.c and returning from these condition because ssid data is NULL. if (!nm_utils_same_ssid (nm_setting_wireless_get_ssid (s_wireless), priv->ssid, TRUE)) return FALSE; and on subsequent operation it doesn't get SSID NULL and above function doesn't return and connected successfully. So How we can resolve this issue and why first time it gets SSID NULL. Any help would be appreciable. Sanjeev ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager crashes when rf kill switch is Activated.
Hi All, I have called emit_error_helper() function Inside nm_supplicant_interface_add_cb() function in nm-supplicant-interface.c to avoid segfault in Networkmanger.This i have been calling when i will get following error messages. if Unexpected supplicant error getting interface: wpa_supplicant couldn't grab this interface. Does it work because same function has been called in some other different place in case of failure from supplicant. On Tue, Jun 16, 2009 at 5:28 PM, sanjeev sharma wrote: > -- Forwarded message -- > From: sanjeev sharma > Date: Mon, Jun 15, 2009 at 5:47 PM > Subject: Re: Network Manager crashes when rf kill switch is Activated. > To: Dan Williams > > > Hi Dan, > > I have called emit_error_helper() function Inside > nm_supplicant_interface_add_cb() function in nm-supplicant-interface.c > to avoid segfault in Networkmanger.This i have been calling when i > will get following error messages. > if Unexpected supplicant error getting interface: wpa_supplicant > couldn't grab this interface. > > Does it work because same function has been called in some other > different place in case of failure from supplicant. > > sanjeev > > > On Wed, Jun 10, 2009 at 4:00 PM, sanjeev > sharma wrote: >> Hi all, >> >> Find My Comments inline as follows. >> >> On Tue, Jun 9, 2009 at 9:19 PM, Dan Williams wrote: >>> On Tue, 2009-06-09 at 18:43 +0530, sanjeev sharma wrote: >>>> Hi All, >>>> >>>> I have been observing a crash of Network Manager when experimenting >>>> with the rf kill >>>> switch. I was trying to flip the >>>> switch before the previous switch state change had been fully processed by >>>> software. >>>> >>>> These are the log messages i have been seeing >>>> >>>> daemon.warn NetworkManager: nm_device_wifi_set_ssid(): error >>>> setting SSID to '(null)' for device eth0: Input/output error >>>> >>>> daemon.warn NetworkManager: wireless_get_range(): (eth0): >>>> couldn't get driver range information (5). >>>> >>>> daemon.warn NetworkManager: nm_supplicant_interface_add_cb(): >>>> Unexpected supplicant error getting interface: wpa_supplicant couldn't >>>> grab this interface. >>>> >>>> daemon.warn NetworkManager: nm_signal_handler(): Caught >>>> signal 11. Generating backtrace... >>> >>> Can you gdb NM and get a backtrace where it crashes? Obviously we're >>> not handling this case correctly, but it's a bit unclear exactly where >>> the error is unless there's a better backtrace. >>> >> This happens very rarely So gdb NM wouldn't be useful >> enough in this case. >> >>> The bits in question are in >>> src/supplicant-manager/nm-supplicant-interface.c. We may need to add a >>> signal to the supplicant interface object for something like "invalid", >>> so that we know to tear down the supplicant interface object in NM when >>> it cannot be added to the supplicant. >>> >> Does Current NetworkManager source code lead to segfault if supplicant >> will fail to add interface. >> Which section of networkManager code will handle this >> invalid Signal. >>> But it actually looks like we should just fix the bug itself, since the >>> rest of the code looks like it will handle re-configuring the interface >>> when the device un-kills itself. Need the backtrace for that though. >>> >> How to proceed further in case if gdb NM not possible. >> >> sanjeev >>> Dan >>> >>>> daemon.crit NetworkManager: *** START >>>> ** >>>> daemon.crit NetworkManager: Frame 0: [0xbeb20c4c] >>>> May 29 12:08:07 (none) daemon.crit NetworkManager: *** >>>> END ** >>>> >>>> >>>> would anybody through some pointer on it which causes segfault and how >>>> to prevent it. >>>> >>>> Sanjeev >>> >>> >> > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Fwd: Network Manager crashes when rf kill switch is Activated.
-- Forwarded message -- From: sanjeev sharma Date: Mon, Jun 15, 2009 at 5:47 PM Subject: Re: Network Manager crashes when rf kill switch is Activated. To: Dan Williams Hi Dan, I have called emit_error_helper() function Inside nm_supplicant_interface_add_cb() function in nm-supplicant-interface.c to avoid segfault in Networkmanger.This i have been calling when i will get following error messages. if Unexpected supplicant error getting interface: wpa_supplicant couldn't grab this interface. Does it work because same function has been called in some other different place in case of failure from supplicant. sanjeev On Wed, Jun 10, 2009 at 4:00 PM, sanjeev sharma wrote: > Hi all, > > Find My Comments inline as follows. > > On Tue, Jun 9, 2009 at 9:19 PM, Dan Williams wrote: >> On Tue, 2009-06-09 at 18:43 +0530, sanjeev sharma wrote: >>> Hi All, >>> >>> I have been observing a crash of Network Manager when experimenting >>> with the rf kill >>> switch. I was trying to flip the >>> switch before the previous switch state change had been fully processed by >>> software. >>> >>> These are the log messages i have been seeing >>> >>> daemon.warn NetworkManager: nm_device_wifi_set_ssid(): error >>> setting SSID to '(null)' for device eth0: Input/output error >>> >>> daemon.warn NetworkManager: wireless_get_range(): (eth0): >>> couldn't get driver range information (5). >>> >>> daemon.warn NetworkManager: nm_supplicant_interface_add_cb(): >>> Unexpected supplicant error getting interface: wpa_supplicant couldn't >>> grab this interface. >>> >>> daemon.warn NetworkManager: nm_signal_handler(): Caught >>> signal 11. Generating backtrace... >> >> Can you gdb NM and get a backtrace where it crashes? Obviously we're >> not handling this case correctly, but it's a bit unclear exactly where >> the error is unless there's a better backtrace. >> > This happens very rarely So gdb NM wouldn't be useful > enough in this case. > >> The bits in question are in >> src/supplicant-manager/nm-supplicant-interface.c. We may need to add a >> signal to the supplicant interface object for something like "invalid", >> so that we know to tear down the supplicant interface object in NM when >> it cannot be added to the supplicant. >> > Does Current NetworkManager source code lead to segfault if supplicant > will fail to add interface. > Which section of networkManager code will handle this > invalid Signal. >> But it actually looks like we should just fix the bug itself, since the >> rest of the code looks like it will handle re-configuring the interface >> when the device un-kills itself. Need the backtrace for that though. >> > How to proceed further in case if gdb NM not possible. > > sanjeev >> Dan >> >>> daemon.crit NetworkManager: *** START >>> ** >>> daemon.crit NetworkManager: Frame 0: [0xbeb20c4c] >>> May 29 12:08:07 (none) daemon.crit NetworkManager: *** >>> END ** >>> >>> >>> would anybody through some pointer on it which causes segfault and how >>> to prevent it. >>> >>> Sanjeev >> >> > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager crashes when rf kill switch is Activated.
Hi all, Find My Comments inline as follows. On Tue, Jun 9, 2009 at 9:19 PM, Dan Williams wrote: > On Tue, 2009-06-09 at 18:43 +0530, sanjeev sharma wrote: >> Hi All, >> >> I have been observing a crash of Network Manager when experimenting >> with the rf kill >> switch. I was trying to flip the >> switch before the previous switch state change had been fully processed by >> software. >> >> These are the log messages i have been seeing >> >> daemon.warn NetworkManager: nm_device_wifi_set_ssid(): error >> setting SSID to '(null)' for device eth0: Input/output error >> >> daemon.warn NetworkManager: wireless_get_range(): (eth0): >> couldn't get driver range information (5). >> >> daemon.warn NetworkManager: nm_supplicant_interface_add_cb(): >> Unexpected supplicant error getting interface: wpa_supplicant couldn't >> grab this interface. >> >> daemon.warn NetworkManager: nm_signal_handler(): Caught >> signal 11. Generating backtrace... > > Can you gdb NM and get a backtrace where it crashes? Obviously we're > not handling this case correctly, but it's a bit unclear exactly where > the error is unless there's a better backtrace. > This happens very rarely So gdb NM wouldn't be useful enough in this case. > The bits in question are in > src/supplicant-manager/nm-supplicant-interface.c. We may need to add a > signal to the supplicant interface object for something like "invalid", > so that we know to tear down the supplicant interface object in NM when > it cannot be added to the supplicant. > Does Current NetworkManager source code lead to segfault if supplicant will fail to add interface. Which section of networkManager code will handle this invalid Signal. > But it actually looks like we should just fix the bug itself, since the > rest of the code looks like it will handle re-configuring the interface > when the device un-kills itself. Need the backtrace for that though. > How to proceed further in case if gdb NM not possible. sanjeev > Dan > >> daemon.crit NetworkManager: *** START >> ** >> daemon.crit NetworkManager: Frame 0: [0xbeb20c4c] >> May 29 12:08:07 (none) daemon.crit NetworkManager: *** >> END ** >> >> >> would anybody through some pointer on it which causes segfault and how >> to prevent it. >> >> Sanjeev > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Network Manager crashes when rf kill switch is Activated.
Hi All, I have been observing a crash of Network Manager when experimenting with the rf kill switch. I was trying to flip the switch before the previous switch state change had been fully processed by software. These are the log messages i have been seeing daemon.warn NetworkManager: nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device eth0: Input/output error daemon.warn NetworkManager: wireless_get_range(): (eth0): couldn't get driver range information (5). daemon.warn NetworkManager: nm_supplicant_interface_add_cb(): Unexpected supplicant error getting interface: wpa_supplicant couldn't grab this interface. daemon.warn NetworkManager: nm_signal_handler(): Caught signal 11. Generating backtrace... daemon.crit NetworkManager: *** START ** daemon.crit NetworkManager: Frame 0: [0xbeb20c4c] May 29 12:08:07 (none) daemon.crit NetworkManager: *** END ** would anybody through some pointer on it which causes segfault and how to prevent it. Sanjeev ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Auto Connect through NetworkManager
Hi All, Is there any possibility to Disable "Auto Connect" through NetworkManager Code. in my Scenario If "Auto Connect" Is enabled In GSM Profile and User Click on Disconnect button then I wanted to Set "Auto Connect" flag disabled so networkManager won't retry to Start Connection again. I don't want to change "Auto Connect" manually through Connection editior because during resume my System has been checking mail and its will start Connection if only Auto Connect is set. Through some pointer on it. sanjeev sharma ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot reconnect to a VPN after cancelling or entering incorrect passwords
Hi, If it has been fixed for Network Manager then from Where I Could Download this release where this fixed is address from testing Purpose. Could I also test Vpnc Plugin where this Bug has been fixed. Thanks & Regards sanjeev sharma On Wed, Feb 4, 2009 at 10:39 PM, Dan Williams wrote: > On Wed, 2009-02-04 at 17:05 +0530, sanjeev sharma wrote: > > Hi, > > > > For VPN connection I am Using vpnc Plugin not OpenVpn Plugin. > > A bug causing this issue was fixed in NetworkManager (unfortunately > after the 0.7 release): > > commit 6bfade3227752f6565a3812238dee415b077b967 > Author: Dan Williams > Date: Mon Dec 8 15:24:38 2008 + > > It will be in NM 0.7.1. Furthermore, the vpnc plugin has been enhanced > to allow you to selectively save your user and group passwords, to > better support one-time-pad and token use-cases, or users who simply > want to enter their password in each time. > > Dan > > > > Regards > > sanjeev sharma > > > > > > On Wed, Feb 4, 2009 at 2:47 PM, Robert Vogelgesang > > wrote: > > Hello, > > > > On Wed, Feb 04, 2009 at 12:04:45PM +0530, sanjeev sharma > > wrote: > > > Hi All,Dan > > > > > > I have a VPN. When I connect to that VPN through > > NetworkManager, there is > > > a prompt dialog asking for Password and Group Password. If I > > enter passwords > > > correctly, it can connect just fine, but if I enter > > incorrect passwords or I > > > dont enter the passwords and close the dialog, from now on, > > I cannot connection > > > to the VPN any more witht the error message "The VPN > > connection 'XXX' failed > > > because the VPN service stopped unexpectedly" > > > > > > If I will Boot Up system a prompt dialog again ask for > > Password and > > > Group Password.The region > > > I think At first time it Save incorrect and correct > > Password for that session. > > > > > > Is this Network Manager Bug or Network Manager-vpnc plugin > > Bug.? > > > > > > VPNs using the Network Manager openvpn plugin share this > > problem, > > but only if the "Remember Password" box is checked. > > > >Robert > > > > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot reconnect to a VPN after cancelling or entering incorrect passwords
Hi, For VPN connection I am Using vpnc Plugin not OpenVpn Plugin. Regards sanjeev sharma On Wed, Feb 4, 2009 at 2:47 PM, Robert Vogelgesang < vo...@users.sourceforge.net> wrote: > Hello, > > On Wed, Feb 04, 2009 at 12:04:45PM +0530, sanjeev sharma wrote: > > Hi All,Dan > > > > I have a VPN. When I connect to that VPN through NetworkManager, there > is > > a prompt dialog asking for Password and Group Password. If I enter > passwords > > correctly, it can connect just fine, but if I enter incorrect passwords > or I > > dont enter the passwords and close the dialog, from now on, I cannot > connection > > to the VPN any more witht the error message "The VPN connection 'XXX' > failed > > because the VPN service stopped unexpectedly" > > > > If I will Boot Up system a prompt dialog again ask for Password and > > Group Password.The region > > I think At first time it Save incorrect and correct Password for that > session. > > > > Is this Network Manager Bug or Network Manager-vpnc plugin Bug.? > > VPNs using the Network Manager openvpn plugin share this problem, > but only if the "Remember Password" box is checked. > >Robert > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Cannot reconnect to a VPN after cancelling or entering incorrect passwords
Hi All,Dan I have a VPN. When I connect to that VPN through NetworkManager, there is a prompt dialog asking for Password and Group Password. If I enter passwords correctly, it can connect just fine, but if I enter incorrect passwords or I dont enter the passwords and close the dialog, from now on, I cannot connection to the VPN any more witht the error message "The VPN connection 'XXX' failed because the VPN service stopped unexpectedly" If I will Boot Up system a prompt dialog again ask for Password and Group Password.The region I think At first time it Save incorrect and correct Password for that session. Is this Network Manager Bug or Network Manager-vpnc plugin Bug.? What are the changes I need to Do If Each time i want to prompt Dialog asking for Password and group Password on My System if password enter my User is Correct or Incorrect each and every time. Which Module Would be Reponsible for this Behaviour change. Any Pointer On this Would be appreciable. Thanks & Regards sanjeev sharma ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless connection to "(none)"
Hi Dan, As we had Already Discussed this and I had Created an Patch for this Bug which is in NetworkManager.And you had a look into it earlier.Could I checked in this patch Into NetworkManager CVS.So We could Closed this Bug after checked in patch. Regards sanjeev sharma On Tue, Feb 3, 2009 at 10:02 PM, Dan Williams wrote: > On Sun, 2009-02-01 at 00:57 +0100, Ermanno Bonifazi wrote: > > Network manager shows in the tooltip to be connected to "(none)" > > network name, even if is connected to a specific Wireless LAN (e.g. > > WLAN) and is correctly working. > > In fact is I right click on connection information the name WLAN with > > the correct IP is shown. > > Any hint? > > What version of NetworkManager? When you see this bug, and you run > 'nm-tool', does a "*" show up next to the wifi network you should be > connected to? > > Dan > > ___ > 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
Patch review for connecting to a non-broadcasted SSID
Hi all,Hi Dan, I've noticed that when I successfully connect to a wireless network with a non-broadcasted SSID that the applet reports: "You are now connected to the wireless network '(none)'." So find Attached Patch which will resolve above mentioned Bug. Comments and review on this patch, Regards sanjeev sharma wifi_none.patch Description: Binary data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
connecting to a non-broadcasted SSID Patch review
Hi Dan, I've noticed that when I successfully connect to a wireless network with a non-broadcasted SSID that the applet reports: "You are now connected to the wireless network '(none)'." Clearly, NetworkManager knows the SSID of the network, since it was able to look for it, and successfully connect to it. But it appears that the applet can't determine it? For this Bug I have created an patch which will prompt the same SSID inside Nm-applet when SSID is non-broadcasted. This will Connect to Same SSID Which NetworkManager recognize at time of Connection. Review the Attached patch for NetworkManager bug.So I can Checked in the patch for this bug in open Source Community. Quick Response would be appreciable. Regards sanjeev sharma wifi_none.patch Description: Binary data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
networkmanger Svn 3973 Vpn
Hi all, i have checked out NetworkManager svn revision 3973 and found a VPN problem add vpn button is disabled.. i have gone through code in which i found that nm-vpn-properties is replaced by nm-connection editor... Hello folks could anybody would tell be what could be the region and VPN plugin path is same as earlier in /etc/NETWORKMANAGER/VPN.. Why this add button is disabled ?? Any pointer would be appreciated . Regards sanjeev sharma ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Automatic Bind configuration with VPN
Hi All, first of all let me thank you all for your great work in NetworkManager. i am evaluating NetworkManager and finds that there is no bind configuration of wlan,wwan with Vpn in NetworkManager0.7. i want Ability to associate a VPN with a WiFi SSID, WWAN profile, such that when we get a connection to that SSID (or to the WWAN), the VPN connection is brought up automatically. Let me elaborate in details. For example i am connected to one Wifi SSID and created a vpn connection for that Particular wifi SSID and if i am switching to another wifi or WAN Profile and created another Vpn with that Wifi SSID. then if i am switching back to previous Wifi associated VPN should be started Automatically and same case for 2nd connection.So there could be multiple connections. Please suggest where i can put checks in code to make this working. Any help would be appreciated. Thanks & Regards sanjeev sharma ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
networkmanger .7.0
Hi all, i am trying to build and test nm .7.0 on ubuntu version 7.10. on x86 Arch. Can anyone give me some inputs about configuration and dependencies when trying to do so? What do I specify for --with-distro in configuration? Thanks & Regards sanjeev sharma ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
