All of lore.kernel.org
 help / color / mirror / Atom feed
* Maintenance for POM-ng modules
@ 2006-12-06 20:48 Jan Engelhardt
  2006-12-07  3:08 ` Patrick McHardy
  0 siblings, 1 reply; 2+ messages in thread
From: Jan Engelhardt @ 2006-12-06 20:48 UTC (permalink / raw)
  To: Netfilter Developer Mailing List; +Cc: kaber

Hi,



connlimit:
As of r6652, it has been moved to external. I would like to see it in 
pomng again (or even mainline kernel).

XOR:
Removed as of r6598, reason: no maintainer. I am currently maintaining 
it in private, just for the fun of it.

unclean:
Also deleted as of r6598. I would like to revive this module since it 
will be useful to us.

So, given this short summary, I would like to take these three projects 
and bring them back into shape (they really don't need a lot fixing 
AFAICT).
What's the preferred procedure?



Thanks,
	-`J'
-- 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Maintenance for POM-ng modules
  2006-12-06 20:48 Maintenance for POM-ng modules Jan Engelhardt
@ 2006-12-07  3:08 ` Patrick McHardy
  0 siblings, 0 replies; 2+ messages in thread
From: Patrick McHardy @ 2006-12-07  3:08 UTC (permalink / raw)
  To: Jan Engelhardt; +Cc: kaber, Netfilter Developer Mailing List

Jan Engelhardt wrote:
> Hi,
> 
> connlimit:
> As of r6652, it has been moved to external. I would like to see it in 
> pomng again (or even mainline kernel).

IIRC it scans the conntrack table. This general opinion so far has
been that this should not be merged, but I'm personally not that
opposed since I don't really see a better way and the functionality
seems useful (and I don't really want to lecture people on whats bad
for them, it should just be documented).

> XOR:
> Removed as of r6598, reason: no maintainer. I am currently maintaining 
> it in private, just for the fun of it.

We definitely don't want to merge this :)

> unclean:
> Also deleted as of r6598. I would like to revive this module since it 
> will be useful to us.

This one is considered harmful by all netfilter developers and the
many bugs so far breaking totally legitimate behaviour proof this
right. This is also why it has been removed in 2.6.

> So, given this short summary, I would like to take these three projects 
> and bring them back into shape (they really don't need a lot fixing 
> AFAICT).
> What's the preferred procedure?

For patches that we don't want to merge but see some use in, an
external pom repository is prefered. Its basically a tar of the
patchlet directory with repository: changed to "external" in the
info file. So for the connlimit match feel free so send me a URL
for an external repository or convince me that it should be
merged, the others should probably just be deleted :)

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-12-07  3:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-06 20:48 Maintenance for POM-ng modules Jan Engelhardt
2006-12-07  3:08 ` Patrick McHardy

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.