Re: Adhoc Connection

Pavel Roskin <[email protected]> Wed, 24 Mar 2010 17:56:09 -0400
Newsgroups gmane.linux.drivers.madwifi.user
Message-ID <1269467769.26368.36.camel@mj>
On Wed, 2010-03-24 at 23:36 +0200, Mohammad Abdelhadi wrote:

>   wlanconfig ath0 destroy
>   wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
>   iwconfig ath0 mode ad-hoc
>   iwconfig ath0 essid 'name'
> iwconfig ath0 channel 2
> ifconfig ath0 up
> dhclient ath0 (didn't work so I set up an IP address)

Don't run dhclient, it can stay in memory and do something you don't
know about.

> ifconfig ath0 'IP Address'
> 
> 
> Did I forget something?
> 
> 
> - then when I used (iwconfig) every thing was in its right place
> (essid, channel, adhoc mode, cell number).
> - when I used (iwlist) the two cards reported the information well,
> except one of them couldn't give the essid ( it shows an empty essid;
> ESSID=' ')!!!

I don't know if that's a problem.  It might be.

> - Ping hasn't worked well yet.

You mean it works somehow?

> - I used (iptables), and it seems that there is no firewall rules.
> 
> 
> Any comments or further suggestions?

Try tshark or tcpdump on both interfaces while running ping.

-- 
Regards,
Pavel Roskin

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev