Date: Sun, 08 Oct 2017 14:13:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Message-ID: <bug-217606-2472-rscUAoFWpf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #23 from punkt.de Hosting Team <mops@punkt.de> --- Hey guys, it hit us again in production. Saturday night, 4am. Sorry - I missed that DTrace diagnose, but I can add two things at least: We are using igb(4) interfaces in that machine, not ix(4), so it seems not = to be interface related. Doesn't come as a big surprise to me, because that wo= uld have been a gross layer violation. Again: the host system is communicating = just fine! I did a `netstat -m` while the bridge was wedged as suggested by gnn. Doesn= 't look suspicious at all to me, but then I'm not a kernel developer. Please s= ee attachment. What I am going to do now, probably: Set up an isolated test environment. Fire up some dozen jails or so. Generate artificial traffic through the bridge IF. A gigabit sustained bandwidth ... Wait for the bug to be triggered. Need to talk to my colleagues, tomorrow, but this will probably be our cour= se of action. I can offer ssh access to that isolated system to anyone who requests it! Kind regards Patrick --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217606-2472-rscUAoFWpf>