Re: force connect to hidden wireless network
Dan Ritter wrote: > In my experience, wicd does a better job than NetworkManager > with this sort of thing. http://wicd.sourceforge.net/ Looks promising. Unfortunately the Ubuntu package for it conflicts with Network Manager, and wicd doesn't support VPNs. Perhaps it can be force installed, as long as you are careful to make sure NM is configured not to manage the wireless interface. And I'm sure the VPN could be managed without the GUI. But I'm not sure either option is worth it just to have a WLAN that connects faster. I'll bookmark wicd and check back after they've released the 2.0 version that will support VPNs. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/ ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: force connect to hidden wireless network
On Thu, Feb 03, 2011 at 07:41:19PM -0500, Tom Metro wrote: > Jerry Feldman wrote: > > iwconfig wlan0 essid "my ssid" > > Most of the time, setting this allowed network manager to connect. > > I tried that in rc.local, and it didn't seem to help., Maybe my > assumption that rc.local runs well before X starts is incorrect. > > I've had a bit better luck with: > > # force set ESSID so hidden WLAN is found > iwconfig wlan0 essid $SSID > until iwlist wlan0 scan | fgrep -q ESSID:\"$SSID\" ; do > sleep 2; > done > echo "Wireless connection established to $SSID WLAN" > > > I don't know what impact "iwconfig wlan0 essid" has when you are in a > foreign location seeking to connect to any available WLAN, but I know my > solution won't handle that well, so I'd like to find a better solution. In my experience, wicd does a better job than NetworkManager with this sort of thing. -dsr- -- http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference. You can't defend freedom by getting rid of it. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: force connect to hidden wireless network
Jerry Feldman wrote: > iwconfig wlan0 essid "my ssid" > Most of the time, setting this allowed network manager to connect. I tried that in rc.local, and it didn't seem to help., Maybe my assumption that rc.local runs well before X starts is incorrect. I've had a bit better luck with: # force set ESSID so hidden WLAN is found iwconfig wlan0 essid $SSID until iwlist wlan0 scan | fgrep -q ESSID:\"$SSID\" ; do sleep 2; done echo "Wireless connection established to $SSID WLAN" I don't know what impact "iwconfig wlan0 essid" has when you are in a foreign location seeking to connect to any available WLAN, but I know my solution won't handle that well, so I'd like to find a better solution. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/ ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: force connect to hidden wireless network
On 01/26/2011 05:30 PM, Tom Metro wrote: > On my Ubuntu desktop I have it configured to automatically connect to my > wireless network, and I have the "Available to all users" option checked > in Network Manager so the connection gets established before I login to > GNOME. > > However, it seems to go through periods where it will fail to connect > prior to X login, and even then it doesn't list my WLAN as an available > network. I'm assuming this is because it is a "hidden" network and it > takes it a while to catch a packet with the SSID. > > At the last BLU meeting I believe I heard Jerry say something about > using iwconfig to set the ESSID. Is that correct, and if so what are the > specifics? > > Also, in my version of Network Manager, if I use the "Connect to hidden > wireless network" option, and then select my WLAN profile in the dialog, > it has all the input fields disabled, including the Connect button, so I > can't force a connection, short of creating a new profile. I'm guessing > this is a bug. > > -Tom > I had our company SSID hidden, and some times I had to use iwconfig. iwconfig wlan0 essid "my ssid" Most of the time, setting this allowed network manager to connect. I since changed the ssid to broadcast because of several discussions on this list. -- Jerry Feldman Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846 ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: force connect to hidden wireless network
On Wed, Jan 26, 2011 at 05:30:44PM -0500, Tom Metro wrote: > On my Ubuntu desktop I have it configured to automatically connect to my > wireless network, and I have the "Available to all users" option checked > in Network Manager so the connection gets established before I login to > GNOME. > > However, it seems to go through periods where it will fail to connect > prior to X login, and even then it doesn't list my WLAN as an available > network. I'm assuming this is because it is a "hidden" network and it > takes it a while to catch a packet with the SSID. > > At the last BLU meeting I believe I heard Jerry say something about > using iwconfig to set the ESSID. Is that correct, and if so what are the > specifics? iwconfig wlan0 essid "EssIDname" -dsr- -- http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference. You can't defend freedom by getting rid of it. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
force connect to hidden wireless network
On my Ubuntu desktop I have it configured to automatically connect to my wireless network, and I have the "Available to all users" option checked in Network Manager so the connection gets established before I login to GNOME. However, it seems to go through periods where it will fail to connect prior to X login, and even then it doesn't list my WLAN as an available network. I'm assuming this is because it is a "hidden" network and it takes it a while to catch a packet with the SSID. At the last BLU meeting I believe I heard Jerry say something about using iwconfig to set the ESSID. Is that correct, and if so what are the specifics? Also, in my version of Network Manager, if I use the "Connect to hidden wireless network" option, and then select my WLAN profile in the dialog, it has all the input fields disabled, including the Connect button, so I can't force a connection, short of creating a new profile. I'm guessing this is a bug. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/ ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
