public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: Automatic dialing in Linux
Date: Mon, 27 Mar 2000 10:42:45 -0500	[thread overview]
Message-ID: <002001bf9803$19339d00$beeef79b@default> (raw)
In-Reply-To: <Pine.LNX.4.10.10003271013120.804-100000@hudson.mhonline.net>

Hi, Chuck!
yes, exactly. Now, my 192.168.0.1 and 0.2 are already in use, so I gave it 0.3
and 0.4. But it still doesn't work. I guess, I have to check more carfully
into the settings.
I'll let you know more on the progress.
Regards,
Vic

----- Original Message -----
From: "Chuck Hallenbeck" <chuckh@mhonline.net>
To: <speakup@braille.uwo.ca>
Sent: Monday, March 27, 2000 10:17 AM
Subject: Re: Automatic dialing in Linux


|
| That should not be a problem. You just give a 'private network' number for
| each, and specify 'dynamic' in your diald.conf file. The docs suggest
| using 192.168.0.1 and 192.168.0.2 if they are not already in use. The
| 'dynamic' option lets the software replace those phoney addresses with the
| assigned ones when your ISP reports them during the signon process.
|
| Chuck.
|
|
|
|  On Mon, 27 Mar 2000, Victor Tsaran wrote:
|
| > Yes, they're both in the kernel. I belive I have a problem with local and
| > remote IP's. The reason is that I am assigned dynamic IP's on both sides.
That
| > is, my ISP assigns IP's for both local and remote terminals.
| > Regards,
| > Vic
| > Thanks for help.
|
|
| _______________________________________________
| Speakup mailing list
| Speakup@braille.uwo.ca
| http://speech.braille.uwo.ca/mailman/listinfo/speakup



      parent reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Victor Tsaran
 ` Chuck Hallenbeck
   ` Victor Tsaran
     ` Chuck Hallenbeck
       ` Chuck Hallenbeck
         ` Christopher Moore
           ` Chuck Hallenbeck
         ` Victor Tsaran
           ` Chuck Hallenbeck
             ` Victor Tsaran
       ` Victor Tsaran [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002001bf9803$19339d00$beeef79b@default' \
    --to=vtsaran@nimbus.ocis.temple.edu \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).