Guest Michael Posted April 9, 2006 Report Share Posted April 9, 2006 Hi there, I am a Madriva / Linux newbie trying to troubleshoot a wifi issue that resently sprang up. I'm running Mandriva 2006 on a Dell Inspiron 6000 laptop with built in wifi capabilities. Since I've installed 2006, I've been able to detect wireless networks and connect with drakroam with no problem. Then out of the blue, I can no longer connect however drakroam correctly identifies the wireless network. I really can't figure out what variables have changed on the box / network, other than running madriva update. To be sure, I can connect to the wireless network without issue on winxp (the laptop is dual boot). I have tried removing WEP, as well as stopping shorewall, but I still cannot connect. Other than this, I really have no idea how to go about troubleshooting this issue. Does anyone have any suggestions? Thanks, Mike Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted April 9, 2006 Report Share Posted April 9, 2006 What is your wireless card? What chipset? Quote Link to comment Share on other sites More sharing options...
lynchmob Posted April 9, 2006 Report Share Posted April 9, 2006 Are you using dhcp? What does your /etc/sysconfig/network file say? Could be gateway ot dns. Quote Link to comment Share on other sites More sharing options...
Guest Michael Posted April 9, 2006 Report Share Posted April 9, 2006 Hey guys, Thanks for the speedy replies. In terms of hardware, I am running a Intel PRO/Wireless 2915ABG MiniPCI Adapter When I try to connect eth2 using the drak network manager, I get the following in the message log: Apr 9 17:43:28 localhost net_applet[4611]: launched command: /usr/sbin/usernetctl eth2 report Apr 9 17:43:28 localhost net_applet[4611]: running: /sbin/ifup eth2 daemon Apr 9 17:43:29 localhost dhclient: eth1: unknown hardware address type 24 Apr 9 17:43:30 localhost dhclient: eth1: unknown hardware address type 24 Apr 9 17:43:32 localhost dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 3 Apr 9 17:43:35 localhost dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 4 Apr 9 17:43:39 localhost dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 6 Apr 9 17:43:45 localhost dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 15 Apr 9 17:44:00 localhost dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 17 Apr 9 17:44:17 localhost dhclient: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 16 Apr 9 17:44:33 localhost dhclient: No DHCPOFFERS received. Apr 9 17:44:33 localhost dhclient: Trying recorded lease 192.168.2.5 sysconfig/networks reads as follows: NETWORKING=yes lynchmob, your dchp hunch is compelling, however, I am able to connect a-okay with a physical ethernet cable connection. Any ideas? Thanks again, Mike Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted April 10, 2006 Report Share Posted April 10, 2006 I'm assuming your also using DHCP to get the IP on the Wireless connection under Windows? Quote Link to comment Share on other sites More sharing options...
Guest Michael Posted April 10, 2006 Report Share Posted April 10, 2006 That is right, I am using DHCP on Windows when connecting wirelessly. Quote Link to comment Share on other sites More sharing options...
Qchem Posted April 11, 2006 Report Share Posted April 11, 2006 Is it feasible to use a static IP address? I'd at least try setting for a short while to rule out some potential problems. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.