HEX
Server: Apache/2.4.41 (Ubuntu)
System: Linux ip-172-31-42-149 5.15.0-1084-aws #91~20.04.1-Ubuntu SMP Fri May 2 07:00:04 UTC 2025 aarch64
User: ubuntu (1000)
PHP: 7.4.33
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
Upload Files
File: //usr/share/doc/ppp/examples/per-linkname
Date: Mon, 06 Oct 2003 16:00:25 +0200
From: Eyal Rozenberg <rozenbrg@barak-online.net>
Subject: ppp per-linkname script dir

(I'm writing you as the maintainer of the Debian ppp package)

On my system, I sometime find it necessary to run different commands for 
different peers/providers after the ppp connection, like specific 
complex routing configuration, etc. To do so I have added the files 
/etc/ppp/ip-up.d/00peer-specific and /etc/ppp/ip-down.d/00peer-specific
whose contents is:
------------------------------------------------------------------

#!/bin/bash
#
# run peer-specific (or, rather, 'link-name' specific) scripts

if [ -n "$LINKNAME" ] ; then
         run-parts /etc/ppp/ip-up.d/$LINKNAME
fi

exit 0

------------------------------------------------------------------

and the same thing for if-down.d (but with its respective directory 
name). To use these, one must set the linkname pppd option in the files 
under /etc/ppp/peers - but that's a good idea anyway.

Perhaps you would consider adding such files to the ppp package.

Eyal Rozenberg