Opened 6 years ago
Last modified 5 years ago
#14981 new bug
DHCP functionality not working after install
| Reported by: | adamfowleruk | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Servers/net_server | Version: | R1/Development |
| Keywords: | DHCP, ip | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | x86-64 |
Description
New install of hrev53001 resulted in the DHCP_DISCOVER being sent constantly, eventually timing out, and never receiving an IP address.
The DHCP changes that broke it on my system are here: https://review.haiku-os.org/c/haiku/+/1296
Blowing away that install with hrev52997 resulted in DHCP working instantly.
Please let me know what log files, if any, you need to resolve this issue.
Attachments (3)
Change History (8)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Weirdly, it now appears the problem is on both builds. DHCP works fine immediately after a fresh install on both revisions, but after the first and subsequent reboots, it gets stuck in the DHCP_DISCOVER loop.
by , 6 years ago
| Attachment: | syslog-hrev52997-reboot-not-working.txt added |
|---|
by , 6 years ago
| Attachment: | syslog-hrev53001-first-boot-working.txt added |
|---|
by , 6 years ago
| Attachment: | syslog-hrev53001-reboot-not-working.txt added |
|---|
comment:3 by , 6 years ago
| Summary: | DHCP functionality not working since hrev53000 → DHCP functionality not working after install |
|---|
Well, then this is not a regression at least :)
comment:4 by , 6 years ago
That third log file syslog-hrev53001-reboot-not-working.txt has garbage at the end, can't see the DHCP activity. Did it crash or is the DHCP client outputting garbage to the log?
comment:5 by , 5 years ago
| Component: | Network & Internet → Servers/net_server |
|---|---|
| Owner: | changed from to |
Tested connected directly to BTHomeHub6, and indirectly via NetGear GS116Ev2 managed switch. Same result. Tested two different network cables, one brand new.