From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip ru ls trouble
Date: Mon, 06 Jun 2005 13:53:10 +0000 [thread overview]
Message-ID: <42A45546.6030607@trash.net> (raw)
In-Reply-To: <03619621.20050606145032@ibz.ru>
Evgeny Kushmanov wrote:
> When I do "ip ru ls" very often is nothing output, but sometime it
> output correct info
>
> root@prima:~# ip ru ls
> root@prima:~# ip ru ls
> root@prima:~# ip ru ls
> root@prima:~# ip ru ls
> root@prima:~# ip ru ls
> root@prima:~# ip ru ls
> root@prima:~# ip ru ls
> root@prima:~# ip ru ls
> 0: from all lookup local
> 1000: from 81.4.240.10 lookup TTK
> 1100: from 217.106.18.62 lookup TCNN
> 2000: from all fwmark 0x80 lookup PROXY
> 2500: from 81.4.241.0/24 to 195.151.0.0/16 lookup TTK
> .....
> 32766: from all lookup main
> 32767: from all lookup default
>
> How I can fix that ?
Are you using 2.4.29? If so you need to upgrade to 2.4.30. 2.4.29
leaks netlink sockets, which causes bind-clashes that confuse iproute.
Regards
Patrick
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-06-06 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 10:50 [LARTC] ip ru ls trouble Evgeny Kushmanov
2005-06-06 13:53 ` Patrick McHardy [this message]
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=42A45546.6030607@trash.net \
--to=kaber@trash.net \
--cc=lartc@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.