So what was the solution to this? I am having the same problem with Suse 9.2. It's a Compaq X1000 laptop so it looks like it could be the same problem as the HP. I have tried everything this thread has suggested with no luck. I get signal strength and it says connected, but I can't even ping my router. I set up a default Gateway..but it still doesn't help. I'm running out of ideas here... -----Original Message----- From: Richard [mailto:ratcheson@earthlink.net] Sent: Saturday, September 11, 2004 9:51 PM To: suse-linux-e@suse.com Subject: Re: [SLE] HP WiFi On Saturday 11 September 2004 09:13 am, Jim Sabatke wrote:
I'm going in circles. I've tried everything I've found on the net. Seems like everyone has an "easy" way to do it, and none of them are working for me. Here are some of my details: Jim, I started this earlier today but got sidetracked. Will send it all anyway cuase it might help you a bit.
First some questions. When you use XP, are you using dhcp to get your IP? If yes then the wireless router is capable of doing its job. Also, it may not be setup to deal with a fixed IP which is what you have setup to do in the following.
wmugsy:/home/jim # cat /etc/sysconfig/network/ifcfg-wlan0 BOOTPROTO='static' DHCLIENT_SET_DOWN_LINK='yes' DHCLIENT_MODIFY_RESOLV_CONF='yes' DHCLIENT_SET_DEFAULT_ROUT='yes' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' WIRELESS='yes' WIRELESS_ESSID=NETGEAR WIRELESS_KEY='' WIRELESS_MODE='Ad-hoc' WIRELESS_NICK='' WIRELESS_NWID='' MII_NOT_SUPPORTED='yes' WIRELESS_RTS='off' BROADCAST='192.168.0.255' IPADDR='192.168.0.97' NETMASK='255.255.255.0' UNIQUE='' #NETWORK='192.168.0.0' CHANNEL='6' wmugsy:/home/jim #
Next question is, is your router acting as an access point? It probably is so you need to use Managed Mode, not ad hoc. Ad-hoc is for peer to peer stuff. First thing I would do is zero out all you have put in your ifcfg-wlan0 until you have the thing talking to your router manually, then you can play with making it setup on boot later. you can manually put in all you need via the iwconfig command e.g., iwconfig alone will read the wireless card and tell you what you have going. ifconfig is another goodie that will show you what is setup. Remember you need to be root, as in su, to make the things work. ifconfig should show something like: lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:72 errors:0 dropped:0 overruns:0 frame:0 TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4664 (4.5 Kb) TX bytes:4664 (4.5 Kb) wlan0 Link encap:Ethernet HWaddr 00:90:96:A7:22:58 inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::290:96ff:fea7:2258/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:178 errors:0 dropped:0 overruns:0 frame:0 TX packets:172 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:24153 (23.5 Kb) TX bytes:35969 (35.1 Kb) Interrupt:11 Memory:fcffc000-fcffdfff This shows you that wlan0 is getting it IP and all that good stuff. iwconfig will give you something like this if it is setup properly: lo no wireless extensions. wlan0 IEEE 802.11g ESSID:"linux01" Nickname:"richdell" Mode:Managed Frequency:2.447GHz Access Point: 00:30:BD:FA:9F:63 Bit Rate=48Mb/s Tx-Power:14 dBm RTS thr=2347 B Fragment thr=2346 B Encryption key:<26digitkey> Security mode:restricted Power Management:off Link Quality:100/100 Signal level:-30 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:5 Invalid misc:238493 Missed beacon:0 If you dont see that then you need to methodically put the stuff in using iwconfig wlan0 <command> AND in my machines they have to be entered in specific sequence. Encryption has to be set before the card will take the ESSID. So I first do: iwconfig wlan0 enc 1245678901234567890abcdef to set the encryption mode and key, then iwconfig wlan0 essid linux01 to set the ESSID. On some cards you may need to place quotes around the name. Now if that takes, and you can verify it by doing iwconfig wlan0 then the next thing you need to do is dhcpcd wlan0 which should get you the IP. If it says its already running you may need to stop the thing and redo it by dhcpcd stop, then dhcpcd wlan0. Another good command to remember is rcnetwork restart That will obviously restart your network and show if the wifi card is getting its IP.
I have no idea what to put in for UNIQUE, if I need anything at all.
If I use dhcp, it can't get one and backgrounds.
wmugsy:/home/jim # ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 00:90:4B:5D:32:6D inet addr:192.168.0.97 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::290:4bff:fe5d:326d/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:54 dropped:0 overruns:0 carrier:0
Looks to me like you are setting the inet addr of your wifi card manually and the router is probably not setup to do fixed addresses. What does a ping to 192.168.0.1 get you? -- Old age ain't for Sissies! -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com