
You do have an Access point, right?
No I am trying to do Ad-Hoc using 2 Wireless cards. Almost there! Bill __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Bill Rosoman wrote:
You do have an Access point, right?
No I am trying to do Ad-Hoc using 2 Wireless cards.
"Probably something blinding simply. Have spent weeks Googling, Wardriving etc but can only so far see APs not log on." You're going to have to be clearer when you ask for help then. Can you please explain the setup of your network? if you want people to help you, you really have to be clear about what it is your doing. This whole time I've been under the assumption you're using an AP, based on your comment that I quoted above. Also, if you have both a wired *and* a wireless interface in each machine, they should both have different ip addresses in different subnets. This is important. Give your wired interfaces IPs in the 192.168.0.0/255.255.255.0 range, and give the wireless interfaces IPs in the 192.168.1.0/255.255.255.0 range.

Also, if you have both a wired *and* a wireless interface in each machine, they should both have different ip >addresses in different subnets. This is important.
Give your wired interfaces IPs in the 192.168.0.0/255.255.255.0 range, and give the wireless interfaces IPs in >the 192.168.1.0/255.255.255.0 range.
I believe daniel has hit the nail on the head here, I may be wrong (feel free to correct me if I am) but from the routing table, and from the rest of the dialog it appears that your laptop is trying to route packets to your network via the wired interface instaed of the wireless. I believe ths could be solved with some creative scripting or magic somewhere and i am probably not the person to solve the problem but hopefully this insight may catch the attention of someone who can help with the specifics.

--- Jason Drake <jase_d(a)ihug.co.nz> wrote:
Also, if you have both a wired *and* a wireless interface in each machine, they should both have different ip addresses in different subnets. This is important.
Give your wired interfaces IPs in the 192.168.0.0/255.255.255.0 range, and give the wireless interfaces IPs in >the 192.168.1.0/255.255.255.0 range.
Sounds logical to me "know", I sort of assumed that LAN WLAN used the same IP range, will try and let you know. Thanks Bill _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

Ok almost there now Tried the following; ifdown eth1 iwconfig eth1 mode Ad-Hoc essid "deb1" channel 6 ifconfig eth1 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255 ping 192.168.1.1 route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.3 0.0.0.0 255.255.255.255 UH 1 0 0 sl0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1 0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 0 sl0 Windows Wifi is Zyair B220 looks like only 802b Maybe part of problem as Netgear is 802b 802g LAN is 192.168.0.1 Wlan is 192.168.1.1 ping 192.168.1.1 still hangs! Almost humming! Ethereal does DHCP then shows UDP + ICMP + ARP and some TCP packets Ethereal correctly identifies all the wifi devices, computers, workgroup, and names of workgroup correctly When I ping Ethereal says it is sending mostly ICMP Packets So 99% there just cannot ping, though Ethereal shows it is trying hard. Also for the first time airsnort sees the windows wifi device OK Bill _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
participants (3)
-
Bill Rosoman
-
Daniel Lawson
-
Jason Drake