Wie kann ich das Skript so einstellen, dass es automatisch ausgeführt wird, wenn Ereignisse für die Schnittstelle "tun0" aktiviert / deaktiviert werden?

Ich verwende einen VPN-Client, um eine Verbindung zu meinen Unternehmensservern herzustellen. Nach dem Start des Clients wird die Schnittstelle tun0 erstellt. Ich habe ein Skript geschrieben, das bestimmte Routen zur tun0-Schnittstelle installiert und die normale WLAN-Verbindung verwendet. Damit geht nur mein Office-bezogener Datenverkehr über VPN und der Rest geht über die Heim-Internetverbindung. Wie kann ich das Skript so einstellen, dass es automatisch ausgeführt wird, wenn Ereignisse auf / ab der tun0 - Schnittstelle auftreten?

Ich bin nicht sicher tun0, aber ich denke , das Skript in /etc/network/if-up.d/und /etc/network/if-down.d/aufgerufen werden , wenn eine Schnittstelle geht nach oben oder unten ist.

Innerhalb des Skripts können Sie anhand des Inhalts der Variablen bestimmen, welche Schnittstelle interessiert ist IFACE.

Um sicherzugehen, fügen Sie ein einfaches Skript hinzu, zu /etc/network/if-up.d/dem der Inhalt gehört

#!/bin/sh
# filename: tun-up

if [ "$IFACE" = tun0 ]; then
  echo "tun0 up" >> /var/log/tun-up.log
fi

mach es ausführbar

sudo chmod +x /etc/network/if-up.d/tun-up

Überprüfen Sie dann, ob die Up-Ereignisse in aufgezeichnet sind /var/log/tun-up.log

gksudo gedit /etc/network/interfaces

Hinzufügen:

auto tun0
iface tun0 inet manual
    up COMMAND

COMMANDkann ein Befehl wie ip route add something...oder ein Skriptpfad mit ausführbaren Berechtigungen ( chmod +x) sein, der schließlich in gespeichert wird /etc/network/if-up.d/.

Statt die upSie verwenden können post-up, down, post-down.

Dokumentation :

IFACE-OPTIONEN

   The  following  "command"  options  are  available for every family and
   method.  Each of these options can be given multiple times in a  single
   stanza,  in  which case the commands are executed in the order in which
   they appear in the stanza.  (You can ensure a command  never  fails  by
   suffixing them with "|| true".)

   pre-up command
          Run  command  before bringing the interface up.  If this command
          fails then ifup aborts, refraining from marking the interface as
          configured,  prints  an  error message, and exits with status 0.
          This behavior may change in the future.

   up command

   post-up command
          Run command after bringing the interface up.   If  this  command
          fails then ifup aborts, refraining from marking the interface as
          configured (even though it has really been  configured),  prints
          an  error  message,  and exits with status 0.  This behavior may
          change in the future.

   down command

   pre-down command
          Run command before taking the interface down.  If  this  command
          fails  then  ifdown  aborts, marks the interface as deconfigured
          (even though it has not really  been  deconfigured),  and  exits
          with status 0.  This behavior may change in the future.

   post-down command
          Run  command  after  taking the interface down.  If this command
          fails then ifdown aborts, marks the interface  as  deconfigured,
          and  exits  with  status  0.   This  behavior  may change in the
          future.

   There exists for each  of  the  above  mentioned  options  a  directory
   /etc/network/if-<option>.d/  the  scripts  in  which  are  run (with no
   arguments)  using  run-parts(8)  after  the  option  itself  has   been
   processed.  Please  note  that  as post-up and pre-down are aliases, no
   files in the corresponding directories are processed.  Please  use  if-
   up.d and if-down.d directories instead.

   All  of  these  commands  have  access  to  the  following  environment
   variables.

   IFACE  physical name of the interface being processed

   LOGICAL
          logical name of the interface being processed

   ADDRFAM
          address family of the interface

   METHOD method of the interface (e.g., static)

   MODE   start if run from ifup, stop if run from ifdown

   PHASE  as per MODE, but with finer granularity, distinguishing the pre-
          up, post-up, pre-down and post-down phases.

   VERBOSITY
          indicates whether --verbose was used; set to 1 if so, 0 if not.

   PATH   the   command   search   path:  /usr/local/sbin:/usr/local/bin:���
          /usr/sbin:/usr/bin:/sbin:/bin

   Additionally, all options given in an interface definition  stanza  are
   exported to the environment in upper case with "IF_" prepended and with
   hyphens  converted  to  underscores  and  non-alphanumeric   characters
   discarded.

   When  ifupdown  is  being  called  with  the --all option, before doing
   anything to interfaces, if calls all the hook scripts (pre-up or  down)
   with  IFACE set to "--all", LOGICAL set to the current value of --allow
   parameter  (or  "auto"   if   it's   not   set),   ADDRFAM="meta"   and
   METHOD="none".   After all the interfaces have been brought up or taken
   down, the appropriate scripts (up or post-down) are executed.

Ich habe systemddanach ein Skript ausgeführt network-online.target. Mein Drehbuch <path>/script.sh.

1.) sudo systemctl edit --force --full my-script.service:

[Unit]
Description=My script after network available
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
User=root
ExecStart=<path>/script.sh

[Install]
WantedBy=multi-user.target

2.) sudo systemctl enable my-script.service

3.) sudo systemctl start my-script.service