https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Summary|NIC status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Igor Zabelin changed:
What|Removed |Added
CC||ig...@yandex.ru
--- Comment #31 fro
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #14 from Kajetan Staszkiewicz ---
The issues described here happen both on VM and hardware. I switched to testing
things on VMs because they reboot way faster. They do happen on hardware too.
--
You are receiving this mail bec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230571
Mark Linimon changed:
What|Removed |Added
CC||sbr...@freebsd.org
Keywor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #15 from Kajetan Staszkiewicz ---
No patch I fetched from HEAD made 11.2 fully stable, so yes, none "sounds like
fixing". But I think we are dealing here with two separate bugs.
One is really easy to trigger by just adding same
When ethernet is unplugged, the interface keeps its IP, and the default
route stays, so WiFi fails to become functional.
It is necessary to run 'ifconfig {iface} inet remove' before connecting
to WiFi.
How is this supposed to function, because regular user shouldn't be
required to run comma