LINUX: dsl-connection crashes after short time

Hallo all,

I am using a linux router, initially it was an 1Ghz athlon, wich i now
replaced
with a 233Mhz PI, which still has enough power to setup a DSL connection
and route
the traffic from a windows machine behind.

On the fast machine, sometimes the DSL connection broke down, let's say 5
times a week or
something (descr. below). Now, with the 'slow' machine, (uses the same
network cards) this
happens allready after an hour.

To get the DSL running again, I need to reboot the router. Just restarting
the network
(/etc/init.d/network restart) doesn't help. (a ping results in "no route
to host")

The most importand thing can be found in the log-files:

from /var/log/messages:

Oct 2 22:35:19 minilinux pppd[608]: No response to 4 echo-requests
Oct 2 22:35:19 minilinux pppd[608]: Serial link appears to be
disconnected.
Oct 2 22:35:20 minilinux pppd[608]: Setting MTU to 1492.
Oct 2 22:35:20 minilinux pppd[608]: Couldn't increase MRU to 1500
Oct 2 22:35:23 minilinux modify_resolvconf: restored
/etc/resolv.conf.saved.by.pppd.ppp0 to /etc/resolv.conf
Oct 2 22:35:24 minilinux pppd[608]: Connection terminated.
Oct 2 22:35:24 minilinux pppd[608]: Connect time 61.6 minutes.

The MRU - line does not seem to be the problem, since a lot of poeple seem
to have that
in their messages files without problems.

Any Ideas why this happens?

THANKA ALOT!
cr

PS
sorry for crossposting....

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Christian Rummey <(E-Mail Removed)> wrote:

> Hallo all,

> I am using a linux router, initially it was an 1Ghz athlon, wich i now
> replaced
> with a 233Mhz PI, which still has enough power to setup a DSL connection
> and route
> the traffic from a windows machine behind.

> On the fast machine, sometimes the DSL connection broke down, let's say 5
> times a week or
> something (descr. below). Now, with the 'slow' machine, (uses the same
> network cards) this

Sounds like a faulty NIC, I'd exchange it.

--
Michael Heiming

Remove +SIGNS and www. if you expect an answer, sorry for
inconvenience, but I get tons of SPAM

On Thu, 02 Oct 2003 23:29:55 +0200, Christian Rummey wrote:

>
> Hallo all,
>
> I am using a linux router, initially it was an 1Ghz athlon, wich i now
> replaced
> with a 233Mhz PI, which still has enough power to setup a DSL connection
> and route
> the traffic from a windows machine behind.
>
> On the fast machine, sometimes the DSL connection broke down, let's say 5
> times a week or
> something (descr. below). Now, with the 'slow' machine, (uses the same
> network cards) this
> happens allready after an hour.
>
> To get the DSL running again, I need to reboot the router. Just restarting
> the network
> (/etc/init.d/network restart) doesn't help. (a ping results in "no route
> to host")
>
> The most importand thing can be found in the log-files:
>
> from /var/log/messages:
>
> Oct 2 22:35:19 minilinux pppd[608]: No response to 4 echo-requests
> Oct 2 22:35:19 minilinux pppd[608]: Serial link appears to be
> disconnected.
> Oct 2 22:35:20 minilinux pppd[608]: Setting MTU to 1492.
> Oct 2 22:35:20 minilinux pppd[608]: Couldn't increase MRU to 1500
> Oct 2 22:35:23 minilinux modify_resolvconf: restored
> /etc/resolv.conf.saved.by.pppd.ppp0 to /etc/resolv.conf
> Oct 2 22:35:24 minilinux pppd[608]: Connection terminated.
> Oct 2 22:35:24 minilinux pppd[608]: Connect time 61.6 minutes.
>
> The MRU - line does not seem to be the problem, since a lot of poeple seem
> to have that
> in their messages files without problems.
>
> Any Ideas why this happens?
>
> THANKA ALOT!
> cr
>
> PS
> sorry for crossposting....

Your answer's right there:
the remote end failed to reply 4 times , so the daemon is assuming that
the link is dead. Now what would cause the remote pppoe server to not
respond? There are several things. A few most probable causes:

network card or modem's pc-modem interface's dead.
Does the modem's lights indicate that the modem-PC link is active? ( light
should be on.)


2. You lost dsl sync. ( flashing "sync" or "dsl" or "ATM" light? )

3. Remote end had some problem.

Regarding the MTU thing, it is always a good idea to minimize the number
of "incorrect, but it's ok" on a system that's not behaving as it should.

Find your pppoe.conf file, and change corresponding parameter to:
CLAMPMSS=1412

mine's running on a p100. so your 233 shouldn't have any problems.

Thanks to Joseph and Michael,

it was definitely the NIC. I tried 3 differet cards, but all with the same
driver (8193too) and
always had the same problem, now I took an very outdated onboard Intel
(ether express pro) Chip
with the the e100 driver and do not have any problems any more. It now ran
for allmost a day without
any loss of the connection.

So if anyone experiences a similar problem, I think he should blame the
driver, not the card.

Thanks again,
christian


On Thu, 02 Oct 2003 23:29:55 +0200, Christian Rummey
<(E-Mail Removed)> wrote:

>
> Hallo all,
>
> I am using a linux router, initially it was an 1Ghz athlon, wich i now
> replaced
> with a 233Mhz PI, which still has enough power to setup a DSL connection
> and route
> the traffic from a windows machine behind.
>
> On the fast machine, sometimes the DSL connection broke down, let's say
> 5 times a week or
> something (descr. below). Now, with the 'slow' machine, (uses the same
> network cards) this
> happens allready after an hour.
>
> To get the DSL running again, I need to reboot the router. Just
> restarting the network
> (/etc/init.d/network restart) doesn't help. (a ping results in "no route
> to host")
>
> The most importand thing can be found in the log-files:
>
> from /var/log/messages:
>
> Oct 2 22:35:19 minilinux pppd[608]: No response to 4 echo-requests
> Oct 2 22:35:19 minilinux pppd[608]: Serial link appears to be
> disconnected.
> Oct 2 22:35:20 minilinux pppd[608]: Setting MTU to 1492.
> Oct 2 22:35:20 minilinux pppd[608]: Couldn't increase MRU to 1500
> Oct 2 22:35:23 minilinux modify_resolvconf: restored
> /etc/resolv.conf.saved.by.pppd.ppp0 to /etc/resolv.conf
> Oct 2 22:35:24 minilinux pppd[608]: Connection terminated.
> Oct 2 22:35:24 minilinux pppd[608]: Connect time 61.6 minutes.
>
> The MRU - line does not seem to be the problem, since a lot of poeple
> seem to have that
> in their messages files without problems.
>
> Any Ideas why this happens?
>
> THANKA ALOT!
> cr
>
> PS
> sorry for crossposting....
>



--
Dr. Christian Rummey
registered linux user #92917