| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH + RFC] neighbour/ARP cache scalability |
| From: | Tim Gardner <timg@xxxxxxx> |
| Date: | Tue, 21 Sep 2004 11:58:27 -0600 |
| Cc: | YOSHIFUJI Hideaki / ???????????? <yoshfuji@xxxxxxxxxxxxxx>, pekkas@xxxxxxxxxx, laforge@xxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040921173134.GC12132@wotan.suse.de> |
| Organization: | TriplePoint, Inc. |
| References: | <20040922.001448.73843048.yoshfuji@linux-ipv6.org> <Pine.LNX.4.44.0409211856260.9906-100000@netcore.fi> <20040922.010428.104988024.yoshfuji@linux-ipv6.org> <1095784761.3934.52.camel@tim.rtg.net> <20040921173134.GC12132@wotan.suse.de> |
| Reply-to: | timg@xxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 2004-09-21 at 11:31, Andi Kleen wrote: > But also allows an easy DOS. Someone just has to spoof a lot of connections > attempts with the source address of your primary name server or > some other important service. > That is what other iptables rules and filters are for. I get thousands of source address spoofs from my Internet connection every day. Network security is a layered approach. rtg -- timg@xxxxxxx http://www.tpi.com 406-443-5357(MT) 503-601-0234(OR) |
| Previous by Date: | Re: [PATCH + RFC] neighbour/ARP cache scalability, Andi Kleen |
|---|---|
| Next by Date: | Re: [PATCH + RFC] neighbour/ARP cache scalability, Andi Kleen |
| Previous by Thread: | Re: [PATCH + RFC] neighbour/ARP cache scalability, Andi Kleen |
| Next by Thread: | Re: [PATCH + RFC] neighbour/ARP cache scalability, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |