On Sat, Jul 14, 2007 at 15:50:03 -0700, I M wrote: [...]
> Yes debian and windows are installed on the same PC using the same wireless > card(PC60g). > As for the MAC-filtering problem it's out of the question,because the AP > doesn't use it.:) > As for the cell01(channel6) it's exactly the one from wich i connect on > windows because it has > greater signal,but there are others(i think 2)also the same listed by "iwlist > ra0 scan" command. > Afer doing "iwconfig ra0 ap 00:05:9E:84:05:67" ,"iwconfig ra0" shows this : > ------------------> > ra0 RT61 Wireless ESSID:"" > Mode:Auto Frequency:2.412 GHz Bit Rate=54 Mb/s > RTS thr:off Fragment thr:off > Encryption key:off > Link Quality=0/100 Signal level:-121 dBm Noise level:-111 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > ------------------> > But i'm sure you wanted to mention this mac(00:05:9E:84:89:ED) because this > is the one wich showes some bit rates. > Doing the same thing shows up: > ------------------> > ra0 RT61 Wireless ESSID:"" > Mode:Auto Frequency:2.412 GHz Bit Rate=54 Mb/s > RTS thr:off Fragment thr:off > Encryption key:off > Link Quality=0/100 Signal level:-121 dBm Noise level:-111 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > ------------------> > To my opinion is not too much! I agree; it really seems to be a problem with the configuration of the rt61 driver (and not a problem with the DHCP client). Google turns up this thread on the Ubuntu forums: http://ubuntuforums.org/showthread.php?t=132980 Especially this post seems interesting: http://ubuntuforums.org/showpost.php?p=1310334&postcount=117 It suggests that you have to use "iwpriv" instead of "iwconfig" to configure this driver. That is probably worth a try. You have to reach a state in which "iwconfig ra0" reports "Mode: Managed", the correct ESSID and "Access Point: <mac address of access point>" > And here's th output of : > > -----------------> > ii dhcp 2.0pl5-19.5 > un dhcp-beta <none> > rc dhcp-client 2.0pl5-19.5 > un dhcp-client-beta <none> > rc dhcp-relay 2.0pl5-19.5 > un dhcp-relay-beta <none> > ii dhcp3-client 3.0.4-13 > ii dhcp3-common 3.0.4-13 > ii dhcp3-dev 3.0.4-13 > un dhcp3-server <none> > un dhcpcd <none> > un dhcpd <none> > ii dhcpdump 1.7-1.1 > ii dhcping 1.2-3 > -----------------> That looks good. (Sometimes people have problems if they still use the older "dhcp-client" package instead of "dhcp3-client". If all else fails you could try if the old package works for you, but I am pretty sure that your problem is related to the configuration of the card rather than the DHCP client.) > Also i am thinking that may be a problem because my system boots up the ra0 > interface in promiscous mode: > "dmesg | grep promi" : > device ra0 entered promiscuous mode > device eth1 entered promiscuous mode > Do you happen to know how do i disable promisc mode for ra0? You can check the current state of the interface with "/sbin/ifconfig ra0". If it is in promiscuous mode then you should see UP BROADCAST RUNNING PROMISC MULTICAST As root you can switch off promiscuous mode by running ifconfig ra0 -promisc AFAIK, however, it is normal for the device to switch to promiscuous mode whenever it tries to acquire a DHCP lease. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
