Mike Gerdts wrote:
On Tue, Jun 24, 2008 at 11:52 AM, Kyle McDonald <[EMAIL PROTECTED]> wrote:
Is there some way to get in.dhcp to spit out some info on why it's not
repsonding?
svcadm disable -t dhcp-server
/usr/lib/inet/in.dhcpd -dv
-> figure out what is going on
^C
svcadm enable dhcp-server
Duh! How did I miss the '-v' option....
Anyway, now I'm seeing:
48613894: Thread Id: 0003 - Monitoring Interface: bge0 *****
48613894: MTU: 1500 Type: SOCKET
48613894: Broadcast: 172.30.170.255
48613894: Netmask: 255.255.255.0
48613894: Address: 172.30.170.21
486138db: Datagram received on network device: bge0(limited broadcast)
486138db: Client: 0100145E2A91E2 has DYNAMIC 172.30.170.27 owned by
server: 172.30.170.21.
486138e0: Datagram received on network device: bge0(limited broadcast)
486138e0: Client: 0100145E2A91E2 has DYNAMIC 172.30.170.27 owned by
server: 172.30.170.21.
486138e8: Datagram received on network device: bge0(limited broadcast)
486138e8: Client: 0100145E2A91E2 has DYNAMIC 172.30.170.27 owned by
server: 172.30.170.21.
486138f8: Datagram received on network device: bge0(limited broadcast)
486138f8: Client: 0100145E2A91E2 has DYNAMIC 172.30.170.27 owned by
server: 172.30.170.21.
That's more info, but it doesn't explain why it's not responding. This
server is 172.30.170.21, so it is in charge of this address, and
172.30.170.27 is the address this client should be given. I've pinged
that address, and nothing responds, so nothing is out on the network
using that address.
Are these messages telling me something I'm not seeing?
-Kyle
_______________________________________________
networking-discuss mailing list
[email protected]
