[Bug 211962] bxe driver queue soft hangs and flooding tx_soft_errors

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211962 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org --- Comment #6

high interrupts on network load

I have a pair systems running relayd in DSR mode. The load balancer works well, to a point, but suffers from high interrupts and cpu utilization on eight cores. The monitoring systems show increased latency until it falls over dead at round 330k requests/sec where the CARP seems to stop responding

Re: NETGRAPH- bridge vlans using netgraph help

01.05.2018 1:03, Freddie Cash wrote: > On Mon, Apr 30, 2018 at 10:59 AM, Eugene Grosbein >wrote: > > > What the OP is trying to do is have PC1 send untagged packets to igb0 > on FreeBSD which is configured for tagged vlan 5. > > Then bridge the packets to igb1

Re: NETGRAPH- bridge vlans using netgraph help

On Mon, Apr 30, 2018 at 10:59 AM, Eugene Grosbein wrote: > 30.04.2018 23:46, Freddie Cash wrote: > > > What the OP is trying to do is have PC1 send untagged packets to igb0 on > FreeBSD which is configured for tagged vlan 5. > > Then bridge the packets to igb1 which is also configured for tagged

Re: ipfw -- selecting locally generated packets

01.05.2018 0:48, Jeff Kletsky wrote: > From time to time, I rewrite my firewall rules to take advantages of the > ever-improving set of features that ipfw provides. One of the challenges I > have faced in the past was selecting packets that are generated on the > firewall host itself, as oppose

Re: NETGRAPH- bridge vlans using netgraph help

30.04.2018 23:46, Freddie Cash wrote: > What the OP is trying to do is have PC1 send untagged packets to igb0 on > FreeBSD which is configured for tagged vlan 5. > Then bridge the packets to igb1 which is also configured for tagged vlan 5. > Then send the packets out, untagged, to PC2. Why wou

ipfw -- selecting locally generated packets

From time to time, I rewrite my firewall rules to take advantages of the ever-improving set of features that ipfw provides. One of the challenges I have faced in the past was selecting packets that are generated on the firewall host itself, as opposed to those that it received through an interf

Re: NETGRAPH- bridge vlans using netgraph help

On Sat, Apr 28, 2018 at 12:55 PM, Eugene Grosbein wrote: > 28.04.2018 21:57, Freddie Cash wrote: > > > If you want to think of it in switch terms, FreeBSD supports access > ports (untagged vlan) and trunk ports (tagged vlans). > > But there's no support for hybrid ports (tagged vlans with a PVID

[Bug 227720] Kernel panic in ppp server

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227720 --- Comment #10 from Eugene Grosbein --- GENERIC kernel has following line: makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols Add it to your kernel configuration file. It makes kernel build process to produc

[Bug 227720] Kernel panic in ppp server

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227720 --- Comment #9 from Matt Allanson --- (In reply to Eugene Grosbein from comment #8) Sorry for the late response, kernel.debug does not exist on any of our machines. -- You are receiving this mail because: You are the assignee for the bug

RE: kernel: in6_delayed_cksum: delayed m_pullup

Tom, I’m using the igb (intel I210) driver for my LAN interface and the em (intel I219-V) driver for the WAN interface. I use this FreeBSD box as my home server so I wouldn’t say that it has a heavy ipv6 workload. Regards, Dries From: Tom Jones Sent: zondag 29 april 2018 21:05 To: Dries Michi