On Mon, 2010-06-28 at 09:35 -0600, Carlos Konstanski wrote: > On 06/28/2010 09:28 AM, Keith wrote: > > It appears that everything is setup, but I have no network access. ping > > or traceroute do not work. > > > > wlan0 IEEE 802.11bg ESSID:"dlink" > > Mode:Managed > > Frequency:2.432 GHz > > Access Point: 00:18:E7:CB:B2:20 > > Bit Rate=36 Mb/s Tx-Power=20 dBm > > Retry long limit:7 RTS thr:off Fragment thr:off > > Encryption key: foo > > Power Management:off > > Link Quality=70/70 Signal level=-38 dBm > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > linux-nxy3:~ # ifup wlan0 > > wlan0 name: RTL8187B_WLAN_Adapter > > wlan0 warning: WPA configured but may be unsupported > > wlan0 warning: by this device > > wlan0 warning: wpa_supplicant already running on interface > > DHCP4 client is already running on wlan0 > > IP address: 192.168.0.103/24 > > > > > > This is from the router. It shows that the USB WiFI card is connected, > > but no network activity with the wireless USB card in OpenSuSE. > > > > Wireless LAN > > Wireless Radio : Enabled > > 802.11 Mode : Mixed 802.11n, 802.11g and 802.11b > > Channel Width : 20MHz > > Channel : 5 > > Secondary Channel : > > WISH : Active > > Wi-Fi Protected Setup : Enabled/Configured > > Guest Wi-Fi Protected Setup : Enabled/Not Configured > > SSID List > > Network Name (SSID) Guest MAC Address Security Mode > > dlink No 00:18:e7:cb:b2:20 WPA/WPA2 - Personal > > > > > > If I plug the USB WiFI into a Ubuntu Laptop it works with no problems. > > There must be something else I have to do? I have gone into YaST network > > setup and added DHCP support. > > What's your route look like, and also your resolv.conf file? These should be > set by the DHCP client. Is a DHCP client being started? The ifup output says > so, but I'd double-check. > > Can you ping a host by IP address? This takes DNS out of the picture, and > narrows the scope of the problem to resolv.conf. > > Here is a typical routing table for a laptop with a single interface - wlan0 > - up: > > r...@sphinktop:~# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.1.0 0.0.0.0 255.255.255.0 U 2000 0 0 wlan0 > 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 2000 0 0 wlan0
Thank you for the information. OK it looks like it is still bringing up eth0 and not wlan0. I don't know what to set so that wlan0 is the default route and not eth0. I unplugged the network cable and restarted Linux with the USB wireless plugged in & this was the result. linux-nxy3:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 linux-nxy3:~ # cat /etc/resolv.conf ### /etc/resolv.conf file autogenerated by netconfig! ### Please remove (at least) this line when you modify the file! search hsd1.or.comcast.net. nameserver 192.168.0.1 linux-nxy3:~ # _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
