On Mon, Sep 06, 1999 at 09:00:47PM +0100, Nick Fisher wrote:
>
> I'm sharing a house with three other computer types, we have (naturally)
> networked our computers and are connecting to the internet via a RedHat 5.2
> box set up for masquerading and diald*. This is all very nice but we need to
> log the traffic to the internet so we can avoid arguing about the phone bill
> (Roll on cable modems... Whooo!). The fire wall provides primitive and messy
> logging but I was wondering could.... diald do better? What I realy need is
> a record of is the IP address on the intranet and the time, the rest I can
> do with macros or a bit of C.
Diald normally logs the connection start time, end time and bytes
transfered. It does not log the intranet IP which brings up the link.
The firewall, in fact, would provide much better logging than diald
since, once the connection is up, diald no longer cares about what goes
over the wire, but the firewall does.
It would certainly provide a record of the originating IP address and
the time.
If you could get diald to log the
requesting IP address, you'd be charging the person who brought up the
link rather than all the people who used the link.
I would recommend that you use the firewall (ipfwadm, I presume)rules
instead. To avoid logging every single packet, you might consider
logging only the initial connections, which have the syn bit set. This
is, of course, only true for TCP connections. To be thorough, you'd
have to log all UDP connections. Spreading the costs based on
originating IP is democratic, but makes no distinctions about bandwidth
usage.
You might want to look into the traffic shaper device. I think it may
provide some of the capabilities you seek.
--
Gyepi Sam --+-- Designer/Programmer --+-- Network/System Administrator
[EMAIL PROTECTED] --+-- http://www.praxis-sw.com/gyepi
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
