Have you tried diald?  Diald is designed for exactly this kind of situation.

It will log source /destination address/port for every packet going over the
link if you wish so you can identify the culprit.

It also has a very flexible filter to determine which packets will bing up the
link or hold it up if it is up� with different timeouts for different types of
traffic.  Ie. web traffic could hold the line up for 20 mins, but emails could
take the line down again 20 seconds after the smtp connection closed.

On Sun, Dec 19, 1999 at 12:03:10PM +0200, John Anderson wrote:
> 
> I have pppd 2.3.10 and 2.2.13 kernels doing dial-on-demand + IP 
> Masquerading for a couple of small networks. The problem is that inevitably 
> one of the users on the network will install some networking software (ICQ, 
> PeopleLink, whatever) that causes pppd to dial out and keep the line up. 
> What I normally do is use ipchains to REJECT requests to/from certain IP 
> addresses and ports. That works nicely. The tricky part is figuring out 
> which IP addresses / ports are causing the problem.
> 
> It's not DNS packets. I've configured the machines as small-time DNS 
> servers - which obviously do cause the line to go up occasionally but 
> that's fine. I've set named's heartbeat so that it does housekeeping about 
> once a day.
> 
> What I'm looking for is a way to log the source & destination IP addresses 
> & ports for packets that are causing the line to go up. I had a quick look 
> at demand.c but I couldn't see anywhere obvious to put code to do this kind 
> of logging.
> 
> Any ideas? Pointers? Suggestions?
> 
> bye
> John
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]

Reply via email to