dhcpcd acts weird upon boot (SOLVED)

[c4nt1]

I get this weird thing from dhcpcd at boot

it starts with:

Code: Select all

running dhcpcd
Class ID

.. stuff scrolls by too fast for me to write it down ...

.. and stops with ...

ParseDhcpMsgRecv: 9 options recieved:
i=1 len=4 option = 255.255.255.0
i=3 len=4 option = 192.168.1.1

.. integer i increases to seemingly random numbers, while the ipv4 address varies and sometimes repeats itself

... and ends with ...

DhcpMsgRecv->yiaddr = 192.168.1.3
DhcpMsgRecv->siaddr = 0.0.0.0
DhcpMsgRecv->giaddr = 0.0.0.0
DhcpMsgRecv->sname = ""
ServerHardwareAddr = 00.0F.BF.26.33.9A

I searched google for it and all I got was this german or something website which made no sense to me. The google translation is at < http://tinylinks.net/459 >. This began to occur immediately after I had rebooted the system after doing a

Code: Select all

 # emerge --update --deep --newuse world 

because I had changed the USE flags a bit, so I am pretty sure the change in USE flags relates to the malfunctioning of dhcpcd. Thanks!

Oh yeah, here are my USE flags:

Code: Select all

USE="X acpi alsa avi bash-completion cdr debug doc dvd emacs ethereal gtk2 gnome -qt -kde mp3 png ncurses opengl truetype threads wifi xine xmms"

[UberLord]

dhcpcd gives you a big fat warning about building with the debug USE flag.

If you read it then it tells you that it prints lots of lovely debug information (which is does) but doesn't actually do anything to your interface - ie it doesn't work as a dhcp client.

[c4nt1]

Yeah, your ssuggestion to change my USE flags worked, but I think it was not only the debug flag after doing another

Code: Select all

 # emerge --update --deep --newuse world 

with debug removed I had the same problem. But now that I had a clue as to where the problem was coming from I began to remove a variety of my USE flags at once to see which ones was causing the problem. I believe that USE flag which caused dhcpcd to act weird is either the one for "ethereal" or "kerberos", but I am not 100% sure, because I removed a variety of others at the same time. Anyway, if anybody else has this problem, the only thing I can say is that this problem is caused by USE flags, although which ones in specific I do not know, and I would recommend fooling around with all of the networking-related ones first. Thanks again UberLord for your help!

[PovMan]

it'd be real nice if emerge could save all those messages somewhere, for those of us who don't sit there and read the screen while doing an upgrade

ie most of us.

[UberLord]

You mean something to log emerge output?
Read up on PORT_LOGDIR in /etc/make.conf