मैं अपने कॉर्पोरेट सर्वर से कनेक्ट करने के लिए वीपीएन क्लाइंट का उपयोग करता हूं। यह क्लाइंट शुरू करने के बाद tun0 इंटरफ़ेस बनाता है। मैंने स्क्रिप्ट लिखी है जो ट्यून इंटरफेस के लिए विशिष्ट रूट पॉइंट स्थापित करती है और सामान्य वाईफाई कनेक्शन का उपयोग करने के लिए आराम करती है। ताकि, केवल मेरे कार्यालय से संबंधित यातायात वीपीएन के माध्यम से चला जाए और बाकी घर इंटरनेट कनेक्शन के माध्यम से चला जाए। जब ट्यून अप / डाउन ईवेंट को स्वचालित रूप से चलाने के लिए मैं स्क्रिप्ट कैसे बनाऊं?
जवाबों:
मुझे यकीन नहीं है tun0, लेकिन मुझे लगता है कि स्क्रिप्ट में /etc/network/if-up.d/और/etc/network/if-down.d/ लागू कर रहे हैं जब एक अंतरफलक ऊपर या नीचे क्रमश: चला जाता है।
स्क्रिप्ट के अंदर आप यह निर्धारित कर सकते हैं कि चर की सामग्री से कौन सा इंटरफ़ेस रुचि रखता है IFACE ।
सुनिश्चित करने के लिए, एक साधारण स्क्रिप्ट जोड़ें कि /etc/network/if-up.d/कौन सी सामग्री है
#!/bin/sh
# filename: tun-up
if [ "$IFACE" = tun0 ]; then
echo "tun0 up" >> /var/log/tun-up.log
fi
इसे अमल में लाएं
sudo chmod +x /etc/network/if-up.d/tun-up
फिर देखें कि क्या अप इवेंट्स में रिकॉर्ड किया गया है /var/log/tun-up.log
gksudo gedit /etc/network/interfaces
जोड़ें:
auto tun0
iface tun0 inet manual
up COMMAND
COMMANDip route add something...निष्पादन योग्य अनुमतियों ( chmod +x) के साथ एक कमांड, जैसे या स्क्रिप्ट पथ , अंततः संग्रहीत किया जा सकता है /etc/network/if-up.d/।
इसके बजाय upआप उपयोग कर सकते हैं post-up, down, post-down।
प्रलेखन :
IFACE विकल्प
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.
मैंने systemdएक स्क्रिप्ट चलाने के बाद उपयोग किया है network-online.target। मेरी स्क्रिप्ट <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