Re: CONNLIMIT Questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[Netfilter v1.3.7, Linux 2.4.20, Tomato 1.23, Busybox v1.12.3, embedded in a WRT54GL router]

On 09  Jan 19, at 10:34 , Sitaram Chamarty wrote:

On 2009-01-18, Peter Renzland <peter@xxxxxxxxxxx> wrote:
1. Is REJECT any better than DROP?  (Will anything or anyone actually
get the reject message and learn anything from it?)

REJECT is better than DROP in the sense that the application
making the connection will get (and be able to pass back to
the user, presumably) a proper error message.  A DROP looks
like the packet didn't make it, and the program will not
report back to the user until some timeout or retry limit
finishes.

If (and that is the question) the reject-reason is indeed seen, then perhaps --reject-with icmp-admin-prohibited would be a clearer message to send than the default icmp-host-unreachable.

This raises some new questions, expanding the original (yet unresolved one) to:

1.1 will anyone or anything actually *get* and *use* the reject reason? (Especially PC users and their software, and especially BitTorrent users and BitTorrent clients.)

-- the iptables manual states that "Using icmp-admin-prohibited with kernels that do not support it will result in a plain DROP instead of REJECT". --
1.2 why does a message text need kernel support?

1.3 why "drop" instead "reject with reason unavailable"?

1.4 how does an iptables user determine whether such kernel support exists?




    But that is not at all what I want to do.   I want to restrict
the number of greatly *divergent* connections to many, many different
servers.

Perhaps there is a better (effective) way to limit connection attempts
by LAN IP?
In any direction and for any protocol.

You could take a look at the hashlimit and the limit
modules; one of those should do what you want.  I have no
used the hashlimit one so far, and the limit one only for
incoming connections, but they seem more general than
connlimit.

The central question that was never addressed was:

* The iptables manual page states that connlimit limits *incoming* *tcp* connections. I want to limit what overwhelmingly are outgoing UDP connections.

Thanks,
Peter Renzland

[Netfilter v1.3.7, Linux 2.4.20, Tomato 1.23, Busybox v1.12.3, embedded in a WRT54GL router]


--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux