[Bug 181741] [kernel] [patch] Packet loss when 'control' messages are present with large data (sendmsg(2))

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181741 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: ngie Date: Sat Apr 25 05:32:03 UTC 2015 New revision: 281974 URL: https://svnweb.freebsd.org/changeset/base/281974 Log: MFC r261550,r281354,r281355,r28

[Bug 194515] Fatal Trap 12 Kernel with vimage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194515 Kubilay Kocak changed: What|Removed |Added Status|New |Open Flags|

Re: net.inet.ip.forwarding impact on throughput

Thanks Navdeep, I figured there had to be more going on than just allowing packets across interfaces. With forwarding automatically disabling TSO/LRO that would entirely explain why my bandwidth throughput tests drop off significantly. *[image: userimage]Scott Larson[image: los angeles]

[Differential] [Commented On] D1944: PF and VIMAGE fixes

glebius added a comment. Recently Nikos has asked questions on kernel debugging. So, I guess, he is working. REVISION DETAIL https://reviews.freebsd.org/D1944 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: nvass-gmx.com, bz, zec, trociny, glebius, rodri

[Differential] [Commented On] D1944: PF and VIMAGE fixes

robak added a subscriber: robak. robak added a comment. Is there any update on these fixes? I've just happened to bump my 10.1-RELEASE into 10-STABLE and created few VIMAGE based jails. As soon as I stop any of them, and I can reproduce it every time, the host OS crashes. That makes the entire

[Bug 194515] Fatal Trap 12 Kernel with vimage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194515 Bartek Rutkowski changed: What|Removed |Added CC||ro...@freebsd.org --- Comment #

Re: bhyve with vlans - host and vm can't pass traffic

On 4/23/2015 11:26 AM, Matthew Grooms wrote: On 4/22/2015 8:34 PM, Scott O'Connell wrote: I tried your suggestions. I was successful in changing the vmhost01 bridge to include vlan100 and tap0, and in the vm (dev) binding the address directly to vtnet0. On the VMHOST: tap0: flags=8943 me

Re: should m_copyback possibly throw data away?

John-Mark Gurney wrote this message on Fri, Apr 24, 2015 at 11:11 -0700: > I would also be fine w/ documenting this behavior, though I'm sure > it'd be surprising to many that you'd have to check to make sure your > data was properly copied. Should have reviewed the m_copyback function before send

should m_copyback possibly throw data away?

I was reviewing m_copyback from some other code, and noticed that it does this: if (m0 == NULL) return; at the beginin... If you pass in a NULL mbuf, it will not copy any data in.. This is clearly to avoid panics, but at the same time, this means we'll have data loss... I

Re: net.inet.ip.forwarding is mysteriously set to 0

Hi, --- Original Message --- From: "Nikos Vassiliadis" Date: 24 April 2015, 19:46:42 > Hi, > > Just saw this. Can somebody re-produce this? > > > root@m4fh2:~ # sysctl net.inet.ip.forwarding > > net.inet.ip.forwarding: 1 > > root@m4fh2:~ # ifconfig bridge0 create > > root@m4fh2:~ # sysct

Re: net.inet.ip.forwarding is mysteriously set to 0

On 04/24/15 18:57, Paul Thornton wrote: Hi This happens when any interface is created if you've enabled forwarding with the sysctl and not using gateway_enable in rc.conf. It is easily fixed though. See this thread from January: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=403720+0+archive/

Re: net.inet.ip.forwarding is mysteriously set to 0

On 04/24/15 18:54, Gary Palmer wrote: On Sat, Apr 25, 2015 at 01:47:50AM +0900, Paul S. wrote: Can confirm that anything to do with netif restart on a forwarding interface also creates the same problem. On 4/25/2015 ?? 01:46, Nikos Vassiliadis wrote: Hi, Just saw this. Can somebody re-p

Re: net.inet.ip.forwarding is mysteriously set to 0

Hi This happens when any interface is created if you've enabled forwarding with the sysctl and not using gateway_enable in rc.conf. It is easily fixed though. See this thread from January: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=403720+0+archive/2015/freebsd-net/20150104.freebsd-net P

Re: net.inet.ip.forwarding is mysteriously set to 0

On Sat, Apr 25, 2015 at 01:47:50AM +0900, Paul S. wrote: > Can confirm that anything to do with netif restart on a forwarding > interface also creates the same problem. > > On 4/25/2015 ?? 01:46, Nikos Vassiliadis wrote: > > Hi, > > > > Just saw this. Can somebody re-produce this? > > > >> ro

Re: net.inet.ip.forwarding is mysteriously set to 0

Can confirm that anything to do with netif restart on a forwarding interface also creates the same problem. On 4/25/2015 午前 01:46, Nikos Vassiliadis wrote: Hi, Just saw this. Can somebody re-produce this? root@m4fh2:~ # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 root@m4fh2:~ # i

net.inet.ip.forwarding is mysteriously set to 0

Hi, Just saw this. Can somebody re-produce this? root@m4fh2:~ # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 root@m4fh2:~ # ifconfig bridge0 create root@m4fh2:~ # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 0 That's on GENERIC 10-STABLE from the day before yesterday. Tha

Re: CARP vhid: across interfaces?

On 01.01.2015 18:29, Aristedes Maniatis wrote: > At any rate what does "interface groups that the carp(4) interface is a > member of" mean? FreeBSD has interface groups. Any interface may be a member of one or multiple groups, you can manually insert interface into a group, list groups etc. See