In article <200610220450.k9M4ocx4008811@rockhead.com>,
Paul Newhouse  <newhouse@rockhead.com> wrote:
>
> christos@astron.com (Christos Zoulas) wrote:
>
>>  In article <200610220317.k9M3HLuR004127@bigbox.wan.vpn>,
>>  Paul Newhouse  <newhouse@rockhead.com> wrote:
>>  >My old cable modem seized up and died a while back and
>>  >Comcast replace it with an RC DCM425c.  I hooked it up
>>  >to an XP system (doctor says I'll recover after a while ;)
>>  >and entered the account number and got the thing configured
>>  >... I think?
>>  >
>>  >Then I did the same thing I used to do with the old modem:
>>  >I powered if off and connected it to my NetBSD system (3.0.1).
>>  >When I run dhclient <cable interface> it doesn't get connected.
>>  >I can run tcpdump -i <cable interface> and see lots of arp traffic
>>  >going by so I think the equipment is working but, I keep getting
>>  >this in /var/log/messages:
>>  >
>>  >Oct 21 18:27:42 bigbox dhclient: No working leases in persistent
>>  >database - sleeping.
>>  >...
>>  >Oct 21 18:35:59 bigbox dhclient: No DHCPOFFERS received.
>>  >Oct 21 18:35:59 bigbox dhclient: No working leases in persistent
>>  >database - sleeping.
>>  >
>>  >
>>  >ifconfig of <cable interface> shows:
>>  >
>>  >: ifconfig tlp1
>>  >tlp1:
>>  >flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu
>>  >1500
>>  >        address: 00:a0:cc:3a:d9:52
>>  >        media: Ethernet autoselect (100baseTX full-duplex)
>>  >        status: active
>>  >        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
>>  >        inet6 fe80::2a0:ccff:fe3a:d952%tlp1 prefixlen 64 scopeid 0x3
>>  >
>>  >I have a DSL line that should be my default route but, I changed the
>>  >default to 0.0.0.0 and started up dhclient.  It still doesn't want to
>>  >connect.
>>  >
>>  >Can anybody tell me where I'm going wrong with this??
>>  
>>  try tcpdump -vv -s 1500 -i tlp1 port bootpc or port bootps
>
>Thanks that eliminates the noise.  I decided to reboot the firewall
>to clean up any loose ends.  Now I get:
>
>
># dhclient tlp1
>Internet Software Consortium DHCP Client V3.0.1rc11
>Copyright 1995-2002 Internet Software Consortium.
>All rights reserved.
>For info, please visit http://www.isc.org/products/DHCP
>
>Listening on BPF/tlp1/00:a0:cc:3a:d9:52
>Sending on   BPF/tlp1/00:a0:cc:3a:d9:52
>Can't bind to dhcp address: Address already in use
>Please make sure there is no other dhcp server
>running and that there's no entry for dhcp or
>bootp in /etc/inetd.conf.   Also make sure you
>are not running HP JetAdmin software, which
>includes a bootp server.
>
>If you did not get this software from ftp.isc.org, please
>get the latest from ftp.isc.org and install that before
>requesting help.
>
>If you did get this software from ftp.isc.org and have not
>yet read the README, please read it before requesting help.
>If you intend to request help from the dhcp-server@isc.org
>mailing list, please read the section on the README about
>submitting bug reports and requests for help.
>
>Please do not under any circumstances send requests for
>help directly to the authors of this software - please
>send them to the appropriate mailing list as described in
>the README file.
>
>exiting.
>bigbox# ps -auwx|grep dhc 
>root     480  0.0  0.0  256     4 ttyp2 R+    9:45PM 0:00.00 grep dhc (ksh)
>bigbox# nr
>Routing tables
>
>Internet:
>Destination        Gateway            Flags     Refs     Use    Mtu  Interface
>0/8                link#3             UC          0        0      -  tlp1 =>
>default            209.128.91.41      UGS         9      793      -  tlp0
>127/8              127.0.0.1          UGRS        0        0  33192  lo0
>127.0.0.1          127.0.0.1          UH          3       10  33192  lo0
>172.16.89/24       link#2             UC          1        0      -  re0
>172.16.89.42       00:40:05:36:73:53  UHLc        5     1155      -  re0
>209.128.91.40/29   link#1             UC          1        0      -  tlp0
>209.128.91.41      00:00:c5:97:fd:c8  UHLc        1        0      -  tlp0
>
>I'm not running a dhcp server or a boot server, so now I'm even more confused.
>
>Paul

what does fstat | grep :68 say?

christos