Arch Linux

hypn0tic

Member

Registered: 2011-04-16

Posts: 10

Cannot get connected to a ad-hoc network. (Connected but not surfing)

I've read several post about similar topics and was able to connect to my phones ad-hoc tether via CLI, unfortunatly I can't seem to surf about then interwebs.

ifconfig wlan0 down
iwconfig wlan0 mode ad-hoc essid <essid>
ifconfig wlan0 up
dhcpcd wlan0

gets me

dhcpcd[4832]: version 5.2.5 starting
dhcpcd[4832]: wlan0: rebinding lease of 192.168.2.103
dhcpcd[4832]: wlan0: acknowledged 192.168.2.103 from 192.168.2.254
dhcpcd[4832]: wlan0: checking for 192.168.2.103
dhcpcd[4832]: wlan0: leased 192.168.2.103 for 43200 seconds
dhcpcd[4832]: forked to background, child pid 4854

yet cant access webpages.

in netcfg I use this profile.

# All thanks to flammenwurfer in https://bbs.archlinux.org/viewtopic.php?id=66273
CONNECTION="wireless"
DESCRIPTION="Automatically generated profile"
INTERFACE=wlan0
HOSTNAME=hypn0tic
IP="dhcp"
DHCP_TIMEOUT=10
ESSID="HAV0K"
SECURITY="NONE"
KEY=""
SCAN="NO"
TIMEOUT=15
PRE_UP="ifconfig wlan0 down; iwconfig wlan0 mode ad-hoc; iwconfig wlan0 essid HAV0K; ifconfig wlan0 up; dhcpcd wlan0"

which gets me a slightly different output (and no connection...or what I at least thought was a connection)

hypn0tic@Z10N ~ :) $netcfg phone
:: phone up                                                              [BUSY] dhcpcd[8727]: version 5.2.5 starting
dhcpcd[8727]: wlan0: rebinding lease of 192.168.1.66
dhcpcd[8727]: wlan0: NAK: wrong network from 192.168.2.254
dhcpcd[8727]: wlan0: broadcasting for a lease
dhcpcd[8727]: wlan0: offered 192.168.2.103 from 192.168.2.254
dhcpcd[8727]: wlan0: acknowledged 192.168.2.103 from 192.168.2.254
dhcpcd[8727]: wlan0: checking for 192.168.2.103
dhcpcd[8727]: wlan0: leased 192.168.2.103 for 43200 seconds
dhcpcd[8727]: forked to background, child pid 8791
 > Invalid SECURITY setting: NONE 
ioctl[SIOCSIWPMKSA]: Invalid argument
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
 > WPA Authentication/Association Failed 

I didn't know that "NONE" was a invalid security setting....I went and poked around in wpa_supplicant and found a bit to do with ad-hoc towards the bottom but honestly didn't want to mess with anything until I ran it by some people as if I lose the ability to connect to even my home network that would be a mess. (networking is not my forte )

My phone has no encryption enabled..so i'm not entirely sure where I should continue from here....any suggestions?

shoehorn

Member

Registered: 2011-04-15

Posts: 1

Re: Cannot get connected to a ad-hoc network. (Connected but not surfing)

I didn't know that "NONE" was a invalid security setting...

Perhaps it's lower case instead:

   

SECURITY='none'

just noticed it in the example netcfg file:

 

/etc/network.d/examples/wireless-open

Also, you're getting a IP address lease off of 192.168.2.254, so if that's your phone, you'll want to check it's sending you the right DNS and gateway settings. Try using the 'dig' command to check if anything resolves, and have a look in /etc/resolv.conf to see if the right DNS server IP is there...or use Googles

If that's ok check

route -n

for the right routing table gateway for destination 0.0.0.0 (the gateway is your phones IP)

Tethering via phone wifi, should be no different than any other hotspot... in theory

Last edited by shoehorn (2011-04-22 07:44:22)

hypn0tic

Member

Registered: 2011-04-16

Posts: 10

Re: Cannot get connected to a ad-hoc network. (Connected but not surfing)

I didn't know that "NONE" was a invalid security setting...

Perhaps it's lower case instead:

   

SECURITY='none'

just noticed it in the example netcfg file:

 

/etc/network.d/examples/wireless-open

Also, you're getting a IP address lease off of 192.168.2.254, so if that's your phone, you'll want to check it's sending you the right DNS and gateway settings. Try using the 'dig' command to check if anything resolves, and have a look in /etc/resolv.conf to see if the right DNS server IP is there...or use Googles

If that's ok check

route -n

for the right routing table gateway for destination 0.0.0.0 (the gateway is your phones IP)

Tethering via phone wifi, should be no different than any other hotspot... in theory

WOW...So I literally spent a good 20 minutes typing out results from various things to come to the realization that i'm retarded.

Thank you very much for you're post.
I was using a app called "wireless tether for root users" and somehow I enabled the access control (or someone I let play with my phone)

So I granted my computer access and whamo - right as rain.

(although it wasn't until I changed NONE to it's lower case brother that I started to receive push notifications...so, much thanks)

moral of the story - if you are using this app and can't seem to connect. Don't be a moron and post without checking your access control in your app

Last edited by hypn0tic (2011-04-22 08:32:25)