Twice this past week when I turned on my PC (Debian latest stable build) the internet didn't work.
I ran `ifdown eth1; ifup eth1` and it started working.
(eth0 is Firewire, eth1 ethernet)
Why? How do I fix it?
I'm suspicious that the init.d isn't working properly because I added a script/file to /etc/init.d/ that reads `ntpdate {servers}` and when I booted, my clock was off by a few hours. (`ntpdate {servers}` fixed it.) Unless that's just because I didn't include a shebang and/or path in that script... :innocent:

Have do changed the script permission to executable in init.d
chmod +x <script-name>
sorry if you know already

Yup. I actually use chmod 700. Most the time the interface is up. Except twice it wasn't...
I tried making a script (owned by root) that ran `ifdown eth1 ; ifup eth1` and "set user or group ID on execution (s)" using chmod 6755, but I get: "/sbin/ifdown: failed to open statefile /etc/network/run/ifstate: Permission denied"
Shouldn't it be running as root?
I tried making that file read/write accessable to everyone (chmod 666) but that just caused the next file to give a permission error.
Hm. For now I let anyone run the script with sudo. It works, but I'd prefer if the suid worked and I'd prefer if it worked without.
EDIT: No go. Even with SUID, it failed. With sudo it worked. So I may as well stick to the shell script and sudo.

EDIT: According to Wikipedia:
"Due to the increased likelihood of security flaws, many operating systems ignore the setuid attribute when applied to executable shell scripts."
Is there a work around?

EDIT: Is this safe? I'm thinking of wrapping the ifdown/ifup in a C program and using the system() call. That should be OK, right?