Re: ngrep/ixgbe bpf bug

2015-12-01 Thread el...@sentor.se
Yes, 100% of the traffic is vlan-tagged, but I get the same results with: ngrep -d ix1 "q" vlan no matches If I invert the test to show all packets that do not contain "foobar", it still matches 0 packets: ngrep -d ix1 -v "foobar" ix1: no IPv4 address assigned: Can't assign requested addre

Re: ngrep/ixgbe bpf bug

2015-11-30 Thread Alexander V . Chernikov
Do you have vlans on top of ixgbe? And actually I wonder what does tcpdump show for the same expression. ( and tcpdump -i ixX -lnes0 might provide good traces on what is going on) 30.11.2015, 19:09, "el...@sentor.se" : > No one has a theory? > > /Elof > > On Thu, 5 Nov 2015, el...@sentor.se wrote:

Re: ngrep/ixgbe bpf bug

2015-11-30 Thread elof2
No one has a theory? /Elof On Thu, 5 Nov 2015, el...@sentor.se wrote: Hi all! Why don't ngrep work on ix interfaces? It shows nice values if I sniff on other interfaces, e.g. igb0 and bridge0: # ngrep -d igb0 "q" ip I see some matching packets. Everything looks good. # netstat -B Pid

ngrep/ixgbe bpf bug

2015-11-05 Thread elof2
Hi all! Why don't ngrep work on ix interfaces? It shows nice values if I sniff on other interfaces, e.g. igb0 and bridge0: # ngrep -d igb0 "q" ip I see some matching packets. Everything looks good. # netstat -B Pid Netif Flags Recv Drop Match Sblen Hblen Command 1800 ig