From: "Peter Pan" <osaka@gmx.net>
To: <gentoo-user@lists.gentoo.org>
Subject: AW: [gentoo-user] ARP-Caching of non-link-local adresses
Date: Wed, 4 Jan 2012 19:54:07 +0100 [thread overview]
Message-ID: <000001cccb12$3d6375c0$b82a6140$@gmx.net> (raw)
In-Reply-To: <CAA2qdGV4JRy0WzHgrUgXKH3kdKObvuoO8NpU63Y=T1E3AONNyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 7665 bytes --]
Hi,
This is quite a large list with lots of hosts, but even grep –v the larger /24-ones leaves the arp-table up to 10.000…
I’ve also heared (but never understood), that the lo-interface should be up and running. This is true in this case, but I noticed, the routes for 127.0.0.1 are missing in some tables.
I slightly doubt, that this is the root-cause for the exploding arp-cache, but I though it’s worth mentioning.
Thanks for your help, and regards,
here is the output:
host ~ # ip rule sh
0: from all lookup local
32717: from 192.168.254.0/24 lookup wlan
32718: from 192.168.1.30 lookup dmz
32719: from 192.168.1.129 lookup dmz
32720: from 192.168.1.118 lookup dmz
32721: from 192.168.1.117 lookup dmz
32722: from 192.168.1.106 lookup owa
32723: from 192.168.1.105 lookup dmz
32724: from 192.168.1.103 lookup dmz
32725: from 192.168.1.100 lookup dmz
32726: from 192.168.1.99 lookup dmz
32727: from 192.168.1.76 lookup dmz
32728: from 192.168.1.56 lookup dmz
32729: from 192.168.1.48 lookup dmz
32730: from 192.168.1.39 lookup dmz
32731: from 192.168.1.25 lookup dmz
32732: from 192.168.1.24 lookup dmz
32733: from 192.168.1.23 lookup dmz
32734: from 213.XXX.143.128/26 lookup dmz
32735: from 213.XXX.141.96/27 lookup dmz
32736: from 213.XXX.140.0/27 lookup dmz
32737: from 89.XXX.XXX.0/24 lookup dmz
32738: from 10.23.47.0/24 lookup voip
32739: from 10.23.42.0/24 lookup vpn2
32741: from 192.168.1.0/24 lookup lan
32742: from 192.168.1.30 lookup dmz
32743: from 192.168.1.129 lookup dmz
32744: from 192.168.1.118 lookup dmz
32745: from 192.168.1.117 lookup dmz
32746: from 192.168.1.106 lookup owa
32747: from 192.168.1.105 lookup dmz
32748: from 192.168.1.103 lookup dmz
32749: from 192.168.1.100 lookup dmz
32750: from 192.168.1.99 lookup dmz
32751: from 192.168.1.76 lookup dmz
32752: from 192.168.1.56 lookup dmz
32753: from 192.168.1.48 lookup dmz
32754: from 192.168.1.39 lookup dmz
32755: from 192.168.1.25 lookup dmz
32756: from 192.168.1.24 lookup dmz
32757: from 192.168.1.23 lookup dmz
32758: from 213.XXX.XXX.128/26 lookup dmz
32759: from 213.XXX.XXX.96/27 lookup dmz
32760: from 213.XXX.XXX.0/27 lookup dmz
32761: from 89.XXX.XXX.0/24 lookup dmz
32762: from 10.23.47.0/24 lookup voip
32763: from 10.23.42.0/24 lookup vpn2
32765: from 192.168.1.0/24 lookup lan
32766: from all lookup main
32767: from all lookup default
table wlan
host ~ # ip route show table wlan
default dev ppp0 scope link
89.XXX.XXX.0/24 dev br0 scope link
127.0.0.0/8 dev lo scope link
192.168.1.0/24 dev lan scope link
192.168.51.0/24 via 89.XXX.XXX.82 dev br0
192.168.52.0/24 via 89.XXX.XXX.82 dev br0
192.168.53.0/24 via 89.XXX.XXX.82 dev br0
192.168.113.0/24 via 192.168.1.113 dev lan
192.168.254.0/24 dev wlan scope link
213.XXX.140.0/27 dev br0 scope link
213.XXX.141.96/27 dev br0 scope link
213.XXX.143.128/26 dev br0 scope link
table dmz
host ~ # ip route show table dmz
default dev br0 scope link
89.XXX.XXX.0/24 dev br0 scope link
127.0.0.0/8 dev lo scope link
192.168.1.0/24 dev lan scope link
192.168.7.0/24 dev tun0 scope link
192.168.9.0/24 dev tun0 scope link
192.168.20.0/24 dev tun1 scope link
192.168.42.0/24 dev tun1 scope link
192.168.51.0/24 via 89.XXX.XXX.82 dev br0
192.168.52.0/24 via 89.XXX.XXX.82 dev br0
192.168.53.0/24 via 89.XXX.XXX.82 dev br0
192.168.113.0/24 via 192.168.1.113 dev lan
192.168.254.0/24 dev wlan scope link
213.XXX.140.0/27 dev br0 scope link
213.XXX.141.96/27 dev br0 scope link
213.XXX.143.128/26 dev br0 scope link
table owa
host ~ # ip route show table owa
default dev br0 scope link
89.XXX.XXX.0/24 dev br0 scope link
127.0.0.0/8 dev lo scope link
192.168.1.0/24 dev lan scope link
192.168.7.0/24 dev tun0 scope link
192.168.9.0/24 dev tun0 scope link
192.168.20.0/24 dev tun1 scope link
192.168.42.0/24 dev tun1 scope link
192.168.51.0/24 via 89.XXX.XXX.82 dev br0
192.168.52.0/24 via 89.XXX.XXX.82 dev br0
192.168.53.0/24 via 89.XXX.XXX.82 dev br0
192.168.113.0/24 via 192.168.1.113 dev lan
213.XXX.140.0/27 dev br0 scope link
213.XXX.141.96/27 dev br0 scope link
213.XXX.143.128/26 dev br0 scope link
table voip
host ~ # ip route show table voip
default dev lan scope link
192.168.1.0/24 dev lan scope link
table vpn2
host ~ # ip route show table vpn2
192.168.1.0/24 dev lan scope link
213.XXX.140.0/27 dev br0 scope link
213.XXX.141.96/27 dev br0 scope link
213.XXX.143.128/28 dev br0 scope link
table lan
host ~ # ip route show table lan
default dev ppp0 scope link
46.137.XXX.148 dev br0 scope link
46.137.XXX.212 dev br0 scope link
62.52.XX.252 dev br0 scope link
62.XXX.14.0/24 dev br0 scope link
62.XXX.192.204 dev br0 scope link
78.46.XXX.24/29 dev br0 scope link
80.153.XX.139 dev br0 scope link
81.137.XX.94 dev br0 scope link
83.104.XXX.105 dev br0 scope link
89.XXX.XXX.0/24 dev br0 scope link
127.0.0.0/8 dev lo scope link
192.168.1.0/24 dev lan scope link
192.168.7.0/24 dev tun0 scope link
192.168.9.0/24 dev tun0 scope link
192.168.20.0/24 dev tun1 scope link
192.168.42.0/24 dev tun1 scope link
192.168.51.0/24 via 89.244.135.82 dev br0
192.168.52.0/24 via 89.244.135.82 dev br0
192.168.53.0/24 via 89.244.135.82 dev br0
192.168.113.0/24 via 192.168.1.113 dev lan
192.168.254.0/24 dev wlan scope link
193.XXX.6.130 dev br0 scope link
193.XXX.12.0/24 dev br0 scope link
193.XXX.13.0/24 dev br0 scope link
193.XXX.14.0/24 dev br0 scope link
195.XXX.161.250 dev br0 scope link
212.XXX.12.0/24 dev br0 scope link
213.XXX.33.0/24 dev br0 scope link
213.XXX.140.0/27 dev br0 scope link
213.XXX.141.96/27 dev br0 scope link
213.XXX.143.128/26 dev br0 scope link
table main
host ~ # ip route show table main
default via 89.XXX.XXX.3 dev br0
87.186.224.XX dev ppp0 proto kernel scope link src 79.194.124.XXX
89.XXX.XXX.0/24 dev br0 proto kernel scope link src 89.XXX.XXX.4
127.0.0.0/8 via 127.0.0.1 dev lo
134.44.XXX.0/24 dev lan proto kernel scope link src 134.44.XXX.102
192.168.1.0/24 dev lan proto kernel scope link src 192.168.1.110
192.168.2.0/24 dev mgm proto kernel scope link src 192.168.2.254
192.168.7.0/24 dev tun0 scope link
192.168.9.0/24 dev tun0 proto kernel scope link src 192.168.9.1
192.168.20.0/24 dev tun1 scope link
192.168.42.0/24 dev tun1 proto kernel scope link src 192.168.42.1
192.168.254.0/24 dev wlan proto kernel scope link src 192.168.254.254
213.XXX.140.0/27 dev br0 proto kernel scope link src 213.XXX.140.2
213.XXX.141.96/27 dev br0 proto kernel scope link src 213.XXX.141.126
213.XXX.143.128/26 dev br0 proto kernel scope link src 213.XXX.143.132
host ~ # ip route show table default
host ~ #
Von: Pandu Poluan [mailto:pandu@poluan.info]
Gesendet: Mittwoch, 4. Januar 2012 18:56
An: gentoo-user@lists.gentoo.org
Betreff: Re: [gentoo-user] ARP-Caching of non-link-local adresses
On Jan 4, 2012 11:20 PM, "Peter Pan" <osaka@gmx.net> wrote:
>
> Hi list,
>
----- >8 snip
Can you post the output of "ip rule sh"?
And for every table listed in the above, post the output of "ip route sh table $TABLENAME"?
Rgds,
[-- Attachment #2: Type: text/html, Size: 33460 bytes --]
prev parent reply other threads:[~2012-01-04 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 16:17 [gentoo-user] ARP-Caching of non-link-local adresses Peter Pan
2012-01-04 17:28 ` Pandu Poluan
2012-01-04 17:31 ` Pandu Poluan
2012-01-04 17:58 ` AW: " Peter Pan
2012-01-04 17:55 ` Pandu Poluan
2012-01-04 18:54 ` Peter Pan [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='000001cccb12$3d6375c0$b82a6140$@gmx.net' \
--to=osaka@gmx.net \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox