🚀 go-pugleaf

On 29 Mar 96 13:10:37 +0500, John S. Burger articulated:
<> I use AmiTCP 4.2 and PPP 1.45 registered also and this works fine. However,
<> with AmoTCP 4.0demo things are a bit different. The default AmiTCP 4.2
<> starenet script uses BOOTP to configure the ppp.device. This works fine
<> using AT&D0 and CD in the ppp0.config file and then running startnet again
<> the connection is renegotiated. . The startnet script actually creates the
<> ENV:sana2/ppp0.config file from the defaults you set during the software
<> installation when the script is run. With AmiTCP 4.0demo the ppp0.config file
<> resides in env- archive: and is copied to ENV: on bootup. The startnet script
<> does not use BOOTP (it is not even in the 4.0 archive) it simply uses the
<> online command to put the ppp.device on line. If you have dynamic connection
<> it seems the online command (ppp.device) can't reconnect because it doesn't
<> know the IP addresses. When the startnet script is first run and the
<> connection negotiated there are two environment variables created--
<> ppp0IPLocal and ppp0IPRemote -- that contain the current IP addresses. I added
<> two lines to the end of my V4.0demo startnet script to copy these two
<> environment variables to env-archive: when the connection is first made. Then
<> after a reboot they are in ENV: and a simple online command will reconnect
<> you.

I was not aware of this. I have always used AmiTCP 4.2, so
this problem never happened to me. I'm glad you have found a
fix for this and I hope others read this too.

-- 
---------------------------------------------------
 Bill    ////\           wnear@epix.net
 Near   ////\\\ A2000/030@50/Picasso II/Supra V.34
       //// \\\\              _____  __      _
 \\\\ ////___\\\\ //// |\  /|   |   /  \    / \
  \\\\///-----\\\\///  | \/ |   |   |  __  /---\
   \\\\/       \\\\/   |    | __|__ \__/  /     \
    Contributing Editor @ Amiga Report Magazine
---------------------------------------------------