Hi all,
some times ago I met this problem, related to possible MAC address
collision using if_epair(4).
I'm not the first one encountering this issue and 2 PR [1][2] are already
filled.
There is also a differential review in phabricator [3] that unfortunately
shows no progress.
Following the app
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671
Luca Pizzamiglio changed:
What|Removed |Added
URL||https://reviews.freebsd.org
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=176671
Luca Pizzamiglio changed:
What|Removed |Added
CC||pizza...@freebsd.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #24 from zjk ---
hw.re.msi_disable hw.re.msix_disable
I tested this solution for a few days (it already exists somewhere on the
internet).
There is no visible effect (on my computers) - network is closing very quickly.
But - ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #25 from zjk ---
hw.re.msi_disable hw.re.msix_disable
I tested this solution for a few days (it already exists somewhere on the
internet).
There is no visible effect (on my computers) - network is closing very quickly.
But - ma
On Thu, May 03, 2018 at 02:11:24PM -0700, Dieter BSD wrote:
> > 10.3-RELEASE
[...]
> pyunyh> Which phy driver is used for axge(4)?
> pyunyh> You can see the phy driver name below axge(4) attachment in dmesg
> pyunyh> output.
>
> axge0: on usbus2
> axge1: on usbus0
> miibus4:
> on axge0
>
