Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Neighbour\s+Table\s+Overflow\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Neighbour\s+Table\s+Overflow\s*$/: 16 ]

Total 16 documents matching your query.

1. neighbour table overflow (score: 1): Author: xxxxxxx; Date: Wed, 8 Nov 2000 12:19:55 -0600; I've recently been directed to this list by Alan Cox, after having some trouble with a Linux Samba server having to many connections. When reaching 1025 arp entries(arp -a -n | wc -l), I get neighbou; /archives/netdev/2000-11/msg00047.html (8,254 bytes)
2. Re: neighbour table overflow (score: 1): Author: xxxxxx>; Date: Wed, 8 Nov 2000 19:58:38 +0000 (GMT); I seem to recall something somewhere about running a userspace arpd, which could presumably remove your limitations. [pauses while rummaging in docs] It's marked as obsolete in the kernel (damn!) and; /archives/netdev/2000-11/msg00049.html (8,598 bytes)
3. Re: neighbour table overflow (score: 1): Author: xxxxxx>; Date: Thu, 9 Nov 2000 09:22:28 +0200; try do this as root: The default value of this threshold is 1024 and this is the max size of the arp table. -- Gleb.; /archives/netdev/2000-11/msg00054.html (9,410 bytes)
4. Neighbour Table Overflow (score: 1): Author: w@xxxxxxxxxxxx>; Date: Wed, 15 Nov 2000 13:33:20 -0600 (CST); I've been running some tests on an x86 Linux based router with basically an AMD 486 DX4-100 processor and two PCNet32 ethernet controllers. The kernel on the router is 2.2.17 with "optimize as router; /archives/netdev/2000-11/msg00089.html (8,003 bytes)
5. Re: Neighbour Table Overflow (score: 1): Author: xxxxxxxxxxxxxx>; Date: Wed, 15 Nov 2000 21:33:59 GMT; I have noticed something like this which seems to be related to the ARP cache entry expiring and so the packet can not be delivered. This usually happens somewhere between 12 and 15 seconds. If you h; /archives/netdev/2000-11/msg00090.html (9,415 bytes)
6. Re: Neighbour Table Overflow (score: 1): Author: @xxxxxxxxxxxxx>; Date: Wed, 15 Nov 2000 16:39:07 -0600 (CST); But why is the re-arp taking so long? And I thought ARP entries lived much longer than 15 seconds, more like a couple of minutes. Can the time be changed? That's still not the solution, certainly. D; /archives/netdev/2000-11/msg00091.html (8,273 bytes)
7. Re: Neighbour Table Overflow (score: 1): Author: xxxxxxxxxxxxxx>; Date: Thu, 16 Nov 2000 13:17:16 -0600 (CST); I tried hardcoding the ARP entries in using arp -s, however the problem still presents itself. The unit appears to halt all network activity for perhaps another 15-20 seconds before resuming operati; /archives/netdev/2000-11/msg00097.html (8,038 bytes)
8. Re: Neighbour Table Overflow (score: 1): Author: xxxxxxxxxxxxxx>; Date: Thu, 16 Nov 2000 21:21:00 GMT; Nope, in our test we are blasting packets at the box and they are expiring (or dropping). It turns out that the device that I was using for testing only replies to arp at the beginning of the test (; /archives/netdev/2000-11/msg00098.html (9,845 bytes)
9. neighbour table overflow (score: 1): Author: "Thompson, Robert Aubrey" <UCS_RAT@xxxxxxxxxxxxxxxx>; Date: Wed, 8 Nov 2000 12:19:55 -0600; I've recently been directed to this list by Alan Cox, after having some trouble with a Linux Samba server having to many connections. When reaching 1025 arp entries(arp -a -n | wc -l), I get neighbou; /archives/netdev/2000-11/msg00181.html (8,254 bytes)
10. Re: neighbour table overflow (score: 1): Author: Peter Denison <peterd@xxxxxxxxxxxxxxxxxx>; Date: Wed, 8 Nov 2000 19:58:38 +0000 (GMT); I seem to recall something somewhere about running a userspace arpd, which could presumably remove your limitations. [pauses while rummaging in docs] It's marked as obsolete in the kernel (damn!) and; /archives/netdev/2000-11/msg00183.html (8,659 bytes)
11. Re: neighbour table overflow (score: 1): Author: Gleb Natapov <gleb@xxxxxxxxxxx>; Date: Thu, 9 Nov 2000 09:22:28 +0200; try do this as root: The default value of this threshold is 1024 and this is the max size of the arp table. -- Gleb.; /archives/netdev/2000-11/msg00188.html (9,545 bytes)
12. Neighbour Table Overflow (score: 1): Author: Mark Spencer <markster@xxxxxxxxxxxxxxxxx>; Date: Wed, 15 Nov 2000 13:33:20 -0600 (CST); I've been running some tests on an x86 Linux based router with basically an AMD 486 DX4-100 processor and two PCNet32 ethernet controllers. The kernel on the router is 2.2.17 with "optimize as router; /archives/netdev/2000-11/msg00223.html (8,003 bytes)
13. Re: Neighbour Table Overflow (score: 1): Author: Frank Byrum <greatbridge.com@xxxxxxxxxxxxx>; Date: Wed, 15 Nov 2000 21:33:59 GMT; I have noticed something like this which seems to be related to the ARP cache entry expiring and so the packet can not be delivered. This usually happens somewhere between 12 and 15 seconds. If you h; /archives/netdev/2000-11/msg00224.html (9,509 bytes)
14. Re: Neighbour Table Overflow (score: 1): Author: Mark Spencer <markster@xxxxxxxxxxxxxxxxx>; Date: Wed, 15 Nov 2000 16:39:07 -0600 (CST); But why is the re-arp taking so long? And I thought ARP entries lived much longer than 15 seconds, more like a couple of minutes. Can the time be changed? That's still not the solution, certainly. D; /archives/netdev/2000-11/msg00225.html (8,298 bytes)
15. Re: Neighbour Table Overflow (score: 1): Author: Mark Spencer <markster@xxxxxxxxxxxxxxxxx>; Date: Thu, 16 Nov 2000 13:17:16 -0600 (CST); I tried hardcoding the ARP entries in using arp -s, however the problem still presents itself. The unit appears to halt all network activity for perhaps another 15-20 seconds before resuming operati; /archives/netdev/2000-11/msg00231.html (8,063 bytes)
16. Re: Neighbour Table Overflow (score: 1): Author: Frank Byrum <greatbridge.com@xxxxxxxxxxxxx>; Date: Thu, 16 Nov 2000 21:21:00 GMT; Nope, in our test we are blasting packets at the box and they are expiring (or dropping). It turns out that the device that I was using for testing only replies to arp at the beginning of the test (; /archives/netdev/2000-11/msg00232.html (9,939 bytes)

Current List: 1 - 16
Page: [1]