LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-22-2010, 04:11 PM   #16
BobNutfield
Senior Member
 
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,491

Rep: Reputation: 52

Quote:
Originally Posted by Richard Cranium View Post
If your gateway did not think that you had an address, you wouldn't be getting any TCP/IP traffic from your gateway.

You could perhaps log into your gateway (if that's possible; my gateway is another slackware box) to see if you have been given an address.

As for the message you are seeing...

...according to RFC 2132, that's a bad message. From the RFC...


(http://docstore.mik.ua/rfc/rfc2132.html#s8. and scroll down to 8.4)
Your link that you provided does in fact seem to explain this mysterious error. I do not unerstand what "vendor specific" information means, but there does not seem to be answer to it. I DO NOT get this error when I broadcast for a lease with dhclient, only dhcpcd.

Thank you very much for solving this mystery for me. No one on any other forum has been able to provide this information. Now if there was a cure for it, that would be great. But according to man dhcp:

Quote:
option dhcp-message-type uint8;
This option, sent by both client and server, specifies the type of DHCP message contained in the DHCP packet. Possible values (taken directly from RFC2132) are:

1 DHCPDISCOVER
2 DHCPOFFER
3 DHCPREQUEST
4 DHCPDECLINE
5 DHCPACK
6 DHCPNAK
7 DHCPRELEASE
8 DHCPINFORM

This option is not user configurable.
So whatever the problem is with DHCP on my machine, it is not changable..

Bob

Last edited by BobNutfield; 04-22-2010 at 04:37 PM.
 
Old 04-22-2010, 06:33 PM   #17
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,286

Rep: Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649
Well, I suspect that dhclient simply ignores that packet.

However, the dhcp server that is running on your gateway is broken. Sending a zero length option 43 packet is NOT in accordance with RFC 2132.

It appears that the Slackware version of dhcpcd is *very* old. See http://roy.marples.name/projects/dhc...DhcpcdDownload

From what I saw scanning the 5.1.5 release code, the newer version won't barf on a zero length option 43 packet. (Which makes sense since the client couldn't care less about that option.)

Sooo, you could attempt to build and install dhcpcd-5.1.5 and see if that works. Plus send a bug report to Pat. :-)
 
Old 04-23-2010, 03:23 PM   #18
BobNutfield
Senior Member
 
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,491

Rep: Reputation: 52
Thank you Richard. You have no idea how much I have dug into finding not just a solution, but understanding the error itself, and you are the first one I have come across who seems to understand it. I will try your solution and download that package. I will report back if it works.

Quote:
However, the dhcp server that is running on your gateway is broken. Sending a zero length option 43 packet is NOT in accordance with RFC 2132.
The gateway is a brand new Zytex router that I just purchased about four weeks ago. My old Belkin finally gave up the ghost on wireless after 7 years of use. I have a number of other machines, Linux and Windows, and Slackware is the only distro or OS that has the issue. As a matter of fact, I have another laptop which is newer and has meatier specs (dual core, 2GB mem) and I run Slackware -current on it. It internmittently also fails to get an IP address, but simply restarting /etc/rc.d/rc.inet1 just once gets me an IP address (using dhcpcd), but during boot it fails and falls back to a 169.XXX.XXX.XX address. I also run Ubuntu, Fedora and Crunchbang on other machines and none of them have this issue, so it is definitely a Slackware problem.

I will do as you suggested and submit a bug report to Pat, but the version of dhcpcd on Slackware -current is 5.2.1. The version on Slackware 13 stable that I have installed on the old P4 is 3.2.3, which indeed must be pretty old.

Bob

Last edited by BobNutfield; 04-23-2010 at 03:38 PM.
 
Old 04-23-2010, 04:07 PM   #19
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949

Original Poster
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
@ Bob

If you haven't already, it is probably a good idea to link back to this thread from the others you had going about the issue. Someone sometime will need that info I'm sure.
 
Old 04-23-2010, 04:19 PM   #20
BobNutfield
Senior Member
 
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,491

Rep: Reputation: 52
Thanks, damgar. I will do that now.

Bob
 
Old 04-23-2010, 10:07 PM   #21
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,286

Rep: Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649Reputation: 1649
Quote:
Originally Posted by BobNutfield View Post
I will do as you suggested and submit a bug report to Pat, but the version of dhcpcd on Slackware -current is 5.2.1. The version on Slackware 13 stable that I have installed on the old P4 is 3.2.3, which indeed must be pretty old.
Bob
Ah. I haven't been tracking -current so I didn't know that he's jumped a couple of releases there. I'm running Slackware64 13.0 (not current) myself.

BTW, I'm glad to have helped (despite my screen name). This stuff isn't hard per se, but sometimes you have to snuffle around in the documents to see what is supposed to happen. I do this for a living so I have an idea what to look for. :-)
 
Old 04-24-2010, 01:06 PM   #22
BobNutfield
Senior Member
 
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,491

Rep: Reputation: 52
Quote:
Originally Posted by Richard Cranium View Post
Ah. I haven't been tracking -current so I didn't know that he's jumped a couple of releases there. I'm running Slackware64 13.0 (not current) myself.

BTW, I'm glad to have helped (despite my screen name). This stuff isn't hard per se, but sometimes you have to snuffle around in the documents to see what is supposed to happen. I do this for a living so I have an idea what to look for. :-)
Just thought I would report back on the results of your suggestions to upgrade dhcpcd. IT WORKED!! I downloaded dchpcd 5.2.2 from the site you provided. I used gnashley's src2pkg app to convert it to a Slack package, and did upgradepkg. It installs dhcpcd to /usr/sbin and it must be moved to /sbin so that /etc/rc.d/rc.inet1 can find it. But on restart, I got an IP address first time.

Hope this information helps someone else with this issue.

Bob
 
  


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
Need help on virtual interface eth0:1 disable at boot time ravibhure Linux - Newbie 4 02-11-2010 03:12 AM
eth0 DHCP time out on boot AtomicAmish Fedora 9 06-19-2006 03:03 PM
Disable dhcpcd for eth0 on boot thomasw92 Linux - Newbie 2 04-10-2006 01:49 AM
How do I disable dhcp request at boot? EcceVery Debian 2 01-01-2006 02:07 AM
howto disable eth0 at boot time rydogg Linux - Newbie 2 06-16-2003 09:33 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:22 PM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration