Thanks Peter. I guess they don't make an issue of it if only 1 person 
has reported the bug. I noticed when I added myself to the "this affects 
me" it changed the status to confirmed. I actually had this working, but 
then I'm pretty sure I did a apt-get upgrade or added a package and that 
is when it broke.

Unfortunately, I didn't have date/time stamping added to my bash profile 
so I can't tell from history when it was.

I also tried various Google references for adding static routes in an 
automated fashion. While there were several differences in the approach, 
none worked.

And I agree, I would think there has got to be other people doing 
similar stuff. I didn't think I was that bleeding edge.

David Garland

On 11/18/2015 2:30 PM, Peter B wrote:
> Hi David,
>    I could not reliably make things work for production.  I had tried to put 
> ifup/ifdown in my rc.local script and I tried tweaking the upstart scripts... 
> but I couldn't get anything to bring up all the interfaces reliably.
>
>    Noone in the forms bothered to help on this either...
>
>    Upstart is a complete disaster...  I ended up abandoning 14.04
> altogether, rolled back to a 10.04 snapshot and then forced an upgrade
> to 12.04 LTS.   12.04 is temperamental at times and also doesn't always
> bring up the interfaces right, but I can script around it and make sure
> things are up.
>
>    I don't understand how this is not a bigger issue for Ubuntu...  We
> can't be the only ones with more complex network configs...
>
> -Cheers, Peter.
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472055

Title:
  /etc/network/interfaces up, post-up commands not run at network
  startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netscript-2.4/+bug/1472055/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to