netisr 0 : %100 and other netisr threads are waiting

2014-04-03 Thread Özkan KIRIK
Hi, I am trying to use suricata on FreeBSD 10 amd64. FreeBSD behaves as a VLAN router and NAT Box. Traffic is about 400Mbps. When i diverted traffic to suricata, swi: netisr 0 thread gets %100 cpu. other netisr threads are %0. And Even I remove the divert rule, netisr still eats %100 cpu. I thin

Re: questions about (system) dhclient

2014-04-03 Thread Dave Duchscher
On Apr 1, 2014, at 10:29 AM, Robert Huff wrote: > > Synopsis of my (apparent) problem: DISCOVER, OFFER, REQUEST, > and ACKNOWLEDGEMENT all happen correctly ... but the information > doesn't make it to ifconfig or the routing table. Have you tried commenting everything out of dhclient.conf

net.inet.ip.random_id

2014-04-03 Thread George Rosamond
Sorry for the cross-post, but assume this is relevant to both lists. It's regarding the default setting of net.inet.ip.random_id to 0 This disclosure has caused a bit of a stir on the Tor-relays list starting with this post: https://lists.torproject.org/pipermail/tor-relays/2014-March/004199.htm

Re: miibus0: mii_mediachg: can't handle non-zero PHY instance 31

2014-04-03 Thread Chris H
> On Tue, Apr 01, 2014 at 05:53:51PM -0700, Chris H wrote: >> > On Tue, Apr 01, 2014 at 01:40:58PM -0700, Chris H wrote: >> >> > On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote: >> >> >> [...] >> >> >> miibus0: on nfe0 >> >> >> rlphy0: PHY 0 on miibus0 >> >> >> rlphy0: 10baseT, 10baseT-FDX, 100

More on the whole interruptless networking

2014-04-03 Thread Sean Fagan
I've made a series of diffs. I've only tested them in vmware fusion for now, so that's if_lem that gets involved. I need to track down a system with igb and try that; I'm much less sure of those changes than I am the if_em / if_lem changes. Note that, for various reasons, I used git for my so

Re: DCTCP implementation

2014-04-03 Thread hiren panchasara
On Thu, Apr 3, 2014 at 4:27 AM, Midori Kato wrote: > Hi Hiren, > > Yes, I intentionally replace the location of DELAY_ACK() macro. > A DCTCP receiver sends an immediate ACK when incoming packets sets CE and > non-CE bit by turns. To implement this processing, I prepare the > cc_ecnpkt_handler() fu

Re: DCTCP implementation

2014-04-03 Thread Midori Kato
Hi Hiren, Yes, I intentionally replace the location of DELAY_ACK() macro. A DCTCP receiver sends an immediate ACK when incoming packets sets CE and non-CE bit by turns. To implement this processing, I prepare the cc_ecnpkt_handler() function. This function calls the DEKAY_ACK() macro to check