** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) = Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus or no nameserver information written to
** Changed in: ifupdown (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus or no nameserver information written to
** Changed in: ifupdown (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus or no nameserver information written to
This bug was fixed in the package ifupdown - 0.7~beta2ubuntu7
---
ifupdown (0.7~beta2ubuntu7) precise; urgency=low
[ Wookey ]
* Use cross-compiler when cross-compiling (LP: #967227)
Also merged upstream as:
FYI.
I tested a daily server build of Ubuntu 12.04 beta today. The (duplicate)
issue 938520 I had noted on /etc/resolv.conf and /etc/network/interfaces is
fixed :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In #940260 I wrote (in reverse order):
3. Perhaps the maintainer scripts should detect a flawed-netcfg-corrupted
/e/n/i and either notify the admin or give her the opportunity
(via debconf?) to repair the corrupted file.
Steve Langasek's change in 1.63ubuntu9 implements the most important
On Mon, Feb 27, 2012 at 08:23:33PM -, Thomas Hood wrote:
A fix-the-bogus-dns-nameservers-line wizard would be nice, but if we
were going to do that we would simply write a wizard for configuring
ifupdown for resolvconf. What would be the correct way to implement
such a thing in Ubuntu?
Stéphane: Very good point. All systems that have been installed with
static network configuration using the faulty netcfg had, and probably
still have, broken /e/n/i files. IIUC that includes all Oneiric
systems.
Unfortunately I don't have an example of a corrupted file on hand. But
if I
Hi Stéphane,
I'm attaching an example /e/n/i file. Due to the nature of this bug,
it's actually writing out initialized memory space, so the results are
random. In the majority of cases, since this is a newly-booted system,
the memory being pointed to is probably zeros, so nothing will actually
So we probably want to have resolvconf check for 'dns-nameservers [0-9A-
Fa-f.:]+' on upgrade when deciding if there's valid info, instead of
just 'dns-nameservers'; and likewise we should have ifupdown do a one-
time scrub on upgrade of any values it finds that don't match this
regexp.
** Also
** Branch linked: lp:ubuntu/resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus or no nameserver information written to /etc/network/interfaces
To manage notifications
This bug was fixed in the package resolvconf - 1.63ubuntu9
---
resolvconf (1.63ubuntu9) precise; urgency=low
* debian/config: dns-nameservers lines are only valid if they take an ipv4
or ipv6 value, and earlier bugs in netcfg may spit out lines with garbage
values instead.
Could this also be the cause of #214492?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus or no nameserver information written to /etc/network/interfaces
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netcfg (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
I have just reproduced this by installing the 23 February 2012
precise-server-amd64.iso in a VirtualBox virtual machine and selecting manual
interface configuration. The dns-search option is written correctly but after
dns-nameservers and a space come two garbage characters.
--
Thomas
--
** Changed in: netcfg (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus or no nameserver information written to /etc/network/interfaces
To
I confirmed the fix to be working doing manual static installs.
Now quickly running through the other tests and will upload if they all
pass.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
This bug was fixed in the package netcfg - 1.68ubuntu12
---
netcfg (1.68ubuntu12) precise; urgency=low
* Apply patch from Matthew L. Dailey to fix the dns- entries in
/etc/network/interfaces. (LP: #932275)
-- Stephane Graber stgra...@ubuntu.com Thu, 23 Feb 2012 12:27:28
** Changed in: netcfg (Ubuntu)
Status: Confirmed = Triaged
** Changed in: netcfg (Ubuntu)
Assignee: (unassigned) = Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can one of you attach an example of the bogus value? it'd help to make
sure resolvconf will be dealing with it properly on upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus
The better patch.
** Attachment added: Better patch
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/932275/+attachment/2739384/+files/static.c.betterpatch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: Quick-and-dirty patch
https://bugs.launchpad.net/bugs/932275/+attachment/2739383/+files/static.c.quickpatch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932275
Title:
Bogus or
The attachment Quick-and-dirty patch of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
23 matches
Mail list logo
