#4377 closed bug (fixed)
broadcom570x: DHCP does not work when plugging in cable after boot
| Reported by: | PieterPanman | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Drivers/Network | Version: | R1/Development |
| Keywords: | Cc: | umccullough, bergep@… | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
hrev32819. When I have my network cable plugged in on boot, it gets the ip address just fine through DHCP. However, when I boot with the cable unplugged, and plug it in a few minutes after haiku booted up, it does not get the proper IP address, but maintains the private address. Possibly something with the freebsd compat layer? Looking at the syslog, it seems that it tries to get the DHCP address anyway, even though the cable is not connected. Is that normal?
Attachments (7)
Change History (19)
by , 15 years ago
| Attachment: | syslog_dhcp_fail added |
|---|
comment:1 by , 15 years ago
comment:3 by , 15 years ago
| Component: | - General → Drivers/Network |
|---|
That should only happen if the link status is not propagated correctly. Can you please add the output of "ifconfig"? Also, does DHCP work if you trigger it manually via "ifconfig /dev/net/... auto-config"?
comment:4 by , 15 years ago
I booted with cable disconnected, pluggged it in after a minute and then tried the auto-config. It results in the same messages in the syslog as when I just plugged in the cable, with a DHCP timeout. Attached are the ifconfig logs.
by , 15 years ago
| Attachment: | ifconfig_plugged_in_on_boot.txt added |
|---|
by , 15 years ago
| Attachment: | ifconfig_unplugged_on_boot.txt added |
|---|
by , 15 years ago
| Attachment: | ifconfig_unplugged_on_boot_then_plugged_in.txt added |
|---|
by , 15 years ago
| Attachment: | ifconfig_unplugged_on_boot_then_plugged_in_then_autoconfig.txt added |
|---|
by , 15 years ago
| Attachment: | ifconfig_down.txt added |
|---|
by , 15 years ago
| Attachment: | ifconfig_down_then_up.txt added |
|---|
comment:5 by , 15 years ago
Also, when I down the interface, and then bring it back up, the errors quickly build up. See the last two ifconfigs.
comment:6 by , 15 years ago
| Cc: | added |
|---|
comment:7 by , 15 years ago
| Cc: | added |
|---|
comment:9 by , 14 years ago
I would like to, but unfortunately my laptop with the broadcom chip passed away. Perhaps some of the others that experienced the same issues can retest? I might try with my other system if I have time.
comment:10 by , 14 years ago
This appears fixed for me using hrev34909.
I had this problem with Alpha 1. Below is my ethernet hardware: device Network controller (Ethernet controller) [2|0|0]
vendor 8086: Intel Corporation device 1229: 82557/8/9/0/1 Ethernet Pro 100
I booted without the ethernet cable and verified I had the 169.... bad ipaddress I used the network applet to enable dhcp and got a vaild ip address from my router. Thanks Alex. Not sure if this can be closed since I was only able to test this with the epro100 driver.
comment:11 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Works for me too. Closing, since PieterPanman can't test, and the bug is fixed for me and thetick.
comment:12 by , 14 years ago
Well, not related to the original device, but it works fine for the ipro1000 with this device: 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) Thanks!
FWIW, I think every one of my machines probably exhibits this same behavior (different drivers).
I think it's lack of link state notification?