[ale] PPP/DHCP conflict

[John Mills]

Jim -

Thanks - that makes sense. I looked with 'netstat -p' but didn't see the 
byte sucker.

'Lessons Learned':
1. Look at the traffic load when the link seems stalled (which I did),
2. Look more closely at the traffic with 'tcpdump' to close in (there's 
always a 'next time').

Regards.

  - Mills

On Sat, 27 Nov 2010, Jim Kinney wrote:

> Looks like the dhcp lease was expired and not able to renew. But there was a
> process that was still running with routes in place. Thus data coming in
> even though the IP was expired. A tcpdump on the ppp link would tell more.
>
> On Sat, Nov 27, 2010 at 7:55 PM, John Mills <johnmills at speakeasy.net> wrote:
>
>> ALErs -
>>
>> This afternoon I noticed that response of my dial-in PPP link had nearly
>> stopped while the data-rate log showed that my incoming link was running
>> almost 100% saturated even though I couldn't identify any task that
>> should have been pulling tons (well, pounds anyway) of incoming traffic. I
>> notice a number of log messages to the effect:
>>
>> Nov 27 07:57:34 muskrat dhcpcd[3140]: eth0: lease expired 342002 seconds
>> ago
>> Nov 27 07:57:34 muskrat dhcpcd[3140]: eth0: broadcasting for a lease
>> Nov 27 07:57:54 muskrat dhcpcd[3140]: eth0: timed out
...