how to automate connection at startup

how to automate connection at startup

Post by steve » Sat, 25 Aug 2001 09:34:39



I have rh7.1 linux box set up as gateway for a couple of other computers on
a home network.  What I would like to be able to do is put the right
commands in the right places so that all I have to do is turn on the linux
box and it will be primed to make the connection to my ISP.  I have most of
the pieces in place and working.  I use the rhPPP dialer to activate the
connection to my ISP.  I have diald set up so that when someone needs a
connection, the modem dials.  I use firestarter to run iptables firewall.  
(A uniqueness about it though is that it cannot be started until after the
connection is made.  (This is what the author of firestarter suggests doing
if address appear to be blocked if started prior to connection.))  I am
still somewhat a newbie with linux.  I have looked at ip-up and attempted
to create an ip-up.local to put the firestarter command in, but it does not
appear to do anything.  Therefore, I am not actually sure it is ip-up that
I am using.  I also looked at wvdial.conf, looks to have some familiar
lines but still not sure where to go.  Can someone pint me in the right
places?  Let me know if you need more info.

thanks,
steve

 
 
 

how to automate connection at startup

Post by Dean Thompso » Sun, 26 Aug 2001 00:27:05


Hi!,

Quote:> I have rh7.1 linux box set up as gateway for a couple of other computers on
> a home network.  What I would like to be able to do is put the right
> commands in the right places so that all I have to do is turn on the linux
> box and it will be primed to make the connection to my ISP.  I have most of
> the pieces in place and working.  I use the rhPPP dialer to activate the
> connection to my ISP.  I have diald set up so that when someone needs a
> connection, the modem dials.  I use firestarter to run iptables firewall.
> (A uniqueness about it though is that it cannot be started until after the
> connection is made.  (This is what the author of firestarter suggests doing
> if address appear to be blocked if started prior to connection.))  I am
> still somewhat a newbie with linux.  I have looked at ip-up and attempted
> to create an ip-up.local to put the firestarter command in, but it does not
> appear to do anything.  Therefore, I am not actually sure it is ip-up that
> I am using.  I also looked at wvdial.conf, looks to have some familiar
> lines but still not sure where to go.  Can someone pint me in the right
> places?  Let me know if you need more info.

You might like to take a look at the man page for ppp.  I am pretty sure that
there is a script in there which gets executed upon the successful connection
to a ISP, you could put your script in there or a pointer to a script in there
that needs to be started upon a connection.  The script lives in the /etc/ppp
directory, but there is another directory and script name which is used.  From
memory, the manual page for PPP has the name of the directory and script file
in it.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

1. best way - automate startup, ppp connection for normal user

Using redhat 7.2 with KDE, and modem connection to ISP.  On a small home
network, if my wife or kids (or myself) want to connect to the internet, I
have been turning on the computer, logging on, and establishing the ppp
connection (via a button click on redhat's rp3 connection icon).  All
somewhat manually.

  What I would like to do is to have some way (established as the default
startup) to automatically connect to the ISP.  An additional requirement is
to be able to interrupt this default startup/connection sequence and login
as root or normal user for maintenance or "whatever".

Thank you,
Steve

2. Pls help me !!!!!!!!!!!!!!!!

3. Automated Startup of Server (inittab?)

4. Dumping AIX and Ultrix machines to the same tape

5. Automating services on startup?

6. Delete all SVM metadevices

7. Automating Apache startup with a dedicated dialup access line....?

8. socket overflow?

9. Automating pppd or diald startup after paower fail

10. I need an init.d (automated startup script) file for SNORT

11. how to automate apache startup?

12. Automated startup commands

13. Automating telnet connection from shell script