Re: multiple ppp links and routing ..

On 29 Jun 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<1151601989.966131.33280@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Lawrence wrote:

Moe Trin wrote:

Does your modem(s) really know how to say all of those words?

I don't know.All I did was looking for example and copying settings I
though I should use.
Let's say that if it understands this words it would be usefull ?

It's just a minor waste of CPU cycles and RAM - really not of major
importance. The idea is to know what it takes to talk to the modem, and
do that. With the normal setup, you need only look for "NO DIALTONE" (USR)
or "NO DIAL TONE" (Rockwell) if you expect that the modem might become
unplugged or the telephone company go tits up, "BUSY", and "NO CARRIER"
(which occurs if the phone gets answered, but the modem can't agree how
to talk with whatever answered).

OK-AT-OK "ATDT0331051010"

OK ATDT0331051010

So I should only use what you say ?
I just copied the result of some configuration tool available for
debian ..
I also had a look in how to's but I wanted to use the most standard
setting I could ..

The 'OK-AT-OK' sequence is useless. It says to expect a response of "OK"
to the preceding command, and if you haven't received that response within
the TIMEOUT time (default is 45 seconds), then send the Hayes Command
Prefix ("I'm going to send a command") and expect that to cause the modem
to wake up. If your sending the modem init string failed to produce the
expected OK, there is no reason to expect that sending the command prefix
is going to do anything different. This sequence seems to have started
around 1995, as I can find a similar sequence in the ppp-on-dialer script
in ppp-2.2.0 (script dated 8 August 1995) though there is no author credited
that I can see (and this sequence is not used in ppp-2.1.2d from May 1995).
There, it's the even more interesting 'OK-+++\*** ATH0' which says that if
you don't get the "OK" you should send the Hayes command break sequence
(at least a second of silence, three + characters, and another period of
silence) to get the modem to go to the command mode - then the command tells
the modem to hang up the phone. Now, I don't know about you, but if the
system was keeping the phone off-hook all of the time, I'd like to know
about this now, rather than wait until the end of the month when I get this
monstrous bill from the telephone company. (It's also interesting that
this same script - same file date and all - is still part of ppp-2.4.4b1
from August 2005, although it's not installed by default any more.)

Oh, let me ask an other question, is it possible to count data in/out
for a certain IP with iptables and log ? like 40 mb in and 90 mb out
for user 10.0.0.2

[compton ~]$ whatis pppstats
pppstats (8) - print PPP statistics
[compton ~]$

That's been part of the ppp package since at least 2.1.2d, though the
data count values were not reported until 2.3.0. Also, ppp-2.3.8 (from
May 1999) added environment variables CONNECT_TIME, BYTES_SENT and
BYTES_RCVD for the ip-down and auth-down scripts indicating the statistics
for the connection just terminated. (CONNECT_TIME is in seconds.) You
can access those variables in /etc/ppp/ip-down. It's in the man page.

Old guy
.

Quantcast