Opened 5 years ago
Closed 5 years ago
#15326 closed bug (not reproducible)
DHCP logging constantly to syslog
Reported by: | dsuden | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Network & Internet | Version: | R1/Development |
Keywords: | Cc: | ttcoder | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
Getting tons of lines of info about DHCP connection attempts in syslog in Haiku 53416. Attaching example.
Attachments (1)
Change History (5)
by , 5 years ago
comment:1 by , 5 years ago
Cc: | added |
---|---|
Component: | Network & Internet/TCP → Network & Internet |
Owner: | changed from | to
comment:2 by , 5 years ago
35 DAEMON 'DHCP': /dev/net/rtl81xx/0: Received DHCP_NACK from 192.168.0.1
Your DHCP server is rejecting the requests. Either it is misconfigured (there may be no IP free in its IP range, for example, so it cannot allocate one), or there is something wrong in the requests we send.
A network capture may help analyzing this, run this for a minute or so and attach the resulting pcap file:
tcpdump -w dhcp.pcap -i /dev/net/rtl81xx/0 udp port 67 or udp port 68
comment:3 by , 5 years ago
The problem seems to be gone since the upgrade/reboot that's logged at the end of the above syslog. Maybe the situation is opposite to what I thought, the bug was present in 53379 and is gone in hrev53416 ?
Guess we should close this, and if this re-occurs we'll re-open with the tcpdump output.
comment:4 by , 5 years ago
Resolution: | → not reproducible |
---|---|
Status: | new → closed |
Looks like a regression from 53379 which Dane used a few days ago before updating to this one.. This is likely a TTS "blocker" for our release: we can't ship systems without functioning syslogs, would make it impossible to analyse problems escalating to customer support..
There's always something, right? :-)