Hi All,
I am sending packet between two back to back connected machine.when I
use same network (192.168.7.x) packet reach upto NF_IP_LOCAL_IN
(IPTABLES INPUT) hook.It is accepted.
But when I spoof ip address network(192.168.8.x) it pass
NF_IP_PRE_ROUTING hook but dropped before NF_IP_LOCAL_IN hoo
ps link or 10Gbps link i
> see a packet drop by kernel ( result of tcpdump -i eth2).How can i minimize
> the packet drop?
>
If you are referring to packet drop by tcpdump (when you ctrl-c it), this
packet is not dropped by kernel stack, but by tcpdump filter. For packets
dropped by stack
connected back to back.)
Query 2) When i run the packet generator on the 1Gbps link or 10Gbps link i
see a packet drop by kernel ( result of tcpdump -i eth2).How can i minimize
the packet drop?
Thanks
Clove
___
Kernelnewbies mailing list
Kernelnewbies
* On Sat, Dec 24, 2011 at 09:57:50PM +0530, Mukesh Yadav
wrote:
Hi Raghavendra,
" /proc/sys/net/core/bpf_jit_**enable " is not present on machine. Seems
kernel need to be configured for these.
Yes, it is a fairly new option -- CONFIG_BPF_JIT=y
Btw CPU scaling issue is resolv
Hi Raghavendra,
" /proc/sys/net/core/bpf_jit_**enable " is not present on machine. Seems
kernel need to be configured for these.
Btw CPU scaling issue is resolved. Packet drop was because all interrupt
handling was happening on core where packets were getting drop. Tuning
system for
9] &
>0x01 = 0'
>Odd IP filter :-> tcpdump -i interface 'ether dst && ip[19] &
>0x01 = 1'
>
>There is a packet loss for odd IP thread even when CPU is available. Reason
>being packet drop due recv buffer full.
>Same amount of traffic is well handle
Hi Mukesh
On Wed, Dec 21, 2011 at 12:25, Mukesh Yadav wrote:
> Thanks Mulyadi,
> Yeah that a final alternative. Actually I was looking for some optimized
> way of getting packet filtered at kernel level using BPF filter.
You're welcome. Logically, your code should have no problem, but well
it s
PF filters used are:
> > Even IP filter :-> tcpdump -i interface 'ether dst && ip[19] &
> > 0x01 = 0'
> > Odd IP filter :-> tcpdump -i interface 'ether dst && ip[19]
> &
> > 0x01 = 1'
> >
> > There is a p
0x01 = 1'
>
> There is a packet loss for odd IP thread even when CPU is available. Reason
> being packet drop due recv buffer full.
> Same amount of traffic is well handled by even IP thread(user code being
> same in both), scaling CPU to full 100%.
>
> In odd IP thread, If
filter :-> tcpdump -i interface 'ether dst && ip[19] &
0x01 = 0'
Odd IP filter :-> tcpdump -i interface 'ether dst && ip[19] &
0x01 = 1'
There is a packet loss for odd IP thread even when CPU is available. Reason
being packet drop due recv buff
10 matches
Mail list logo