Re: Don't know what else to do with DHCP...help??

hoe-waa_at_hawaii.rr.com
Date: 05/31/04

  • Next message: Edward Carmody: "RE: Problems after CVSUP"
    Date: Mon, 31 May 2004 10:10:53 -1000
    To: Don <kindredmnementh@yahoo.com>
    
    
    

    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"

    
    
    

    _______________________________________________
    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"



  • Next message: Edward Carmody: "RE: Problems after CVSUP"

    Relevant Pages