On Mon, Jan 07, 2002 at 03:42:56PM +0100, Ralf Dreibrodt wrote:
> > yeah, that looks nice, but who'd run a 2.4.6 these days???
> > dammit, i don't really want to patch 2.2.20 or 2.4.17 myself
> i use the patch with a 2.4.16.
> some parts of the patch failed (after the lids patch), it took less than
On Mon, Jan 07, 2002 at 03:42:56PM +0100, Ralf Dreibrodt wrote:
> > yeah, that looks nice, but who'd run a 2.4.6 these days???
> > dammit, i don't really want to patch 2.2.20 or 2.4.17 myself
> i use the patch with a 2.4.16.
> some parts of the patch failed (after the lids patch), it took less tha
Hi,
> > There is a tool set, including a Linux kernel patch: UserIPacct
> > (http://ramses.smeyers.be/homepage/useripacct/). But I do not know how
> > stable it is. Besides, the last patch is for 2.4.6 and I need a more
> > up-to-date 2.4 kernel.
>
> yeah, that looks nice, but who'd run a 2.4.6 t
also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.07.0244 +0100]:
> The big problem are the ssh shell accounts. The user can start almost any
> program that listens on a socket. You wouldn't have log files from this
> program and you can only account the outgoing traffic with iptables.
well
(i have started a thread on this on debian-isp btw.)
also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.07.0244 +0100]:
> There is one problem with this: the module that matches user IDs
> can only be used in the OUTPUT chain (as said in the netfilter how-to).
oh man, this sucks!
> The bi
Hi,
> > There is a tool set, including a Linux kernel patch: UserIPacct
> > (http://ramses.smeyers.be/homepage/useripacct/). But I do not know how
> > stable it is. Besides, the last patch is for 2.4.6 and I need a more
> > up-to-date 2.4 kernel.
>
> yeah, that looks nice, but who'd run a 2.4.6
also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.07.0244 +0100]:
> The big problem are the ssh shell accounts. The user can start almost any
> program that listens on a socket. You wouldn't have log files from this
> program and you can only account the outgoing traffic with iptables.
wel
(i have started a thread on this on debian-isp btw.)
also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.07.0244 +0100]:
> There is one problem with this: the module that matches user IDs
> can only be used in the OUTPUT chain (as said in the netfilter how-to).
oh man, this sucks!
> The b
You may find the Debian package ipac-ng very useful if you don't want to
write your own scripts to handle all the ip accounting.
I don't think it'll do per-user on a single host (what can?!?) but
certainly per-ip.
--
Craig Ringer
IT Manager, POST Newspapers
http://www.postnewspapers.com.au/
You may find the Debian package ipac-ng very useful if you don't want to
write your own scripts to handle all the ip accounting.
I don't think it'll do per-user on a single host (what can?!?) but
certainly per-ip.
--
Craig Ringer
IT Manager, POST Newspapers
http://www.postnewspapers.com.au/
On Sun, 6 Jan 2002, martin f krafft wrote:
> also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.06.1914 +0100]:
> > Does Debian (potato or woody) have tools to account IP traffic per user?
>
> iptables, as others have suggested.
>
> AFAIK, the recommended method of doing this is to create a
On Sun, 6 Jan 2002, martin f krafft wrote:
> also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.06.1914
>+0100]:
> > Does Debian (potato or woody) have tools to account IP traffic per user?
>
> iptables, as others have suggested.
>
> AFAIK, the recommended method of doing this is to create
also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.06.1914 +0100]:
> Does Debian (potato or woody) have tools to account IP traffic per user?
iptables, as others have suggested.
AFAIK, the recommended method of doing this is to create a chain for
every user or group of users that you intend
also sprach Matthias Juchem <[EMAIL PROTECTED]> [2002.01.06.1914
+0100]:
> Does Debian (potato or woody) have tools to account IP traffic per user?
iptables, as others have suggested.
AFAIK, the recommended method of doing this is to create a chain for
every user or group of users that you inte
iptables can log by gid and pid or you can use the user queue with iptables.
and log but I'm not sure it's a very clean method with some logging packets
...
Francois
Matthias Juchem writes:
Hi there.
Does Debian (potato or woody) have tools to account IP traffic per user?
Greeting,
M
On Sun, Jan 06, 2002 at 07:14:00PM +0100, Matthias Juchem wrote:
> Hi there.
>
> Does Debian (potato or woody) have tools to account IP traffic per user?
With iptables you can create rules to match different Users, you could
use this for accounting.
HTH&RUMH
--
PGP/GPG encrypted mail preferred
Hi there.
Does Debian (potato or woody) have tools to account IP traffic per user?
Greeting,
Matthias
iptables can log by gid and pid or you can use the user queue with iptables.
and log but I'm not sure it's a very clean method with some logging packets
...
Francois
Matthias Juchem writes:
> Hi there.
>
> Does Debian (potato or woody) have tools to account IP traffic per user?
>
> Gr
On Sun, Jan 06, 2002 at 07:14:00PM +0100, Matthias Juchem wrote:
> Hi there.
>
> Does Debian (potato or woody) have tools to account IP traffic per user?
With iptables you can create rules to match different Users, you could
use this for accounting.
HTH&RUMH
--
PGP/GPG encrypted mail preferre
Hi there.
Does Debian (potato or woody) have tools to account IP traffic per user?
Greeting,
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
20 matches
Mail list logo
