Opened 5 days ago

Last modified 4 hours ago

#19139 new bug

No hostname resolution after disabling and re-enabling interface

Reported by: Morgul Owned by: axeld
Priority: normal Milestone: Unscheduled
Component: Servers/net_server Version: R1/beta5
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

I don't know if this happens only with my hardware. I'm running up-to-date Haiku R1/beta5 x86_64, hrev57937+118 on real hardware (not a virtual machine).

I'm connecting to the Internet with an ethernet connection, it works perfectly and resolves hostnames without any issue. But following the next steps name resolution stops working.

Steps to reproduce, waiting a few seconds between each step:

  • Disconnect the ethernet cable
  • Disable the network interface
  • Enable the network interface
  • Connect the ethernet cable
  • The interface changes to "configuring" status and stays on it for a much longer time than usual, but it gets an IP address
  • The Internet works, but name resolution doesn't and it never works again until a reboot

If I do the same steps without disabling the network interface or without disconnecting the cable, it works as expected, resolving names without an issue.

Device information on listdev, it appears twice:

device Network controller (Ethernet controller) [2|0|0]
  vendor 14e4: Broadcom Inc. and subsidiaries
  device 16b1: NetLink BCM57781 Gigabit Ethernet PCIe

Related listimage entry:

 7516 0xffffffff82639000 0xffffffff82666000     0          0 /boot/system/add-ons/kernel/drivers/dev/net/broadcom570x

Attachments (1)

syslog.txt (4.5 KB ) - added by Morgul 5 days ago.
syslog extract. As far as I can tell, full syslog doesn't add any more information except showing how the interface goes down, up, and tries to get DHCP successfully again

Download all attachments as: .zip

Change History (7)

by Morgul, 5 days ago

Attachment: syslog.txt added

syslog extract. As far as I can tell, full syslog doesn't add any more information except showing how the interface goes down, up, and tries to get DHCP successfully again

comment:1 by waddlesplash, 5 days ago

Is there a Gateway or DNS set in the Network preferences?

comment:2 by diver, 5 days ago

Component: Network & InternetServers/net_server
Owner: changed from nobody to axeld

comment:3 by vidrep, 5 days ago

9386 and 9695 are old tickets describing the same problem.

in reply to:  1 ; comment:4 by Morgul, 4 hours ago

Replying to waddlesplash:

Is there a Gateway or DNS set in the Network preferences?

Do you mean if I set a gateway or DNS manually? No, they're set through DHCP.

I'll follow the steps to reproduce the issue and will let you know if they're still set after it happens.

in reply to:  3 comment:5 by Morgul, 4 hours ago

Replying to vidrep:

9386 and 9695 are old tickets describing the same problem.

Ticket 9386 seems to be completely unrelated.

Ticket 9695 could be related, I can't know.

in reply to:  4 comment:6 by Morgul, 4 hours ago

Replying to Morgul:

Replying to waddlesplash:

Is there a Gateway or DNS set in the Network preferences?

Do you mean if I set a gateway or DNS manually? No, they're set through DHCP.

I'll follow the steps to reproduce the issue and will let you know if they're still set after it happens.

After the issue happens, I saw that the two DNS I had remained, but the gateway was gone.

And by the way, this is name resolution error that was reported:

~> ping www.google.com
ping: cannot resolve www.google.com: Temporary failure in name resolution
Note: See TracTickets for help on using tickets.