Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizGeneral Tech Bugs & Fixes 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
Here's the solution I eventually solved my problem with:
while ! ip link show eth0 | grep -q 'state UP'; do
sleep 1
done
ip link add macvlan0 link eth0 type macvlan mode bridge
ip addr add 192.168.0.240/32 dev macvlan0
ip link set macvlan0 up
ip route add 192.168.0.240/28 dev macvlan0
However, I had 2 "boot-up" scheduled tasks on my Synology and I was getting some errors at boot-up. To solve that issue I configure this task to have the other one as pre-task. In other words, the tasks executed in sequence, waiting for the previous task to finish before starting the new one.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Ready to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
I have the following script that I need to run on my Synology NAS at boot-up. The Synology NAS has built-in scheduled tasks with the ability to trigger tasks at boot-up.
The script I need to run is this:
However, this does not work, the task seems to trigger to soon when the
eth0interface is not yet ready to accept these commands.Placing a
sleep 60before allip *commands, solves the issue. But it doesn't feel right to wait an arbitrary amount of seconds before doing my thing.Given my requirements above, what's the best method to wait for the
eth0interface to be available so that I can executeip *commands?