Opened 14 years ago
Closed 14 years ago
#7260 closed bug (fixed)
DHCP doesn't work at the first time
| Reported by: | Giova84 | Owned by: | phoudoin |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Network & Internet/IPv4 | Version: | R1/Development |
| Keywords: | dhcp ip ethernet | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
I found a bug with the network connection. All my computers go on internet in dhcp mode (on the first desktop computer i have an Intel pro1000 ethernet card, and on the second desktop computer i have two ethernet cards: a Realtek rt8139 and an nforce) all the ethernet cards are correctly recognized. When i look in network preferences, i can see all the correct ip addresses and the right domain (i am under NAT) assigned by dhcp (dhcp is selected by default), and the network replicant has the green signal. but when i go to open webpositive or i try to ping any website, seem to be no active connections: i get errors about inactive connection (this even after an hour of waiting). So i have to open again the network prefs and press the "apply" button (after this operation it become gray). After this i can go on internet and the ping work correctly. I found this problem on every release of Haiku. Currently i run #40596. Sorry for my imperfect english.
Attachments (3)
Change History (14)
follow-up: 2 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Replying to MichaelPeppers:
I can confirm it happening with an nforce since... well, forever, though it happens seldom and only on startup. Don't know how to reproduce it, sorry, it looks like a hit and miss bug to me.
Hi Michael, it happens to me at every startup, not seldom. Best regards.
comment:3 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
Sounds more like an issue with getting DNS settings right at first DHCP request. Since a week or two, DHCP messages are a bit more well traced in /var/log/syslog. Could you post your(s) so one could investigate a bit more what actually happends at second try that don't at first.
Thanks.
by , 14 years ago
| Attachment: | Before.jpg added |
|---|
by , 14 years ago
by , 14 years ago
comment:4 by , 14 years ago
I made some screenshots, before and after: seems the card immediately gets the correct DNS addresses.
Above I have attached the screenshots and the part of the syslog inherent to the network adapter.
comment:5 by , 14 years ago
I also had a look in the folder "boot/common/setting/network" at the file resolv.conf: Immediatly after startup the file is correctly set.. Seems that the "apply" button is not checked by default or similar.. As I've said, at every startup i have to click on the apply button in the network prefs, nevertheless the network applet has the green signal, and the eth cards the right addresses..
comment:6 by , 14 years ago
comment:7 by , 14 years ago
Do you see this behavior on both computers or only one, and which one then?
comment:8 by , 14 years ago
Hi phoudoin,
i saw this behaviour (dhcp correctly work on hrev40576) on second desktop computer (with nforce and rt8139) and on virtualbox. I have not tested the first desktop computer.
with later nightly versions of Haiku the problem is back on all pc's (included virtualbox).
Regards.
comment:9 by , 14 years ago
comment:10 by , 14 years ago
Hi, since r1a3 branch (now i'm using hrev41595 ) DHCP seems to work immediatly, without trouble!
comment:11 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Thanks for reporting. I'm closing the ticket.
If the issue comes back or is still there, we can always reopen it...
I can confirm it happening with an nforce since... well, forever, though it happens seldom and only on startup. Don't know how to reproduce it, sorry, it looks like a hit and miss bug to me.