Lost connections and reboots with RP PPPoE

Hello everyone,

I've been using the Roaring Penguin PPPoE software for some time on a
couple of different systems. First on Mandrake 10, then Suse 9.1, and
now on an IpCop installation. What is happening is that on both the
Suse and the IpCop installations, after several days of running
flawlessly my connection will fail. Any attempts to reconnect via
software command are useless. The only way I can reconnect is after I
reboot the system, in which case it's again a couple of days before a
reboot is needed.

Of course this is a very vague set of circumstances (using two
different versions of RP-PPPoE), however I would like to find out why
it is happening. Any chance of monitoring the connection and determing
what is going on? What about a hidden switch command or something that
I can use to keep a log of error messages, or something? Fortunately
both Suse and IpCop have alternative solutions to Roaring Penguin's
PPPoE software, and I am using it on the IpCop installation now. But,
as I said earlier, I'd love to see what is going on behind the scenes.
What exactly is happening to shutdown the software so completely that I
have to reboot the system to get connection again.

Thanks for any input,

Dave

P.S. Please respond in thread.

P.P.S. ADSL modem is a SpeedStream 5360 on a dynamic SBC DSL
connection.

Dave

"Dave" <(E-Mail Removed)> wrote in news:1112389446.879116.290600
@g14g2000cwa.googlegroups.com:

> Thanks for any input,

I use

[root@ohmster pppoe]# rpm -q rp-pppoe
rp-pppoe-3.5-1

Had not luck at all ith 3.5-2. Just would not connect at all, but 3.5-1
works just fine, no problems, stays connected for days, weeks, months, etc.
Running redhat 9 system.

--
~Ohmster
ohmster at newsguy dot com