Closed grahamperrin closed 3 years ago
Also possibly DHCP no longer working for em(4) –
5.0
on FreeBSD14.0-CURRENT
; I'll proceed to test without networkgr …
Confirmed. HP EliteBook 8570p. A few days ago, without understanding the cause(s) of the issue, I began working around by configuring rc.conf(5) to use static addressing with the DHCP service of my router at home.
Today I reconfigured to use DHCP, after which service netif restart em0
did not gain a network address. Worked around by using networkmgr to manually connect.
I deleted the package, restarted, gained an address automatically.
Whilst I do not have GhostBSD (with OpenRC) on real hardware at the time of writing, https://bsd-hardware.info/?probe=4bfec050c1 (2021-05-01, limited lifetime) is for VirtualBox, with the default 82540EM Gigabit Ethernet Controller
virtualised.
Here, as far as I can tell, no problem.
@grahamperrin just to be clear those issues are is a booth on FreeBSD?
Correct:
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driven by re(4) is FreeBSD 13.0-RELEASE
on an Ergo Vista 631 notebook (sometimes known as Asus T12Ah or Pegatron T12Ah), circa 200882579LM Gigabit Network Connection (Lewisville)
driven by em(0) is FreeBSD 14.0-CURRENT
on an HP EliteBook 8570p notebook, circa 2013. Will it help if I make the issue reproducible, on either computer, with GhostBSD 13-RELEASE
? I can try to install it to a spare USB flash drive (16 GB Kingston DataTraveler G3, I know it will be slow, but I don't mind, for testing).
Will it helps if I make the issue reproducible, on either computer, with GhostBSD
13-RELEASE
? I can try to install it to a spare USB flash drive (16 GB Kingston DataTraveler G3, I know it will be slow, but I don't mind, for testing).
not really since they do not use the same thing to start the DHCP.
I was able to reproduce for GhostBSD and fix it. The only thing I do not use FreeBSD on desktop since I eat my own dog food.
I will test my fix for GhostBSD on my laptop.
this will fix the issue for GhostBSD https://github.com/ghostbsd/networkmgr/releases/tag/5.4
This morning's update should cover the problem for GhostBSD.
For FreeBSD, I will have to install it in one of my hardware, when I have time.
I think I have found a fix for FreeBSD I will need help for testing when it is ready.
Thanks, I'll help in that.
This PR https://github.com/ghostbsd/networkmgr/pull/65 should fix the problem for FreeBSD.
This should do it for FreeBSD https://www.freshports.org/net-mgmt/networkmgr/
networkmgr-5.5 installed, wired network (em0) OK with a DHCP server following restart of FreeBSD 14.0-CURRENT.
Thank you, would you like to close this issue?
Yeah, it looks fix to me, and it has improved the GhostBSD boot process with networking.
Thanks for testing that for me.
re(4)
https://www.freshports.org/net-mgmt/networkmgr/ networkmgr
5.0
on FreeBSD13.0-RELEASE
withlatest
packages.With the package installed:
After deleting the package and restarting the system:
https://bsd-hardware.info/?probe=ce8d45af17
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driven by re(4).Comparisons
https://forums.ghostbsd.org/viewtopic.php?p=9437#p9437
Also possibly DHCP no longer working for em(4) –
5.0
on FreeBSD14.0-CURRENT
; I'll proceed to test without networkgr …