Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 845061 Details for
Bug 1048342
dhcpd stops after working
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
tcpdump showing dhcp packets arriving, but no dhcpd response
dhcpd-tcpdump (text/plain), 4.42 KB, created by
sean darcy
on 2014-01-03 19:08:27 UTC
(
hide
)
Description:
tcpdump showing dhcp packets arriving, but no dhcpd response
Filename:
MIME Type:
Creator:
sean darcy
Created:
2014-01-03 19:08:27 UTC
Size:
4.42 KB
patch
obsolete
>No dhcp log messages. But tcpdump shows lots received: > >11:57:01.210319 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:02.210316 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:13.205292 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:14.205304 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:15.205282 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:18.897303 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:82:40:0e:93, length 548 >11:57:21.983290 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:82:40:0e:93, length 548 >11:57:25.061279 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:82:40:0e:93, length 548 >11:57:26.200279 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:27.200284 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:28.199258 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:28.848254 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from cc:6d:a0:11:22:a0, length 548 >11:57:39.198233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:40.195231 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >11:57:41.194227 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:99:6a:9c:94, length 554 >,,,,,,,,, > >Now I systemctl restart dhcpd, and it recognizes all the DHCP requests: > >Jan 2 11:59:36 new-gateway systemd[1]: Started DHCPv4 Server Daemon. >Jan 2 11:59:36 new-gateway dhcpd: Internet Systems Consortium DHCP Server 4.2.5 >Jan 2 11:59:37 new-gateway dhcpd: Copyright 2004-2013 Internet Systems Consortium. >Jan 2 11:59:37 new-gateway dhcpd: All rights reserved. >Jan 2 11:59:37 new-gateway dhcpd: For info, please visit https://www.isc.org/software/dhcp/ >Jan 2 11:59:37 new-gateway dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file >Jan 2 11:59:37 new-gateway dhcpd: Wrote 0 deleted host decls to leases file. >Jan 2 11:59:37 new-gateway dhcpd: Wrote 0 new dynamic host decls to leases file. >Jan 2 11:59:37 new-gateway dhcpd: Wrote 12 leases to leases file. >Jan 2 11:59:37 new-gateway dhcpd: >Jan 2 11:59:37 new-gateway dhcpd: No subnet declaration for wlan0 (no IPv4 addresses). >Jan 2 11:59:37 new-gateway dhcpd: ** Ignoring requests on wlan0. If this is not what >Jan 2 11:59:37 new-gateway dhcpd: you want, please write a subnet declaration >Jan 2 11:59:37 new-gateway dhcpd: in your dhcpd.conf file for the network segment >Jan 2 11:59:37 new-gateway dhcpd: to which interface wlan0 is attached. ** >Jan 2 11:59:37 new-gateway dhcpd: >Jan 2 11:59:37 new-gateway dhcpd: Listening on LPF/external/00:1d:72:05:4a:68/24.0.0.0/8 >Jan 2 11:59:37 new-gateway dhcpd: Sending on LPF/external/00:1d:72:05:4a:68/24.0.0.0/8 >Jan 2 11:59:37 new-gateway dhcpd: Listening on LPF/internal/00:e0:4c:03:07:ba/10.10.11.0/24 >Jan 2 11:59:37 new-gateway dhcpd: Sending on LPF/internal/00:e0:4c:03:07:ba/10.10.11.0/24 >Jan 2 11:59:37 new-gateway dhcpd: Sending on Socket/fallback/fallback-net >Jan 2 11:59:38 new-gateway dhcpd: DHCPDISCOVER from 00:15:99:6a:9c:94 via internal >Jan 2 11:59:38 new-gateway dhcpd: DHCPOFFER on 10.10.11.152 to 00:15:99:6a:9c:94 via internal >Jan 2 11:59:38 new-gateway dhcpd: DHCPREQUEST for 10.10.11.152 (10.10.11.251) from 00:15:99:6a:9c:94 via internal >Jan 2 11:59:38 new-gateway dhcpd: DHCPACK on 10.10.11.152 to 00:15:99:6a:9c:94 via internal >Jan 2 11:59:40 new-gateway dhcpd: DHCPREQUEST for 10.10.11.152 (10.10.11.251) from 00:15:99:6a:9c:94 via internal >Jan 2 11:59:40 new-gateway dhcpd: DHCPACK on 10.10.11.152 to 00:15:99:6a:9c:94 via internal >Jan 2 11:59:51 new-gateway dhcpd: DHCPDISCOVER from 00:0b:82:40:0e:93 via internal >Jan 2 11:59:51 new-gateway dhcpd: DHCPOFFER on 10.10.11.182 to 00:0b:82:40:0e:93 via internal >Jan 2 11:59:51 new-gateway dhcpd: DHCPREQUEST for 10.10.11.182 (10.10.11.251) from 00:0b:82:40:0e:93 via internal >Jan 2 11:59:51 new-gateway dhcpd: DHCPACK on 10.10.11.182 to 00:0b:82:40:0e:93 via internal
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1048342
:
845050
| 845061