From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mhonline.net(dan-test.mhonline.net[204.97.156.9]) (1373 bytes) by braille.uwo.ca via smail with P:smtp/D:aliases/T:pipe (sender: ) id for ; Mon, 27 Mar 2000 10:17:03 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: (qmail 4808 invoked from network); 27 Mar 2000 15:17:01 -0000 Received: from unknown (HELO 209-23-38-177.ip.termserv.net) (209.23.38.177) by smtp.mhonline.net with SMTP; 27 Mar 2000 15:17:01 -0000 Date: Mon, 27 Mar 2000 10:17:08 -0500 (EST) From: Chuck Hallenbeck To: speakup@braille.uwo.ca Subject: Re: Automatic dialing in Linux In-Reply-To: <000b01bf9800$9dd272a0$beeef79b@default> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: 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.