gumstix

I had this same problem myself, try stopping the Network Manager with
"etc/init.d/NetworkManager stop" then set all the necessary settings.

ucbgumstix wrote:
> 
> Hi, I cannot connect my Overo Air (on a Summit expansion board) to a
> wireless network.  Here's what I've tried:
> -------------------------------------------------------------------------
> root@...:~# iwconfig            
> lo        no wireless extensions.
> 
> wlan0     IEEE 802.11b/g  ESSID:""  
>           Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated  
>           Bit Rate:0 kb/s   Tx-Power=13 dBm  
>           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B  
>           Encryption key:off
>           Power Management:off
>           Lnk0 vee    id:al  d   xcetva  earo~#
> root@...:~# iwconfig wlan0 essid any
> root@...:~# ifconfig wlan0 up
> root@...:~# iwlist wlan0 scan
> wlan0     Scan completed :
>           Cell 01 - Address: 00:23:04:89:CF:00
>                     ESSID:"EECS-Open"
>                     Mode:Managed
>                     Frequency:2.412 GHz (Channel 1)
>                     Quality=79/100  Signal level=-69 dBm  Noise level=-96
> dBm
>                     Encryption
>   it M/s 1 M       2 Mb/
> ...
> root@...:~# iwconfig wlan0 essid "EECS-Open"
> root@...:~# iwconfig
> lo        no wireless extensions.
> 
> wlan0     IEEE 802.11b/g  ESSID:""  
>           Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated  
>           Bit Rate:0 kb/s   Tx-Power=13 dBm  
>           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B  
>           Encryption key:off
>           Power Management:off
>           Llina Nl:  li Rcr ig:  sis: mis:0ov
> --------------------------------------------------------------------------------------------------
> ESSID is empty...  The fact that the Overo is able to scan for various
> wireless networks suggests to me that the WiFi module & antenna work. 
> I've tried connecting to different wireless networks using #iwconfig wlan0
> essid "name" where "name" is the name of the network, and I've tried
> "name" with double quotes, single quotes, no quotes - nothing has worked. 
> I can't connect to the network.
> 
> I have also tried setting up an ad-hoc network by editing
> /etc/network/interfaces:
> -----------------------------------------------------------
> auto wlan0
> iface wlan0 inet static
> address 192.168.2.2
> netmask 255.255.255.0
> wireless-mode ad-hoc
> wireless-essid gumstix-network
> -----------------------------------------------------------
> then:
> ------------------------------------------------------------
> root@...:~# ifconfig wlan0 down
> root@...:~# ifconfig wlan0 address 192.168.2.2 netmask 255.255.255.0
> address: Host name lookup failure
> ifconfig: `--help' gives usage information.
> root@...:~# iwconfig wlan0 mode ad-hoc essid gumstix-network
> root@...:~# ifconfig wlan0 up
> root@...:~# iwconfig
> lo        no wireless extensions.
> 
> wlan0     IEEE 802.11b/g  ESSID:""  
>           Mode:Ad-Hoc  Frequency:2.437 GHz  Cell: Not-Associated  
>           Bit Rate:0 kb/s   Tx-Power=13 dBm  
>           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B  
>           Encryption key:off
>           Power Management:off
>           Link Qualityna0 l:  liRx c iag  sss:d 46be
>                                                     r~#
> --------------------------------------------------------------------
> The mode changes to ad-hoc, but ESSID is again empty, and it doesn't
> connect to the network.  Also, my laptop doesn't see the newly created
> ad-hoc "gumstix-network" network.
> 
> Other things I've tried that I don't know if they are relevant or not, but
> that I thought I'd write - power cycling everything, using sudo before all
> commands - all without success.
> 
> Any help would be greatly appreciated - thanks! 
> 

-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29393545.html
Sent from the Gumstix mailing list archive at Nabble.com.

How do I set the settings?  What do I set them to?  I tried man
NetworkManager and NetworkManager --help, but couldn't figure it out. 
Sorry, I'm a bit new to all this wireless networking stuff.  Thanks.



chris2007 wrote:
> 
> I had this same problem myself, try stopping the Network Manager with
> "etc/init.d/NetworkManager stop" then set all the necessary settings.
> 
> 


-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29401262.html
Sent from the Gumstix mailing list archive at Nabble.com.

I would try reading through basic Linux networking commands thats what
helped me. but the command he gave you stops network manager then you
just have to do basically the steps you were trying before. And in
case you missed that command:
etc/init.d/NetworkManager stop
That goes into your command line and will stop it.

Also I personally had issues if I was trying to connect to the
internet through the console port on my overo fire/summit combo. Once
I either put on just a console image or booted normally through the
desktop image most if not all issues went away for me.

http://www.pixelbeat.org/cmdline.html  thats a linux cheat sheet you
might find useful. :) Hope that helps



On Tue, Aug 10, 2010 at 12:17 PM, ucbgumstix <itien08@...> wrote:
>
> How do I set the settings?  What do I set them to?  I tried man
> NetworkManager and NetworkManager --help, but couldn't figure it out.
> Sorry, I'm a bit new to all this wireless networking stuff.  Thanks.
>
>
>
> chris2007 wrote:
>>
>> I had this same problem myself, try stopping the Network Manager with
>> "etc/init.d/NetworkManager stop" then set all the necessary settings.
>>
>>
>
>
> --
> View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29401262.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

Also you did do and try all the listed steps in the wiki and user wiki right?



On Tue, Aug 10, 2010 at 12:34 PM, J. L. <vwyodapink@...> wrote:
> I would try reading through basic Linux networking commands thats what
> helped me. but the command he gave you stops network manager then you
> just have to do basically the steps you were trying before. And in
> case you missed that command:
> etc/init.d/NetworkManager stop
> That goes into your command line and will stop it.
>
> Also I personally had issues if I was trying to connect to the
> internet through the console port on my overo fire/summit combo. Once
> I either put on just a console image or booted normally through the
> desktop image most if not all issues went away for me.
>
> http://www.pixelbeat.org/cmdline.html  thats a linux cheat sheet you
> might find useful. :) Hope that helps
>
>
>
> On Tue, Aug 10, 2010 at 12:17 PM, ucbgumstix <itien08@...> wrote:
>>
>> How do I set the settings?  What do I set them to?  I tried man
>> NetworkManager and NetworkManager --help, but couldn't figure it out.
>> Sorry, I'm a bit new to all this wireless networking stuff.  Thanks.
>>
>>
>>
>> chris2007 wrote:
>>>
>>> I had this same problem myself, try stopping the Network Manager with
>>> "etc/init.d/NetworkManager stop" then set all the necessary settings.
>>>
>>>
>>
>>
>> --
>> View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29401262.html
>> Sent from the Gumstix mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>

Ok, open a terminal and type exactly what's inside the quotes to shut
down network manager, "etc/init.d/NetworkManager stop".
Now for an ad-hoc connection, you need to set the ip address
(192.168.2.2), netmask (255.255.255.0), and broadcast address
(192.168.2.255):
#ifconfig wlan0 192.168.2.2
#ifconfig wlan0 netmask 255.255.255.0 broadcast 192.168.2.255
After you've done that you need to set the wireless settings: mode,
channel, rate, power, txpower , and essid ( and in that order). Here's
an example.
#iwconfig wlan0 mode ad-hoc channel 11 rate 54Mb
(Make sure the channel and rate are the same for all devices you wish
to connect together in you ad-hoc network)
#iwconfig wlan0 power off
(power is for power management which doesn't work in ad-hoc mode)
#iwconfig wlan0 txpower 16dBm
(16dBm is full power)
#iwconfig wlan0 essid your_essid

And that should get you connected!

If you want to know how to make these settings more permanant so that
they are set on bootup just let me know.

On 8/10/10, ucbgumstix <itien08@...> wrote:
>
> How do I set the settings?  What do I set them to?  I tried man
> NetworkManager and NetworkManager --help, but couldn't figure it out.
> Sorry, I'm a bit new to all this wireless networking stuff.  Thanks.
>
>
>
> chris2007 wrote:
>>
>> I had this same problem myself, try stopping the Network Manager with
>> "etc/init.d/NetworkManager stop" then set all the necessary settings.
>>
>>
>
>
> --
> View this message in context:
> http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29401262.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

-- 
Sent from my mobile device

I thought power management on the onboard wifi was not adjustable ? I
get and error anytime I try and run the txpower command?

On Tue, Aug 10, 2010 at 1:05 PM, Chris Crews
<christopher.crews07@...> wrote:
> Ok, open a terminal and type exactly what's inside the quotes to shut
> down network manager, "etc/init.d/NetworkManager stop".
> Now for an ad-hoc connection, you need to set the ip address
> (192.168.2.2), netmask (255.255.255.0), and broadcast address
> (192.168.2.255):
> #ifconfig wlan0 192.168.2.2
> #ifconfig wlan0 netmask 255.255.255.0 broadcast 192.168.2.255
> After you've done that you need to set the wireless settings: mode,
> channel, rate, power, txpower , and essid ( and in that order). Here's
> an example.
> #iwconfig wlan0 mode ad-hoc channel 11 rate 54Mb
> (Make sure the channel and rate are the same for all devices you wish
> to connect together in you ad-hoc network)
> #iwconfig wlan0 power off
> (power is for power management which doesn't work in ad-hoc mode)
> #iwconfig wlan0 txpower 16dBm
> (16dBm is full power)
> #iwconfig wlan0 essid your_essid
>
> And that should get you connected!
>
> If you want to know how to make these settings more permanant so that
> they are set on bootup just let me know.
>
> On 8/10/10, ucbgumstix <itien08@...> wrote:
>>
>> How do I set the settings?  What do I set them to?  I tried man
>> NetworkManager and NetworkManager --help, but couldn't figure it out.
>> Sorry, I'm a bit new to all this wireless networking stuff.  Thanks.
>>
>>
>>
>> chris2007 wrote:
>>>
>>> I had this same problem myself, try stopping the Network Manager with
>>> "etc/init.d/NetworkManager stop" then set all the necessary settings.
>>>
>>>
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29401262.html
>> Sent from the Gumstix mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>
> --
> Sent from my mobile device
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

The power management works on my overo fire, but it doesn't work when
its in ad-hoc mode. Now I'm by far no expert but that's just personal
experience.

On 8/10/10, J. L. <vwyodapink@...> wrote:
> I thought power management on the onboard wifi was not adjustable ? I
> get and error anytime I try and run the txpower command?
>
> On Tue, Aug 10, 2010 at 1:05 PM, Chris Crews
> <christopher.crews07@...> wrote:
>> Ok, open a terminal and type exactly what's inside the quotes to shut
>> down network manager, "etc/init.d/NetworkManager stop".
>> Now for an ad-hoc connection, you need to set the ip address
>> (192.168.2.2), netmask (255.255.255.0), and broadcast address
>> (192.168.2.255):
>> #ifconfig wlan0 192.168.2.2
>> #ifconfig wlan0 netmask 255.255.255.0 broadcast 192.168.2.255
>> After you've done that you need to set the wireless settings: mode,
>> channel, rate, power, txpower , and essid ( and in that order). Here's
>> an example.
>> #iwconfig wlan0 mode ad-hoc channel 11 rate 54Mb
>> (Make sure the channel and rate are the same for all devices you wish
>> to connect together in you ad-hoc network)
>> #iwconfig wlan0 power off
>> (power is for power management which doesn't work in ad-hoc mode)
>> #iwconfig wlan0 txpower 16dBm
>> (16dBm is full power)
>> #iwconfig wlan0 essid your_essid
>>
>> And that should get you connected!
>>
>> If you want to know how to make these settings more permanant so that
>> they are set on bootup just let me know.
>>
>> On 8/10/10, ucbgumstix <itien08@...> wrote:
>>>
>>> How do I set the settings?  What do I set them to?  I tried man
>>> NetworkManager and NetworkManager --help, but couldn't figure it out.
>>> Sorry, I'm a bit new to all this wireless networking stuff.  Thanks.
>>>
>>>
>>>
>>> chris2007 wrote:
>>>>
>>>> I had this same problem myself, try stopping the Network Manager with
>>>> "etc/init.d/NetworkManager stop" then set all the necessary settings.
>>>>
>>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29401262.html
>>> Sent from the Gumstix mailing list archive at Nabble.com.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev
>>> _______________________________________________
>>> gumstix-users mailing list
>>> gumstix-users@...
>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>
>>
>> --
>> Sent from my mobile device
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

-- 
Sent from my mobile device

Okay, I tried all this, and this is what I get:
-------------------------------------------------------------------------------
root@...:~# /etc/init.d/NetworkManager stop
Stopping Network connection manager daemon: NetworkManager.
root@...:~# ifconfig wlan0 192.168.2.2
root@...:~# ifconfig wlan0 netmask 255.255.255.0 broadcast 192.168.255
root@...:~# iwconfig wlan0 mode ad-hoc channel 11 rate 54Mb
root@...:~# iwconfig wlan0 power off
root@...:~# iwconfig wlan0 txpower 16dBm
Error for wireless request "Set Tx Power" (8B26) :
    SET failed on device wlan0 ; Invalid argument.
root@...:~# iwconfig wlan0 essid my_network     
root@...:~# iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11b/g  ESSID:""  
          Mode:Ad-Hoc  Frequency:2.462 GHz  Cell: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power=13 dBm   
          Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B   
          Encryption key:3031-3233-3435-3637-3839-0000-00   Security
mode:open
    r :o  uana  el  li R c iag  sss:d Min:@o 
root@...:~# 
-------------------------------------------------------------------------
The ESSID field is still empty, so I'm not connected.  Got an error when
setting the txpower, but I don't think that's the main problem.  Any ideas
why it still can't connect?


chris2007 wrote:
> 
> Ok, open a terminal and type exactly what's inside the quotes to shut
> down network manager, "etc/init.d/NetworkManager stop".
> Now for an ad-hoc connection, you need to set the ip address
> (192.168.2.2), netmask (255.255.255.0), and broadcast address
> (192.168.2.255):
> #ifconfig wlan0 192.168.2.2
> #ifconfig wlan0 netmask 255.255.255.0 broadcast 192.168.2.255
> After you've done that you need to set the wireless settings: mode,
> channel, rate, power, txpower , and essid ( and in that order). Here's
> an example.
> #iwconfig wlan0 mode ad-hoc channel 11 rate 54Mb
> (Make sure the channel and rate are the same for all devices you wish
> to connect together in you ad-hoc network)
> #iwconfig wlan0 power off
> (power is for power management which doesn't work in ad-hoc mode)
> #iwconfig wlan0 txpower 16dBm
> (16dBm is full power)
> #iwconfig wlan0 essid your_essid
> 
> And that should get you connected!
> 
> If you want to know how to make these settings more permanant so that
> they are set on bootup just let me know.
> 
> 

-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29402047.html
Sent from the Gumstix mailing list archive at Nabble.com.

Ok, try this. Do all the same steps I gave you before but add these
in. After you set the ip, netmask, and broadcast do:
#ifconfig wlan0 down
Then just before you set your essid do:
#ifconfig wlan0 up
And see if that changes anything.

On 8/10/10, ucbgumstix <itien08@...> wrote:
>
> Okay, I tried all this, and this is what I get:
> -------------------------------------------------------------------------------
> root@...:~# /etc/init.d/NetworkManager stop
> Stopping Network connection manager daemon: NetworkManager.
> root@...:~# ifconfig wlan0 192.168.2.2
> root@...:~# ifconfig wlan0 netmask 255.255.255.0 broadcast 192.168.255
> root@...:~# iwconfig wlan0 mode ad-hoc channel 11 rate 54Mb
> root@...:~# iwconfig wlan0 power off
> root@...:~# iwconfig wlan0 txpower 16dBm
> Error for wireless request "Set Tx Power" (8B26) :
>     SET failed on device wlan0 ; Invalid argument.
> root@...:~# iwconfig wlan0 essid my_network
> root@...:~# iwconfig
> lo        no wireless extensions.
>
> wlan0     IEEE 802.11b/g  ESSID:""
>           Mode:Ad-Hoc  Frequency:2.462 GHz  Cell: Not-Associated
>           Bit Rate:0 kb/s   Tx-Power=13 dBm
>           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B
>           Encryption key:3031-3233-3435-3637-3839-0000-00   Security
> mode:open
>     r :o  uana  el  li R c iag  sss:d Min:@o
> root@...:~#
> -------------------------------------------------------------------------
> The ESSID field is still empty, so I'm not connected.  Got an error when
> setting the txpower, but I don't think that's the main problem.  Any ideas
> why it still can't connect?
>
>
> chris2007 wrote:
>>
>> Ok, open a terminal and type exactly what's inside the quotes to shut
>> down network manager, "etc/init.d/NetworkManager stop".
>> Now for an ad-hoc connection, you need to set the ip address
>> (192.168.2.2), netmask (255.255.255.0), and broadcast address
>> (192.168.2.255):
>> #ifconfig wlan0 192.168.2.2
>> #ifconfig wlan0 netmask 255.255.255.0 broadcast 192.168.2.255
>> After you've done that you need to set the wireless settings: mode,
>> channel, rate, power, txpower , and essid ( and in that order). Here's
>> an example.
>> #iwconfig wlan0 mode ad-hoc channel 11 rate 54Mb
>> (Make sure the channel and rate are the same for all devices you wish
>> to connect together in you ad-hoc network)
>> #iwconfig wlan0 power off
>> (power is for power management which doesn't work in ad-hoc mode)
>> #iwconfig wlan0 txpower 16dBm
>> (16dBm is full power)
>> #iwconfig wlan0 essid your_essid
>>
>> And that should get you connected!
>>
>> If you want to know how to make these settings more permanant so that
>> they are set on bootup just let me know.
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29402047.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

-- 
Sent from my mobile device

I think it's connected to the ad-hoc network!  But now I'm having trouble
getting an address (using dhclient):
------------------------------------------------------------------
root@...:~# iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11b/g  ESSID:"my_network"  
          Mode:Ad-Hoc  Frequency:2.462 GHz  Cell: 6E:65:74:77:6F:72   
          Bit Rate=54 Mb/s   Tx-Power=13 dBm   
          Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B   
          Encryption key:off
          Power Management:off
        al0 ve  l=  x idva0 id   ere  isMion@... 
root@...:~# dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.2p1
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

can't create /var/lib/dhcp/dhclient.leases: No such file or directory
Listening on LPF/wlan0/00:19:88:3d:11:8c
Sending on   LPF/wlan0/00:19:88:3d:11:8c
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
--------------------------------------------------------------------------------------------

In /var/lib I only have a folder called "dhcp3."  In the dhcp3 folder, there
was no file called dhclient.leases, so, looking at the "can't create
/var/lib/dhcp/dhclient.leases: No such file or directory" error, I tried
copying the dhclient.leases file from my Ubuntu laptop (on my laptop:
/var/lib/dhcp3/dhclient.leases) and created a folder in the Overo to copy
the file to (/var/lib/dhcp/dhclient.leases).  That "can't create" error goes
away, but still no DHCPOFFERS received:

------------------------------------------------------------------------------------------
root@...# dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.2p1
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:19:88:3d:11:8c
Sending on   LPF/wlan0/00:19:88:3d:11:8c
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
Trying recorded lease 192.168.1.43
PING 192.168.1.1 (192.168.1.1): 56 data bytes

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss
No working leases in persistent database - sleeping.
------------------------------------------------------------------------------------------

Also, how do I make the ad-hoc wireless network settings permanent on the
Overo so that they are set on bootup?  Is it something to do with editing
the /etc/network/interfaces file?  Thanks.



chris2007 wrote:
> 
> Ok, try this. Do all the same steps I gave you before but add these
> in. After you set the ip, netmask, and broadcast do:
> #ifconfig wlan0 down
> Then just before you set your essid do:
> #ifconfig wlan0 up
> And see if that changes anything.
> 
> 

-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29404168.html
Sent from the Gumstix mailing list archive at Nabble.com.

Well to begin with, an ad-hoc network is static ip only unless you have a
dhcp server in your network, in which case it wouldn't really be an ad-hoc
network now would it. Your not receiving any dhcp offers because there is no
dhcp server to send them out. If you where connecting to a home router in
managed mode you would receive a dhcp offer from the router's built-in dhcp
server. So, are you really wanting an ad-hoc network or a managed network
(connect to an access point or router)? Let me know which one it is and i
can help you to get it set on boot-up.

On Tue, Aug 10, 2010 at 9:39 PM, ucbgumstix <itien08@...> wrote:

>
> I think it's connected to the ad-hoc network!  But now I'm having trouble
> getting an address (using dhclient):
> ------------------------------------------------------------------
> root@...:~# iwconfig
> lo        no wireless extensions.
>
> wlan0     IEEE 802.11b/g  ESSID:"my_network"
>          Mode:Ad-Hoc  Frequency:2.462 GHz  Cell: 6E:65:74:77:6F:72
>          Bit Rate=54 Mb/s   Tx-Power=13 dBm
>           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B
>           Encryption key:off
>          Power Management:off
>        al0 ve  l=  x idva0 id   ere  isMion@...
> root@...:~# dhclient wlan0
> Internet Systems Consortium DHCP Client V3.1.2p1
> Copyright 2004-2009 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> can't create /var/lib/dhcp/dhclient.leases: No such file or directory
> Listening on LPF/wlan0/00:19:88:3d:11:8c
> Sending on   LPF/wlan0/00:19:88:3d:11:8c
> Sending on   Socket/fallback
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
>
> --------------------------------------------------------------------------------------------
>
> In /var/lib I only have a folder called "dhcp3."  In the dhcp3 folder,
> there
> was no file called dhclient.leases, so, looking at the "can't create
> /var/lib/dhcp/dhclient.leases: No such file or directory" error, I tried
> copying the dhclient.leases file from my Ubuntu laptop (on my laptop:
> /var/lib/dhcp3/dhclient.leases) and created a folder in the Overo to copy
> the file to (/var/lib/dhcp/dhclient.leases).  That "can't create" error
> goes
> away, but still no DHCPOFFERS received:
>
>
> ------------------------------------------------------------------------------------------
> root@...# dhclient wlan0
> Internet Systems Consortium DHCP Client V3.1.2p1
> Copyright 2004-2009 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> Listening on LPF/wlan0/00:19:88:3d:11:8c
> Sending on   LPF/wlan0/00:19:88:3d:11:8c
> Sending on   Socket/fallback
> DHCPREQUEST on wlan0 to 255.255.255.255 port 67
> DHCPREQUEST on wlan0 to 255.255.255.255 port 67
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
> No DHCPOFFERS received.
> Trying recorded lease 192.168.1.43
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
>
> --- 192.168.1.1 ping statistics ---
> 1 packets transmitted, 0 packets received, 100% packet loss
> No working leases in persistent database - sleeping.
>
> ------------------------------------------------------------------------------------------
>
> Also, how do I make the ad-hoc wireless network settings permanent on the
> Overo so that they are set on bootup?  Is it something to do with editing
> the /etc/network/interfaces file?  Thanks.
>
>
> --
> View this message in context:
> http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29404168.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

What I really want is two devices to be on the same network, be it ad-hoc or
managed, so that I can send data between the two over the network.


chris2007 wrote:
> 
> Well to begin with, an ad-hoc network is static ip only unless you have a
> dhcp server in your network, in which case it wouldn't really be an ad-hoc
> network now would it. Your not receiving any dhcp offers because there is
> no
> dhcp server to send them out. If you where connecting to a home router in
> managed mode you would receive a dhcp offer from the router's built-in
> dhcp
> server. So, are you really wanting an ad-hoc network or a managed network
> (connect to an access point or router)? Let me know which one it is and i
> can help you to get it set on boot-up.
> 
> 

-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29411270.html
Sent from the Gumstix mailing list archive at Nabble.com.

Then you want to setup each device as an ad-hoc if they are to only
connect to each other. And you will be good to go. Thats what I do
with my onboard WIFI on my fire its an ad-hoc to my groundstation to
send telemetry and some other info to the GS. Then I also have a USB
WIFI adapter that is doing other things.

On Wed, Aug 11, 2010 at 11:27 AM, ucbgumstix <itien08@...> wrote:
>
> What I really want is two devices to be on the same network, be it ad-hoc or
> managed, so that I can send data between the two over the network.
>
>
> chris2007 wrote:
>>
>> Well to begin with, an ad-hoc network is static ip only unless you have a
>> dhcp server in your network, in which case it wouldn't really be an ad-hoc
>> network now would it. Your not receiving any dhcp offers because there is
>> no
>> dhcp server to send them out. If you where connecting to a home router in
>> managed mode you would receive a dhcp offer from the router's built-in
>> dhcp
>> server. So, are you really wanting an ad-hoc network or a managed network
>> (connect to an access point or router)? Let me know which one it is and i
>> can help you to get it set on boot-up.
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29411270.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

Yes, that's exactly what I was thinking for an ad-hoc network.  My other
device is a Nokia N810.  So I want to set up the Nokia to connect to my
ad-hoc network, and I think I need to use the same commands as used to set
up the ad-hoc network on the Overo, but when I try the command iwconfig the
Nokia says "iwconfig: not found."  I tried "apt-get install wireless-tools"
but still no iwconfig in /bin or /sbin.

Also, tried just copying the iwconfig file from an Ubuntu laptop to the
Nokia /bin and /sbin folders.  But this is what I get when I try to use
iwconfig:
--------------------------------------------------
Nokia-N810-51-3:/# iwconfig
sh: iwconfig: Permission denied
Nokia-N810-51-3:/# sudo iwconfig
Nokia-N810-51-3:/# 
--------------------------------------------------
I don't get anything from iwconfig.  So, I'm at a loss as to how to set up
the ad-hoc network on the Nokia.  Any help would be greatly appreciated!


vwyodapink wrote:
> 
> Then you want to setup each device as an ad-hoc if they are to only
> connect to each other. And you will be good to go. Thats what I do
> with my onboard WIFI on my fire its an ad-hoc to my groundstation to
> send telemetry and some other info to the GS. Then I also have a USB
> WIFI adapter that is doing other things.
> 
> 

-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29413713.html
Sent from the Gumstix mailing list archive at Nabble.com.

I would start looking on google for your Nokia, seems as though there
are specific steps required for different situations and from my quick
reading the Nokia does not connect to all ad-hoc networks, and has
this issue for a bit. Also read its insanely power hungry in that mode
and most recomended avoiding it .



On Wed, Aug 11, 2010 at 3:54 PM, ucbgumstix <itien08@...> wrote:
>
> Yes, that's exactly what I was thinking for an ad-hoc network.  My other
> device is a Nokia N810.  So I want to set up the Nokia to connect to my
> ad-hoc network, and I think I need to use the same commands as used to set
> up the ad-hoc network on the Overo, but when I try the command iwconfig the
> Nokia says "iwconfig: not found."  I tried "apt-get install wireless-tools"
> but still no iwconfig in /bin or /sbin.
>
> Also, tried just copying the iwconfig file from an Ubuntu laptop to the
> Nokia /bin and /sbin folders.  But this is what I get when I try to use
> iwconfig:
> --------------------------------------------------
> Nokia-N810-51-3:/# iwconfig
> sh: iwconfig: Permission denied
> Nokia-N810-51-3:/# sudo iwconfig
> Nokia-N810-51-3:/#
> --------------------------------------------------
> I don't get anything from iwconfig.  So, I'm at a loss as to how to set up
> the ad-hoc network on the Nokia.  Any help would be greatly appreciated!
>
>
> vwyodapink wrote:
>>
>> Then you want to setup each device as an ad-hoc if they are to only
>> connect to each other. And you will be good to go. Thats what I do
>> with my onboard WIFI on my fire its an ad-hoc to my groundstation to
>> send telemetry and some other info to the GS. Then I also have a USB
>> WIFI adapter that is doing other things.
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29413713.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

Okay, I've decided to try the managed network (not ad-hoc network) route. 
I've got the Overo connected to an existing managed wireless network (I see
it from iwconfig).  But when I try to ping another device on the network, I
get:
------------------------------------------------------------------
root@...:~# ping 192.168.1.44
PING 192.168.1.44 (192.168.1.44): 56 data bytes
ping: sendto: Network is unreachable
root@...:~# 
root@...:~# ping google.com
ping: bad address 'google.com'
root@...:~# 
-------------------------------------------------------------------
I have tried pinging the 192.168.1.44 device using a laptop connected to the
same existing managed wireless network, and it works, so I don't think the
problem is with the network.  (also, pinging from the laptop to google.com
using the network works)  Is the Overo not actually connected to the
network?


chris2007 wrote:
> 
> Well to begin with, an ad-hoc network is static ip only unless you have a
> dhcp server in your network, in which case it wouldn't really be an ad-hoc
> network now would it. Your not receiving any dhcp offers because there is
> no
> dhcp server to send them out. If you where connecting to a home router in
> managed mode you would receive a dhcp offer from the router's built-in
> dhcp
> server. So, are you really wanting an ad-hoc network or a managed network
> (connect to an access point or router)? Let me know which one it is and i
> can help you to get it set on boot-up.
> 
> 

-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29414236.html
Sent from the Gumstix mailing list archive at Nabble.com.

you have gone through the listed steps to enable it properly correct?
Its in the user wiki I think. Also try editing your resolv.conf file



On Wed, Aug 11, 2010 at 5:27 PM, ucbgumstix <itien08@...> wrote:
>
> Okay, I've decided to try the managed network (not ad-hoc network) route.
> I've got the Overo connected to an existing managed wireless network (I see
> it from iwconfig).  But when I try to ping another device on the network, I
> get:
> ------------------------------------------------------------------
> root@...:~# ping 192.168.1.44
> PING 192.168.1.44 (192.168.1.44): 56 data bytes
> ping: sendto: Network is unreachable
> root@...:~#
> root@...:~# ping google.com
> ping: bad address 'google.com'
> root@...:~#
> -------------------------------------------------------------------
> I have tried pinging the 192.168.1.44 device using a laptop connected to the
> same existing managed wireless network, and it works, so I don't think the
> problem is with the network.  (also, pinging from the laptop to google.com
> using the network works)  Is the Overo not actually connected to the
> network?
>
>
> chris2007 wrote:
>>
>> Well to begin with, an ad-hoc network is static ip only unless you have a
>> dhcp server in your network, in which case it wouldn't really be an ad-hoc
>> network now would it. Your not receiving any dhcp offers because there is
>> no
>> dhcp server to send them out. If you where connecting to a home router in
>> managed mode you would receive a dhcp offer from the router's built-in
>> dhcp
>> server. So, are you really wanting an ad-hoc network or a managed network
>> (connect to an access point or router)? Let me know which one it is and i
>> can help you to get it set on boot-up.
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29414236.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

Actually, I think the problem is that I'm not getting an address - "dhclient
wlan0" doesn't give me anything.



vwyodapink wrote:
> 
> you have gone through the listed steps to enable it properly correct?
> Its in the user wiki I think. Also try editing your resolv.conf file
> 
> 
> On Wed, Aug 11, 2010 at 5:27 PM, ucbgumstix <itien08@...> wrote:
>>
>> Okay, I've decided to try the managed network (not ad-hoc network) route.
>> I've got the Overo connected to an existing managed wireless network (I
>> see
>> it from iwconfig).  But when I try to ping another device on the network,
>> I
>> get:
>> ------------------------------------------------------------------
>> root@...:~# ping 192.168.1.44
>> PING 192.168.1.44 (192.168.1.44): 56 data bytes
>> ping: sendto: Network is unreachable
>> root@...:~#
>> root@...:~# ping google.com
>> ping: bad address 'google.com'
>> root@...:~#
>> -------------------------------------------------------------------
>> I have tried pinging the 192.168.1.44 device using a laptop connected to
>> the
>> same existing managed wireless network, and it works, so I don't think
>> the
>> problem is with the network.  (also, pinging from the laptop to
>> google.com
>> using the network works)  Is the Overo not actually connected to the
>> network?
>>
> 

-- 
View this message in context: http://old.nabble.com/Overo-Air-cannot-connect-to-existing-wireless-network-or-ad-hoc-network-tp29393403p29414368.html
Sent from the Gumstix mailing list archive at Nabble.com.