dhcpcd question

[Matthew Carpenter]

How are you getting that log message, because your firewall drops it?

Use tcpdump to sniff for udp port 67 traffic.  See if that's ALL they they are sending.  They may be sending the correct traffic as well.
tcpdump -i eth1 udp port 67


begin  "Joel Hammer" <Joel at hammershome.com>
(Sat, 13 Jul 2002 18:22:53 -0400)

> bootps		67/tcp		# BOOTP server
> bootpc		68/tcp		# BOOTP client
> 
> eth1 is plugged into the comcast network.
> I am not running a dhcp server on this machine.
> I conclude that the server, broadcasting from its port 67, is broadcasting
> to any client listening on port 68. I do no know of any documentation
> for a server to do this in RFC 2131. Indeed, I have no processes
> listening to port 68. Does comcast have it show dhcpcd software that it
> gives its customers to use?
> My dhcpcd doesn't log anything except when it stops.
> Joel
> 
> On Sat, Jul 13, 2002 at 06:08:38PM -0400, Matthew Carpenter wrote:
> > <snip>
> > > 
> > > eth1 PROTO=17 10.133.184.1:67 255.255.255.255:68 
> > > ( I accept these packets.)
> > 
> > This looks like a server responding to a client.  What NIC is plugged into Comcast?  Are you running dhcpd on this system as well as dhcpcd?  I'm not sure what behavior shit would cause...  Would the machine fulfill its own dhcp requests?
> > 
> > 
> > 
> _______________________________________________
> Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users
> Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.


-- 
Matthew Carpenter
matt at e-i-s.cc                          http://www.e-i-s.cc/

Enterprise Information Systems
*Network Consulting, Integration & Support
*Web Development and E-Business