https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156667
mar...@blazingdot.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193743
Sean Bruno changed:
What|Removed |Added
CC||sbr...@freebsd.org
Status
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=199174
--- Comment #11 from Sean Bruno ---
Did a couple of tests via iperf.
test 1
#1 set hw.em.txd="4096"
#2 set hw.em.rxd="4096"
#3 ran with TSO enabled
-- ran into hangs and debug output from watchdog as reporter and stated.
-- seems to happen
On Sun, May 3, 2015 at 6:17 PM, Barney Cordoba via freebsd-net <
freebsd-net@freebsd.org> wrote:
> Frankly I'm baffled by netmap. You can easily write a loadable kernel
> module that moves packets from 1 interface to another and hook in the
> firewall; why would you want to bring them up into user
Frankly I'm baffled by netmap. You can easily write a loadable kernel module
that moves packets from 1 interface to another and hook in the firewall; why
would you want to bring them up into user space? It's 1000s of lines of
unnecessary code.
On Sunday, May 3, 2015 3:10 AM, Raimundo S
Clarifying things for the sake of documentation:
To use the host stack, append a ^ character after the name of the interface
you want to use. (Info from netmap(4) shipped with FreeBSD 10.1 RELEASE.)
Examples:
"kipfw em0" does nothing useful.
"kipfw netmap:em0" disconnects the NIC from the usual
