On 11/12/2016 07:54, dkle...@phy.ucsf.edu wrote:
I'm trying to setup a private testing environment using the bhyve
hypervisor and some virtual machines connected with tap interfaces
to a bridge. My network configuration for this environment looks like
this:
I have a bridge interface with 5 tap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196361
Alan Somers changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196361
--- Comment #9 from jhujh...@adjectivism.org ---
Created attachment 178192
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178192=edit
Respect net.add_addr_allfibs=0 for inet6 (revision 1)
I didn't forget about this! I
Hi Luigi,
I attached a minimal change containing two fixes:
- change IFNET_WLOCK into IFNET_RLOCK, to fix the cxgbe issue related
to this thread
- use the proper locking functions for the "worker_lock", unrelated
but needed to avoid the O.S. to trap because of a mismatch between
MTX_SPIN and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213115
Ed Maste changed:
What|Removed |Added
Status|New |Open
--- Comment
On Wed, Dec 21, 2016 at 11:15 AM, Vincenzo Maffione
wrote:
> Hi,
> There is no commit related to that in the FreeBSD svn or git.
>
> The fix has been published to the github netmap repository here
> (branch master): https://github.com/luigirizzo/netmap
>
> What we should
Hi,
There is no commit related to that in the FreeBSD svn or git.
The fix has been published to the github netmap repository here
(branch master): https://github.com/luigirizzo/netmap
What we should do is to import all the recent updates from the github
into HEAD. I can prepare a patch for
Dear netmap gurus,
I'm getting different crashes if using vale(4) as a drop in replacement
for if_bridge(4).
Before collecting dumps I'd like to know if the setup, which I need to
keep (including a MTU of 9000 bytes), is meant to be supported at all
with netmap.
Usually I have two GbE ports
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212283
--- Comment #19 from Mathieu Arnold ---
Still a problem with 11.0-RELEASE-p5.
--
You are receiving this mail because:
You are the assignee for the bug.
___