The method I use to do this is to create a directory with multiple configurations stored, and then use a program to copy the requested config to the current config.
the program multiconfig is used like this.. (rocknet is the isp name) # multiconfig /etc/pon/rocknet which just recurses the directy and copies it to the hiearchy with the initial directy pathname removed.. umm.. maybe an example is will be more clear # multiconfig /etc/pon/rocknet /etc/pon/rocknet/etc/hosts copies to /etc/hosts so pon only needs to do something like multiconfig /etc/pon/$SETUP where $SETUP is $1 or /etc/pon/default if no argument is specified. to connect to the isp "rocknet" i use # pon rocknet or simply # pon which defaults to /etc/pon/default which is just a sym link to rocknet poff then does a # multiconfig /etc/pon/local currently /etc/pon/local is manually created, however if there is any interest into this method of handling ppp, then i'll change it to save the origianl config here automatically and then use something like multiconfig --restor/multiconfig -r. (works great currently for something I quickly hacked up) a lock file is created showing on pon startup, so if the pc gets reset or something else happens, I know what the current configuration is.. so just modify rc.boot to handle this and you'll be fine.. i'll send the source and pon/poff changes if requested. typically something like this should be expected in the ppp package.. ANyway, this works great, and provides a clean way for multiple ppp setups including selected changes to config file, ie no more script changes to ip-up/ip-down if you want to change your /etc/hosts for ppp or whatever.. Silvio Cesare
