mtu 1492
lcp-echo-interval 30
noipx
And I've read the man pages several times but don't see a solution or
even a hint to what's happening.
The latest instance in the logs looks like this:
Mar 23 17:31:51 playground pppd[7752]: sent [LCP EchoReq id=0x4
magic=0x295e1973]
Mar 23 17:32
On Sun, Mar 23, 2014 at 12:00:55PM +1300, Chris Bannister wrote:
> Are you sure the line is OK? Check the Carrier Detect( CD) LED on the
> modem. If it's off, it can't "see" the modem at the other end.
Thanks for the thought Chris I'll check the light next time it happens.
Mike
--
When is it appr
[LCP EchoReq id=0x4
magic=0x84f3fde5]
Mar 22 16:04:49 playground pppd[20465]: Modem hangup
Mar 22 16:04:49 playground pppd[20465]: Connect time 2.5 minutes.
Mar 22 16:04:49 playground pppd[20465]: Sent 124 bytes, received 261 bytes.
In this case the hangup occurred 26 Seconds after the EchoRe
16:03:53 playground pppd[20465]: sent [LCP EchoReq id=0x3
magic=0x84f3fde5]
Mar 22 16:03:53 playground pppd[20465]: rcvd [LCP EchoRep id=0x3 magic=0x0]
Mar 22 16:04:23 playground pppd[20465]: sent [LCP EchoReq id=0x4
magic=0x84f3fde5]
Mar 22 16:04:49 playground pppd[20465]: Modem hangup
Mar 22 16:04:49 pl
On 22/03/2014 18:04, Ron Leach wrote:
On 21/03/2014 23:10, Mike McClain wrote:
I'm running Squeeze on a P3 board and dialup.
My modem gets hungup after 2.5 minutes about 30% - 40% of the time I
connect. Being idle, in the middle of fetching email or loading a
webpage seems to make no difference.
On Sat, Mar 22, 2014 at 01:19:43PM +0100, Wilko Fokken wrote:
> On Fri, Mar 21, 2014 at 04:10:42PM -0700, Mike McClain wrote:
> > I'm running Squeeze on a P3 board and dialup.
> > My modem gets hungup after 2.5 minutes about 30% - 40% of the time I
> > connect. Being idle, in the middle of fetching
On Fri, Mar 21, 2014 at 04:10:42PM -0700, Mike McClain wrote:
> I'm running Squeeze on a P3 board and dialup.
> My modem gets hungup after 2.5 minutes about 30% - 40% of the time I
> connect. Being idle, in the middle of fetching email or loading a
> webpage seems to make no difference. Is there an
On 21/03/2014 23:10, Mike McClain wrote:
I'm running Squeeze on a P3 board and dialup.
My modem gets hungup after 2.5 minutes about 30% - 40% of the time I
connect. Being idle, in the middle of fetching email or loading a
webpage seems to make no difference. Is there any way to log all
transactio
On Fri, Mar 21, 2014 at 04:10:42PM -0700, Mike McClain wrote:
> I'm running Squeeze on a P3 board and dialup.
> My modem gets hungup after 2.5 minutes about 30% - 40% of the time I
> connect. Being idle, in the middle of fetching email or loading a
> webpage seems to make no difference. Is there an
I'm running Squeeze on a P3 board and dialup.
My modem gets hungup after 2.5 minutes about 30% - 40% of the time I
connect. Being idle, in the middle of fetching email or loading a
webpage seems to make no difference. Is there any way to log all
transactions going to the modem which is on ttyS2? So
online all night when
doing a distupgrade.
A google search led me to reduce the mtu from 1500 to 1200 to no
avail. I've got pppd keepalive running and may disconnect immediately
after receiving an LCP EchoReply with the logs only showing 'modem
hangup' and no suggestion why or b
On Friday 30 August 2002 05:23 pm, Christian Schoenebeck wrote:
> > > You mean, when you deactivate ppp_on_boot (by moving or removing
> > > /etc/ppp/ppp_on_boot) and reboot your system, the _exact_ same error
> > > (messages) occur?
> >
> > No, I don't deactivate ppp_on_boot. Here is what happens
Am Freitag, 30. August 2002 23:01 schrieb Slaven Peles:
> On Friday 30 August 2002 04:44 pm, Christian Schoenebeck wrote:
> > Am Freitag, 30. August 2002 15:54 schrieb Slaven Peles:
> > > > Looks like you're automatically establishing a connection on startup.
> > > > If yes there must be a /etc/pp
On Friday 30 August 2002 04:44 pm, Christian Schoenebeck wrote:
> Am Freitag, 30. August 2002 15:54 schrieb Slaven Peles:
> > > Looks like you're automatically establishing a connection on startup.
> > > If yes there must be a /etc/ppp/ppp_on_boot file? Is this the case?
> >
> > Yes, that's what I
On Sat, Jan 06, 2001 at 10:01:32AM -0800, David S. Bach wrote:
> Last week there was a post about avoiding a modem hangup by
> specifying /dev/cua??? instead of /dev/ttyS?.
/dev/cu?? has been deprecated for some time now (years even). Are you
saying you want the modem to keep the line open
Last week there was a post about avoiding a modem hangup by
specifying /dev/cua??? instead of /dev/ttyS?.
Can someone please forward to me? I've been having this problem for a
long time and wanted to implement the solution, but now I cannot find
the message.
TIA,
db
--
David S.
"ludd pppd[420]: Modem hangup" occurs frequently, immediately after
booting up and rarely thereafter.
Sep 21 07:54:14 ludd pppd[420]: pppd 2.3.5 started by root, uid 0
Sep 21 07:54:42 ludd pppd[420]: Serial connection established.
Sep 21 07:54:43 ludd pppd[4
On Sat, 7 Jun 1997 [EMAIL PROTECTED] wrote:
> Does anyone know a simple command or tool to hang up the modem? Just
> hang it up, not stay connected to the tty and await more commands.
>
> What I'm after is something simple I can put into a script for sudo
> to kill the ppp daemon and also hang up
On Sun, 8 Jun 1997, Rick Jones wrote:
> On Sun, 8 Jun 1997 [EMAIL PROTECTED] wrote:
>
> > On 7 Jun 1997, John Goerzen wrote:
> >
> > > Just killing pppd will do it unless your modem isn't set up properly.
> >
> > Then my modem isn't set up properly. I got a private email mentioning
> > somethi
at&c1&d2 fixes these problems which isn't the factory default. The &d2
tells it to hangup, with autoanswer inhibited, when DTR is droped.
On Sun, 8 Jun 1997 [EMAIL PROTECTED] wrote:
> On 7 Jun 1997, John Goerzen wrote:
>
> > Just killing pppd will do it unless your modem isn't set up properly.
Look for an option something like:
* Drop carrier on DTR low
* Disconnect on DTR low
If I remember correctly, it is an AT&Dx command, but I'm not
completely sure.
<[EMAIL PROTECTED]> writes:
> On 7 Jun 1997, John Goerzen wrote:
>
> > Just killing pppd will do it unless your modem isn't set up
On 7 Jun 1997, John Goerzen wrote:
> Just killing pppd will do it unless your modem isn't set up properly.
Then my modem isn't set up properly. I got a private email mentioning
something about how the modem should automatically hangup once DTR is
dropped, which happens if "modem" is given as an
Just killing pppd will do it unless your modem isn't set up properly.
<[EMAIL PROTECTED]> writes:
> Does anyone know a simple command or tool to hang up the modem? Just
> hang it up, not stay connected to the tty and await more commands.
>
> What I'm after is something simple I can put into a
<[EMAIL PROTECTED]> writes:
[snip]
> What I'm after is something simple I can put into a script for sudo
> to kill the ppp daemon and also hang up the line, freeing /dev/ttyS1
> immediately (rather than waiting for the ISP to idle out the line and
> hang up on me).
>
> The first part I've got fi
How about a trick I use in M$DOS frequently to test modem response:
ECHO ATH0>/dev/modem (or COMx: in DOS)
Toss that in right after the pppd kill in your script.
On 7 Jun 97, debian-user@lists.debian.org wrote regarding:
__ Non-interactive modem hangup __
> Does anyone know a simple c
Does anyone know a simple command or tool to hang up the modem? Just
hang it up, not stay connected to the tty and await more commands.
What I'm after is something simple I can put into a script for sudo
to kill the ppp daemon and also hang up the line, freeing /dev/ttyS1
immediately (rather than
26 matches
Mail list logo
