LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 07-06-2004, 12:47 PM   #1
xias
LQ Newbie
 
Registered: Jul 2004
Distribution: Slackware 10.0
Posts: 10

Rep: Reputation: 0
Question dhcp problems in slackware 10.0


I have just installed slack 10.0 on my hp omnibook 5700 ctx. I have a trendnet cardbus network card. It installs just fine, lsmod shows the 8139too driver as being loaded. But when I try to get an IP address via dchpcd it doesn't work. I can see the lights blinking on the net card and I can see my router offering the ip address, but it doesn't accept it for whatever reason. I also tried dhclient but it says it can't find eth0. Am I missing something? By the way I've been trolling this forum for about 3 weeks now trying other solutions I've seen. I.E., I tried setting a hostname in dhpcd, I've tried the "-r" option. I've looked at my iptables config. I've tried setting a static route. All I ever get when I ping my router with the static route is "network unreachable". And yes I did setup the route in the router. Any and all help would be greatly appreciated.
 
Old 07-06-2004, 01:01 PM   #2
broxys
Member
 
Registered: Jun 2003
Location: nj
Distribution: slack10
Posts: 46

Rep: Reputation: 15
perhaps my problem. Is the same? Or related at least.
This is really surprising from the notoriously ultra-stable Slackware.
 
Old 07-06-2004, 01:08 PM   #3
xias
LQ Newbie
 
Registered: Jul 2004
Distribution: Slackware 10.0
Posts: 10

Original Poster
Rep: Reputation: 0
Mine does the same thing. I'll bring up the interface with ifconfig. Then I run dhpcd. It timesout waiting for the dhcpoffer and brings the interface down. Very weird. But I've also tried the same thing on slack 9 and got the same result. The sad part is I'm pretty sure the problem is some little setting I forgot to configure, but for the life of me I don't know what it is. Hopefully one of the gods, I mean gurus here can show me the light. Hehe.
 
Old 07-06-2004, 03:18 PM   #4
broxys
Member
 
Registered: Jun 2003
Location: nj
Distribution: slack10
Posts: 46

Rep: Reputation: 15
AH - HA!

try this. I have no clue WHY this works.. but for some reason it allows me to maintain a connection with an AP and get an IP:

1. bring up wirless ingerface
2. dhclient wlan0 (or whatever else). this will fail with some error about the interface not being found.
3. dhcpcd wlan0 (etc..) should then work fine.

WHY does this work? i don't know...

I really hope there's a better way to do this.. but for now, this works for me.
 
Old 07-06-2004, 03:20 PM   #5
xias
LQ Newbie
 
Registered: Jul 2004
Distribution: Slackware 10.0
Posts: 10

Original Poster
Rep: Reputation: 0
Well I'm at work now, but I'll try it when I get home.
 
Old 07-07-2004, 09:43 AM   #6
xias
LQ Newbie
 
Registered: Jul 2004
Distribution: Slackware 10.0
Posts: 10

Original Poster
Rep: Reputation: 0
Damn, still has the same problem. I'll keep researching and I'll hopefully figure it out. If anyone has any suggestions please post them, I'll be lurking around.
 
Old 07-07-2004, 12:08 PM   #7
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
Quote:
Then I run dhpcd
This may be running well into trivia territory, but the command is dhcpcd not dhpcd. If I remember correctly, dhpcd is a dhcp server you can run if you want to use your system as a dhcp server.
 
Old 07-07-2004, 12:52 PM   #8
xias
LQ Newbie
 
Registered: Jul 2004
Distribution: Slackware 10.0
Posts: 10

Original Poster
Rep: Reputation: 0
My bad, that was a typo. I sometimes type a little fast.
 
Old 07-07-2004, 01:46 PM   #9
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
So much for that idea.....

The only other suggestion I have is to rummage around in /var/log/syslog and /var/log/messages and see if dhcpcd is reporting anything other than the brutally obivous. To be honest, this one has me stumped since I can use dhcpcd on Slackware 10 without any trouble. The only thing I can think of is that the card isn't configured right. Wrong key or ssid for instance.

Actually, if broxys has some spare time, it would be interesting to see the output of ifconfig and iwconfig for the wireless card both before and after the dhclient step.
 
Old 07-07-2004, 02:38 PM   #10
xias
LQ Newbie
 
Registered: Jul 2004
Distribution: Slackware 10.0
Posts: 10

Original Poster
Rep: Reputation: 0
My card isn't wireless, it's wired. And ya you're right, I should check the logs. When I get home I'll check them and post back. Thanx for the tip Hangdog42.
 
Old 07-07-2004, 02:51 PM   #11
broxys
Member
 
Registered: Jun 2003
Location: nj
Distribution: slack10
Posts: 46

Rep: Reputation: 15
iwconfig after bringing up the interface:
Code:
wlan0     IEEE 802.11-DS  ESSID:"<AP Name>"  Nickname:"<AP Name>"
          Mode:Managed  Frequency:2.437GHz  Access Point: <AP MAC>
          Bit Rate:2Mb/s   Tx-Power:2346 dBm   
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality:68/92  Signal level:-60 dBm  Noise level:-100 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
ifconfig after `dhclient wlan0`
Code:
wlan0     Link encap:Ethernet  HWaddr <My MAC>
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3430 (3.3 Kb)  TX bytes:0 (0.0 b)
iwconfig after `dhclient wlan0`
Code:
wlan0     IEEE 802.11-DS  ESSID:"<AP Name>"  Nickname:"<AP Name>"
          Mode:Managed  Frequency:2.437GHz  Access Point: <AP MAC>
          Bit Rate:2Mb/s   Tx-Power:2346 dBm   
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality:66/92  Signal level:-62 dBm  Noise level:-100 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
`dhcpcd wlan0 -d`:
Code:
dhcpcd: MAC address = <My MAC>
dhcpcd: your IP address = 192.168.1.100
dhcpcd: MAC address = <My MAC>
dhcpcd: your IP address = 192.168.1.100
ifconfig after `dhcpcd wlan0`:
Code:
wlan0     Link encap:Ethernet  HWaddr <My MAC>
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:11513 (11.2 Kb)  TX bytes:638 (638.0 b)
iwconfig after `dhcpcd wlan0`:
Code:
wlan0     IEEE 802.11-b  ESSID:"<AP Name>"  Nickname:"<AP Name>"
          Mode:Managed  Frequency:2.437GHz  Access Point: <AP MAC>
          Bit Rate:11Mb/s   Tx-Power:2346 dBm   
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality:68/92  Signal level:-60 dBm  Noise level:-100 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
It's worth noting that I AM actually using WEP, which makes the "Encryption key: off" bit a little dubious. However, my card uses the prism2_usb drivers, so i am using the linux-wlan-ng tools instead of iwconfig. Perhaps iwconfig isn't aware of all the commands I issue.

Last edited by broxys; 07-07-2004 at 02:55 PM.
 
Old 07-09-2004, 07:27 AM   #12
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
Quote:
which makes the "Encryption key: off" bit a little dubious.
You may be right about iwconfig not reflecting the actaul state of the card, but I would still be suspicious about this. From what you've posted, iwconfig is otherwise showing correct information, so I would at least consider that your WEP key isn't being set properly. Probably the best way to test this would be to turn off WEP encryption at your router and see if you can connect then.
 
Old 07-09-2004, 07:47 AM   #13
broxys
Member
 
Registered: Jun 2003
Location: nj
Distribution: slack10
Posts: 46

Rep: Reputation: 15
The thing is, that state is when I was already connected with an IP. I've noticed since then that the Encryption Key: Off bit isn't there every time. So, for isntance, right now my iwconfig looks normal.

What's really wierd to me is that i need to run `dhclient wlan0` before `dhcpcd wlan0` to properly get an IP address.
 
Old 07-09-2004, 08:00 AM   #14
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
I don't understand that at all. The only thing I can suggest is to run dhcpcd first and then rummage through your syslogs and see if it has left any indications what is happening. From what you've posted so far, dhclient isn't really messing with the card configuration at all, so I suspect the problem lies somewhere else in the system and this is just a symptom.

I do know that Slackware can do some kind of strange things with kernel modules. I've been working on a script that would scan for access points on start-up, so I loaded my ndiswrapper module, but didn't configure the card any further. However, as soon as I tried to run iwlist, Slackware would run the card configuration script I normally used. The point is I hadn't asked Slackware to run this script and I don't know why it did so there may be something similarly strange going on with dhcpcd your system. Hopefully it is leaving some clue in the syslogs.
 
Old 07-09-2004, 10:16 AM   #15
dissolved soul
Member
 
Registered: Sep 2002
Posts: 35

Rep: Reputation: 15
i had the same problem in slack 10.
i had installed it twice.. dhcp didn't work.
then i installed a third time, and honestly the only difference was i used reiserfs on my root partition instead of ext3.
then dhcp worked fine (and has been working great on my built in ethernet and my pcmcia wireless adapter).

i know that reiserfs wouldnt make any difference, i just thought it was strange.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP problems - multiple DHCP servers sat86 Linux - Networking 4 10-02-2005 05:43 AM
slackware and dhcp realcr Linux - Networking 1 09-11-2005 05:35 AM
slackware and DHCP veritas Slackware 5 12-08-2003 07:16 PM
DHCP on Slackware reclusivemonkey Linux - Networking 1 10-18-2003 10:04 AM
XP Pro Build 2600/sp1 v.1105 DHCP Client to Redhat 8.0 DHCP Server - Problems atomant Linux - Networking 5 06-28-2003 11:24 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 02:12 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration