LinuxQuestions.org
Help answer threads with 0 replies.
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 08-10-2004, 09:06 AM   #1
kennedy01
LQ Newbie
 
Registered: Nov 2003
Location: Georgia
Distribution: Slackware 10.1
Posts: 28

Rep: Reputation: 15
dhcpd not working on wlan0


Hello all, and thanks for taking the time to try to help me resolve my dhcpd issue with my wireless usb NIC. Let me first explain what I have. I have a Slackware 10.0 system with a stock kernel. I have installed the berliOS USB driver for my old Ipaq HNW-200 802.11b USB card (http://at76c503a.berlios.de/). I have setup the card as follows in /etc/rc.d/rc.wlan0

Code:
   #!/bin/sh
   #
   # rc.wlan0
   #

   CHANNEL=11
   ESSID="packetclip"
   INTERFACE="wlan0"
   IPADDR="192.168.200.1"
   KEY="56D7-51AD-1A24-609B-85BB-8952-24" # Change this to some random value
   MODE="Ad-Hoc"
   NETMASK="255.255.255.0"

   # Determine broadcast and network addresses from the IP address and netmask:

   BROADCAST=`/bin/ipmask $NETMASK $IPADDR | cut -f 1 -d ' '`
   NETWORK=`/bin/ipmask $NETMASK $IPADDR | cut -f 2 -d ' '`

   # Set up the WiFi card

   echo "Configuring ${INTERFACE}:"
   /sbin/ifconfig ${INTERFACE} ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
   /sbin/iwconfig ${INTERFACE} essid ${ESSID}
   /sbin/iwconfig ${INTERFACE} channel ${CHANNEL}
   /sbin/iwconfig ${INTERFACE} mode ${MODE}
   sleep 2
   /sbin/iwconfig ${INTERFACE} key ${KEY}
Using this configuration I can assign an IP to an AdHoc peer with the correct WEP key and ping the Slackware system. However, if I setup the peer as a DHCP client the Slackware server never provides an IP.

Here is my dhcpd.conf, I have added a line to rc.local to start the server on wlan0.

Code:
ddns-update-style none;
default-lease-time 2400;
max-lease-time 7200;

##subnet for wireless network
subnet 192.168.200.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option routers 192.168.200.1;
option domain-name-servers 192.168.2.1, 66.193.174.2, 66.193.174.3;
range 192.168.200.100 192.168.200.140;
}
Finally, Here is a view of the tcpdump of wlan0 while a client tries to get an IP from the DHCP sever. I apologize for the long post, but I thought the entire tcpdump might have something important for those with more experience.

Code:
root@KingSaul:/etc# tcpdump -i wlan0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes
07:49:21.354526 IP 192.168.200.10.netbios-dgm > 192.168.200.255.netbios-dgm: NBT UDP PACKET(138)
07:49:21.354751 arp who-has 192.168.200.10 tell 192.168.200.1
07:49:21.355539 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:49:21.360526 arp reply 192.168.200.10 is-at 00:09:5b:b5:69:7c
07:49:21.360559 IP 192.168.200.1.netbios-dgm > 192.168.200.10.netbios-dgm: NBT UDP PACKET(138)
07:49:22.842232 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:49:25.846705 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:49:26.590571 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:49:27.340463 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:49:30.841775 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:49:31.591636 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:50:08.932845 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:09.685694 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:10.433575 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:11.186419 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:12.683163 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:13.434025 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:13.436035 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:14.182891 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:14.184898 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:14.935733 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:14.937762 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:15.683615 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:15.685625 IP 192.168.200.10.netbios-ns > 192.168.200.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:50:15.805594 arp who-has 192.168.200.1 tell 192.168.200.10
07:50:15.805641 arp reply 192.168.200.1 is-at 00:90:4b:0e:84:bf
07:50:15.808597 IP 192.168.200.10 > 192.168.200.1: icmp 40: echo request seq 256
07:50:15.808726 IP 192.168.200.1 > 192.168.200.10: icmp 40: echo reply seq 256
07:50:16.434479 IP 192.168.200.10.netbios-dgm > 192.168.200.255.netbios-dgm: NBT UDP PACKET(138)
07:50:16.434683 IP 192.168.200.1.netbios-dgm > 192.168.200.255.netbios-dgm: NBT UDP PACKET(138)
07:50:16.435443 IP 192.168.200.1.netbios-dgm > 192.168.200.255.netbios-dgm: NBT UDP PACKET(138)
07:50:16.792417 IP 192.168.200.10 > 192.168.200.1: icmp 40: echo request seq 512
07:50:16.792484 IP 192.168.200.1 > 192.168.200.10: icmp 40: echo reply seq 512
07:50:17.792232 IP 192.168.200.10 > 192.168.200.1: icmp 40: echo request seq 768
07:50:17.792293 IP 192.168.200.1 > 192.168.200.10: icmp 40: echo reply seq 768
07:50:18.792050 IP 192.168.200.10 > 192.168.200.1: icmp 40: echo request seq 1024
07:50:18.792110 IP 192.168.200.1 > 192.168.200.10: icmp 40: echo reply seq 1024
07:50:20.800431 arp who-has 192.168.200.10 tell 192.168.200.1
07:50:20.803687 arp reply 192.168.200.10 is-at 00:09:5b:b5:69:7c
07:50:28.299316 IP 192.168.200.10 > 192.168.2.1: icmp 40: echo request seq 1280
07:50:28.303933 IP 192.168.2.1 > 192.168.200.10: icmp 40: echo reply seq 1280
07:50:29.310133 IP 192.168.200.10 > 192.168.2.1: icmp 40: echo request seq 1536
07:50:29.314665 IP 192.168.2.1 > 192.168.200.10: icmp 40: echo reply seq 1536
07:50:30.307953 IP 192.168.200.10 > 192.168.2.1: icmp 40: echo request seq 1792
07:50:30.312732 IP 192.168.2.1 > 192.168.200.10: icmp 40: echo reply seq 1792
07:50:31.307767 IP 192.168.200.10 > 192.168.2.1: icmp 40: echo request seq 2048
07:50:31.312063 IP 192.168.2.1 > 192.168.200.10: icmp 40: echo reply seq 2048
07:50:59.859540 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:51:12.839192 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:51:27.838458 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:51:59.838627 arp who-has 169.254.82.109 tell 169.254.82.109
07:52:00.305540 arp who-has 169.254.82.109 tell 169.254.82.109
07:52:01.305355 arp who-has 169.254.82.109 tell 169.254.82.109
07:52:02.308170 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:02.315174 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:02.356165 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:52:03.056036 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:03.057039 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:03.805903 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:03.806903 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:04.555763 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:04.556765 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:05.308625 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:05.309628 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:06.055489 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:06.056492 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:06.353433 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:52:06.805357 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:06.806355 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:07.555214 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:07.557218 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:08.307079 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:08.308083 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:09.055942 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:09.056945 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:09.805805 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:09.806808 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:10.555669 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:10.556671 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:11.307531 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:12.805257 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:14.305980 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:14.352974 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:52:15.805711 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:17.305434 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:18.306253 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:19.306071 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:20.305891 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:21.305709 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:22.055578 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:22.805435 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:23.555299 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:24.306162 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:25.056023 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:25.804888 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:26.555755 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
07:52:27.305613 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:27.306620 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:27.307619 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:27.308620 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:52:28.055478 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:52:28.805341 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:52:29.353240 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:52:29.557203 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:52:30.305068 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:52:31.054930 IP 169.254.82.109.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:52:32.462673 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:52:32.463680 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:53:01.352404 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:53:04.357836 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:53:12.351400 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:53:27.304669 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
07:53:28.351482 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:09:5b:b5:69:7c, length: 300
07:54:26.430546 IP 192.168.200.1.netbios-dgm > 192.168.200.255.netbios-dgm: NBT UDP PACKET(138)
07:54:26.431859 IP 192.168.200.1.netbios-dgm > 192.168.200.255.netbios-dgm: NBT UDP PACKET(138)
07:54:27.303733 IP 169.254.82.109.netbios-dgm > 169.254.255.255.netbios-dgm: NBT UDP PACKET(138)
At this point the Win2K client gives up.

Notes: I do have IPTABLEAS running. For debugging I commented out the line starting the IPTABLES process in rc.local and rebooted. The same problem existed. I also have dhcpd running on my Internal network eth1. Again I commented out the line starting dhcpd on eth1 AND the firewall and rebooted. The same problem existed.

My final assumption is that my el cheapo USB card cannot function as a DHCP sever, or I have missed something in the configuration of a wireless device. Thanks in advance for the help.
 
Old 08-10-2004, 10:21 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,785
Blog Entries: 1

Rep: Reputation: 413Reputation: 413Reputation: 413Reputation: 413Reputation: 413
It may be a simple typo.....The correct command to request an IP address from the DHCP server is dhcpcd wlan0 not dhcpd.
 
Old 08-10-2004, 02:25 PM   #3
kennedy01
LQ Newbie
 
Registered: Nov 2003
Location: Georgia
Distribution: Slackware 10.1
Posts: 28

Original Poster
Rep: Reputation: 15
The attempt to get an IP was made from a Win2K. This was after I set the IP manually and verified I could ping the Slackware sever. Set it back to DHCP (GUI of course). The tcpdump included was after I tried to get a lease from the Win2K machine.
 
Old 08-10-2004, 04:33 PM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,785
Blog Entries: 1

Rep: Reputation: 413Reputation: 413Reputation: 413Reputation: 413Reputation: 413
Sorry, I didn't read your post closely enough. I don't have much experience with this, but it looks like your dhcpd.conf file is OK and from your tcpdump, your card is seeing the dhcp request. Since your not getting an IP address, that suggests that dhcpd isn't responding. I know you said that you modified rc.local to start the server, but have you verified that it is running and listening on the right port? Also, are you starting it so that it uses your conf file?
 
Old 08-10-2004, 04:48 PM   #5
kennedy01
LQ Newbie
 
Registered: Nov 2003
Location: Georgia
Distribution: Slackware 10.1
Posts: 28

Original Poster
Rep: Reputation: 15
Im not near the server now. Tonight I'll send the portion of the rc.local file that starts dhcpd and also the response when I start the server. Anything else needed? Thanks for the help. --justin
 
Old 08-10-2004, 05:18 PM   #6
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,785
Blog Entries: 1

Rep: Reputation: 413Reputation: 413Reputation: 413Reputation: 413Reputation: 413
I'd also check the output of netstat -pantu to see if dhcpd is listening.
 
Old 08-10-2004, 07:55 PM   #7
slacka
LQ Newbie
 
Registered: Jul 2004
Location: Chico, CA
Distribution: Slackware 10
Posts: 21

Rep: Reputation: 15
If your Slackware machine is going to be the server, you need to set up the dnsmasq.conf file in /etc. There is a man page for it: #man dnsmasq. The startup script for it is /etc/rc.d/rc.dnsmasq. This works for my Slack server and XP client.
 
Old 08-11-2004, 09:04 AM   #8
kennedy01
LQ Newbie
 
Registered: Nov 2003
Location: Georgia
Distribution: Slackware 10.1
Posts: 28

Original Poster
Rep: Reputation: 15
In the end it was Operator Error

I was calling dhcpd incorrectly in my rc.local file as follows

##############INCORRECT################
#/usr/sbin/dhcpd eth1
#/usr/sbin/dhcpd wlan0
#######################################


Changed to the following
###############CORRECT#################
#/usr/sbin/dhcpd
#######################################


Its all happy :-) I have also verified it works with my IPTABLES firewall running.


Thank you VERY much for the help Hangdog42 and slacka! Its always something simple and operator error!

--justin
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Mandriva/Broadcom 4318/wlan0 not working konfusionrave Linux - Laptop and Netbook 11 09-21-2006 11:04 PM
dhcpd wlan0 hangs kaon Linux - Wireless Networking 6 10-01-2005 07:36 AM
dhcpd not working properly bwarsh Linux - Networking 1 08-15-2005 04:24 PM
dhcpd wlan0 does not work AP81 Slackware 2 04-18-2005 05:49 PM
Broadcom wireless with ndiswrapper: ifconfig wlan0 works; ifup wlan0 fails orangechicken Linux - Wireless Networking 2 04-17-2004 05:39 PM


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

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration