Date: Mon, 31 May 2004 10:10:53 -1000 From: hoe-waa@hawaii.rr.com To: Don <kindredmnementh@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: Don't know what else to do with DHCP...help?? Message-ID: <dab552db08e9.db08e9dab552@socal.rr.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Aloha This sounds a whole lot like my DHCP problem. It was being discussed on this list earlier last week. I have attached my thread for your perusal. I have the same ethernet card as you. There is a workaround in the attachment that I am using (I also created a script to do it) but if someone comes up with a real fix it would be muck better. Read through my attachment and see if you think we have the same problem. Robert ----- Original Message ----- From: Don <kindredmnementh@yahoo.com> Date: Monday, May 31, 2004 1:56 am Subject: Re: Don't know what else to do with DHCP...help?? > > --- Rob <stopspam@users.sourceforge.net> wrote: > > What is the last entry in /var/db/dhclient.leases ? > > If there's something, does that make sense ? > > > > Anything dhclient related in /var/log/messages ? > > > > And how about running dhclient manually in the > > foreground ? > > As root, kill the running dhclient pid first, and > > then start: > > > > # dhclient -d rl0 > > > > where you should replace "rl0" by your own network > > card. > > Does that tell you something useful? > > > > Rob. > > There was nothing in the /var/db/dhclient.leases and > the only relevant thing I found in the > /var/log/messages was this > > May 31 05:02:10 kernel: skc0: <3Com 3C940 Gigabit > Ethernet> port 0xd800-0xd8ff mem 0xe5800000-0xe5803fff > irq 18 at device 9.0 on pci0 > May 31 05:02:10 kernel: skc0: 3Com Gigabit LOM > (3C940) > May 31 05:02:10 kernel: sk0: <Marvell Semiconductor, > Inc. Yukon> on skc0 > May 31 05:02:10 kernel: sk0: Ethernet address: > 00:0e:a6:46:f4:d9 > May 31 05:02:10 kernel: e1000phy0: <Marvell 88E1000 > Gigabit PHY> on miibus0 > May 31 05:02:10 kernel: e1000phy0: 10baseT, > 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, > auto > > and > > May 31 05:02:34 dhclient: Can't bind to dhcp address: > Address already in use > May 31 05:02:34 dhclient: Please make sure there is > no other dhcp server > May 31 05:02:34 dhclient: running and that there's no > entry for dhcp or > May 31 05:02:34 dhclient: bootp in /etc/inetd.conf. > Also make sure you > May 31 05:02:34 dhclient: are not running HP JetAdmin > software, which > May 31 05:02:34 dhclient: includes a bootp server. > > so it looks like the kernel is definitely identifying > my NIC correctly (I guessed this seeing how I was able > to install over FTP) but for whatever reason the > dchlient is no longer working > > I killed the dhclient pid and reran it...both as just > "dhclient" and "dhclinet -d sk0" both times the > computer would just sit there with nothing > happening...no messages no nothing (I let them sit > there for 10-15 minutes before I killed it) > > Don > > > > > __________________________________ > Do you Yahoo!? > Friends. Fun. Try the all-new Yahoo! Messenger. > http://messenger.yahoo.com/ > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" [-- Attachment #2 --] From hoe-waa@hawaii.rr.com Sent Wednesday, May 26, 2004 2:27 pm To Eric Crist Cc freebsd-questions@freebsd.org Subject Re: RE: ethernet card not coming up on reboot Aloha and Mahalo Okay, that works. I dropped out of gnome and logged in as root. I deleted all the append data in rc.conf and I deleted /usr/local/etc/rc.d/rc.local. I then rebooted. When I came back up ifconfig showed no ip address. I then did the "killall -9 dhclient" and the "sh /etc/netstart". After that completed ifconfig showed the ip address. So, what's happening? Is there a sequence problem or do I need to have a script run to kill dhclient and then run netstart? Thanks for your time helping with this problem. Robert ----- Original Message ----- From: Eric Crist <ecrist@secure-computing.net> Date: Wednesday, May 26, 2004 12:53 pm Subject: RE: ethernet card not coming up on reboot > Before you run the netstart command, you need to kill all processes > named dhclient. You can accomplish this with a: > > #killall -9 dhclient > > And then, #sh /etc/netstart > > Eric F Crist > President > AdTech Integrated Systems, Inc > (612) 998-3588 > > > > -----Original Message----- > From: hoe-waa@hawaii.rr.com [hoe-waa@hawaii.rr.com] > Sent: Wednesday, May 26, 2004 12:45 PM > To: Luke Kearney > Cc: Eric Crist; freebsd-questions@freebsd.org > Subject: Re: ethernet card not coming up on reboot > > > > Subject: Re: ethernet card not coming up on reboot > > > > > On Tue, 25 May 2004 20:00:12 -1000 > > hoe-waa@hawaii.rr.com spake thus: > > > > > Aloha Eric and Luke > > > > > > I am aware that sysinstall will append to rc.conf. > > > I went ahead and deleted all of the appends and rebooted. The > > > ethernet did not come up on reboot. I had to use sysinstall to get > > > an ip. And yes, it did append to rc.conf again. > > > > > > I will look into setting a static ip but I would like > > > to know why this is happening. I have 3 other boxes > > > that have FreeBSD on them and they don't have this problem. > > > > > > Robert > > > > > > ----- Original Message ----- > <SNIP> > > On Tuesday, May 25, 2004 8:15 pm > Luke Kearney <lukek@meibin.net> wrote: > > > When you used /stand/sysinstall again did you reboot to get the > IP or > > did you bring up the interface by hand? I am wondering if having > only> one config line in rc.conf gives you no IP upon boot whether > or not > > having booted and go no address can you get one by using netstart or > > not? eg > > > > #sh /etc/netstart > > > > This should re-read your rc.conf file and execute the network > related> cmds. > > After "sh /etc/netstart" I get : > > hw.bus.devctl_disable: 1-> 1 > (then the lo0 printou) > dhclient already running? (pid-221) > > and ifconfig -a unchanged. have to use sysinsstall. > > > > > One more shot in the dark and believe me this is a shot in the > > dark, try > > changing the line in rc.conf to ifconfig_sk0="UP" and then through > > rc.local run dhclient as a separate script. The net effect being > that> you start the interface before trying to get an IP as a separate > > process. > > I tried this but it didn't change anything...if I did it right? I > editedrc.conf and changed the line [ifconfig_sk0="DHCP"] to > [ifconfig_sk0="UP"] and created /usr/local/etc/rc.d/rc.local to read > ifconfig_sk0="DHCP" > > When I did this I could never i initialize DHCP. Even sysinstall > failed. > as a side note, during boot, the sequence delays for over a minute > during starting DHClient. It can't initialize sk0 but sysinstall > can. Go > figure? > > > > > > > Just out of curiousity, your other three machines that don't have > this > > problem, are they all identical to the machine that does? Somehow I > > think they are probably all unique in which case we can continue to > > focus on the machine at hand. > > You are absolutely right! My other boxes are all frankenputers. > > Robert > > > > HTH > > > > LukeK > > > > -- > > Luke Kearney <lukek@meibin.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dab552db08e9.db08e9dab552>