From: Roberto Nibali <ratz@tac.ch>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Developers <netfilter-devel@lists.netfilter.org>,
Patrick Schaaf <bof@bof.de>, Herve Eychenne <rv@wallfire.org>
Subject: Re: possible issues with blowing up struct ipt_log_info
Date: Mon, 04 Jul 2005 12:13:57 +0200 [thread overview]
Message-ID: <42C90BE5.7030102@tac.ch> (raw)
In-Reply-To: <20050704095351.GZ3186@sunbeam.de.gnumonks.org>
> Well, to be honest I'm happy that I can say - to a certain extend: I
> don't care abou your particular setup and it's political/organizational
> erstrictions ;) [don't get me wrong, please].
No, I understand and agree with you. You do the technical correctness of what
you implement and we deal with the correct architectural issues.
> As always, I think we should provide some infrastructure and let people
> use it how they want. We can try to be flexible, but we cannot optimize
> ever possible setup.
Never asked for that ;).
> Your particular setup would need something like a proxy that does the
> interpretation before it ends up at the centralized logging server.
We also have that (a proxy), but still, it's not that easy ... _but_ also
completely off-topic for this list.
> Alternatively you could store the hostname of the firewall and make the
> interpretation of such a prefix local to that host. Now you certainly
> can come up with a reason why you can't do that. And I can frankly
> repeat: well, that's your problem ;) Technically it is possible...
Yes, let's kill this part of the thread.
Cheers,
Roberto Nibali, ratz
--
-------------------------------------------------------------
addr://Rathausgasse 31, CH-5001 Aarau tel://++41 62 823 9355
http://www.terreactive.com fax://++41 62 823 9356
-------------------------------------------------------------
terreActive AG Wir sichern Ihren Erfolg
-------------------------------------------------------------
next prev parent reply other threads:[~2005-07-04 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 15:37 possible issues with blowing up struct ipt_log_info Roberto Nibali
2005-06-29 15:40 ` Patrick Schaaf
2005-06-29 16:08 ` Roberto Nibali
2005-06-29 16:09 ` Herve Eychenne
2005-07-01 7:08 ` Roberto Nibali
2005-07-03 12:36 ` Harald Welte
2005-07-03 22:05 ` Herve Eychenne
2005-07-04 5:55 ` Patrick Schaaf
2005-07-04 8:20 ` Roberto Nibali
2005-07-04 8:59 ` Harald Welte
2005-07-04 9:26 ` Roberto Nibali
2005-07-04 9:53 ` Harald Welte
2005-07-04 10:13 ` Roberto Nibali [this message]
2005-07-04 10:08 ` Herve Eychenne
2005-07-04 10:48 ` Roberto Nibali
2005-07-04 11:21 ` Herve Eychenne
2005-07-04 9:23 ` Herve Eychenne
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=42C90BE5.7030102@tac.ch \
--to=ratz@tac.ch \
--cc=bof@bof.de \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rv@wallfire.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 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.