25.02.2012 19:17, Eugene Grosbein пишет:
> 25.02.2012 02:00, Andrew Thompson пишет:
>> 2012/2/25 Eugene Grosbein :
>>> 25.02.2012 00:14, Eugene Grosbein пишет:
This problem occurs only when net.isr.direct=0/net.isr.direct_force=0.
And only when lagg1 has both ports up and running. And whe
25.02.2012 02:00, Andrew Thompson пишет:
> 2012/2/25 Eugene Grosbein :
>> 25.02.2012 00:14, Eugene Grosbein пишет:
>>> This problem occurs only when net.isr.direct=0/net.isr.direct_force=0.
>>> And only when lagg1 has both ports up and running. And when I use oversized
>>> pings.
>>> At the same t
2012/2/25 Eugene Grosbein :
> 25.02.2012 00:14, Eugene Grosbein пишет:
>> This problem occurs only when net.isr.direct=0/net.isr.direct_force=0.
>> And only when lagg1 has both ports up and running. And when I use oversized
>> pings.
>> At the same time, transit oversized pings go through this BRA
25.02.2012 00:14, Eugene Grosbein пишет:
> Hi!
>
> I've found that my PPPoE BRAS server gives 80% packet loss
> for fragmented pings against itself while no packet loss for transit
> fragmented pings same time.
> The problem vanishes if I do ONE of following:
>
> 1) disable indirect netisr mode,
Hi!
I've found that my PPPoE BRAS server gives 80% packet loss
for fragmented pings against itself while no packet loss for transit fragmented
pings same time.
The problem vanishes if I do ONE of following:
1) disable indirect netisr mode, e.g. set back sysctl net.isr.direct=1 AND
net.isr.direc
