[Expired for ifupdown (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
[Expired for resolvconf (Ubuntu) because there has been no activity for
60 days.]
** Changed in: resolvconf (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
** Changed in: resolvconf (Ubuntu)
Status: New => Incomplete
** Changed in: ifupdown (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
> well i've now been able to restart 3 of the 4 systems about 5-10x each
> through the day. all have
> had their gateway and dns- settings from /e/n/i reliably set. that is, until
> now. i've got one
> system that did not get gateway or dns- settings.
The gateway is set directly from ifup (by
bump! definitely a repeatable issue albeit sporadically. lost another
system on reboot - no default gateway installed although it's set in
/e/n/i. have to manually add route via rc.local and symlink
/etc/resolv.conf.d/resolv.conf original to tail as workarounds.
--
You received this bug
yes i think all of them. the interface appears to always be configured
correctly. however, sometimes the default gateway is not set, other
times the dns- settings are not set, and still other times neither are
set.
--
You received this bug notification because you are a member of Ubuntu
Touch
Are there cases where the interface is configured properly but
resolv.conf is not updated to include material from the dns-* lines?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
note see package ifupdown bug #1573272. it would seem related but note
that dns- settings are also problematic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1628552
well i've now been able to restart 3 of the 4 systems about 5-10x each
through the day. all have had their gateway and dns- settings from
/e/n/i reliably set. that is, until now. i've got one system that did
not get gateway or dns- settings.
is there a way to check for a failure status code tied
Obviously the presence of material in the "base" file should have no
effect on the processing of material from /etc/network/interfaces. Are
you still sure that material from /e/n/i is sometimes incorrectly
omitted from the /etc/resolv.conf file?
--
You received this bug notification because you
thank you. that of course worked (apologies for not fully understanding
the parsing of the base file). interestingly enough, with that search
addition in the base file, now the settings from /etc/network/interfaces
are now showing up in resolv.conf (bogus.com is appended to the other
dns-search
Comment lines from the "base" file are always omitted from resolv.conf.
Try adding a line "search bogus.com“ and see if "bogus.com" shows up on
the "search" line in resolv.conf.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
12 matches
Mail list logo
