From: Matt <tank.en.mate@gmail.com>
To: Oleg Kutkov <elenbert@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network activity after route changes
Date: Sun, 18 Apr 2010 17:45:51 +0100 [thread overview]
Message-ID: <4BCB373F.4070400@gmail.com> (raw)
In-Reply-To: <4BCAE9BC.3090609@gmail.com>
On 18/04/10 12:15, Oleg Kutkov wrote:
> Hello.
> I try to send and receive ethernet packets on very low level in my
> kernel module.
> When i change (add or delete entry) routin table (via route command)
> my network is freeze for ~15 seconds and my application can't send and
> receive any packets.
> Is it normal or bug somewhere in my application?
> Can i change this behavior of route system? Maybe change some
> timeouts, or immediately flush route (rt_flush() ?) table?
Depending on your routing configuration the change may be causing the
problem. Have you tried flushing the route cache (as opposed to the main
routing table)?
# ip route flush table cache
matt
next prev parent reply other threads:[~2010-04-18 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 16:02 Network activity after route changes Oleg Kutkov
2010-04-18 11:15 ` Oleg Kutkov
2010-04-18 12:07 ` Eric Dumazet
2010-04-18 16:45 ` Matt [this message]
2010-04-19 8:14 ` Oleg Kutkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BCB373F.4070400@gmail.com \
--to=tank.en.mate@gmail.com \
--cc=elenbert@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.