group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #14235
[Bug 1626617] Re: console-conf does not allow to set up dns for static ip
This bug was fixed in the package nplan - 0.23~16.10.1
---------------
nplan (0.23~16.10.1) yakkety; urgency=medium
* Backport netplan 0.23 to 16.10. (LP: #1688632)
nplan (0.23) artful; urgency=medium
* Do not unbind brcmfmac, interface will be gone. (LP: #1696162)
nplan (0.22) artful; urgency=medium
* Add support for setting a custom MAC address on all device types.
(LP: #1690388)
* Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
changes.
nplan (0.21) artful; urgency=medium
[ Ryan Harper ]
* Add support for setting MTU on a device. (LP: #1668693)
[ Mathieu Trudel-Lapierre ]
* Don't rebind Atheros AR9271; it would confuse the driver. (LP: #1672740)
* debian/control: Add Conflicts: against netplan; the network 'plan' daemon.
Both ship the same /usr/sbin/netplan. (LP: #1665842)
nplan (0.20) zesty; urgency=medium
* tests/integration.py: increase timeout for integration tests (networkd and
NetworkManager "wait-online" checks) to account for longer bring-up times
when dealing with stacked virtual devices.
nplan (0.19) zesty; urgency=medium
* Add support for unordered definition of network devices: you can now
specify a virtual devices before their member devices. (LP: #1670495)
* Allow setting up the STP state for a bridge. (LP: #1665088)
* Document bond/bridge parameters support. (LP: #1664702)
nplan (0.18) zesty; urgency=medium
* debian/tests/integration.py: in some cases 'iw reg get' may qualify the
reg domain results with 'global'; we must not let that trip up tests when
they are run on Ubuntu infrastructure vs. local tests.
nplan (0.17) zesty; urgency=medium
* New release:
- Add support for configuring bonds.
- Add support for configuring bridges.
nplan (0.16) zesty; urgency=medium
[ Martin Pitt ]
* doc/example-config: Adjust "routes:" example.
It does not make sense to make "routes:" a global thing, they should be
tied to an interface so that the route is only set when the corresponding
interface exists and is up, and the config is not split in two parts.
* doc/netplan.md: Point out that NM does not support globbing (LP: #1631018)
[ Mathieu Trudel-Lapierre ]
* Fix coverage for src/netplan to be 100%, and fail if coverage falls below
that mark again.
* Add support for specifying routes.
nplan (0.15) zesty; urgency=medium
* tests/generate.py: Fix PEP-8 error (newly detected by -proposed
pycodestyle).
nplan (0.14) zesty; urgency=medium
* tests/generate.py: Introduce macros for commonly expected networkd output
* networkd: Use NetworkManager compatible DHCP route metrics (LP: #1639754)
* doc/netplan.md: Fix wrong wifi reference in "br0" example
* doc/netplan.md: Clarify introduction
* tests/integration.py: Fix race condition with waiting for networkd
nplan (0.13) zesty; urgency=medium
[ Jonathan Cave ]
* Blacklist mwifiex_pcie from rebinds (work around LP: #1630285)
[ Martin Pitt ]
* Add support for nameservers (LP: #1626617)
-- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx> Tue, 06 Jun 2017
17:25:57 -0700
** Changed in: nplan (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1626617
Title:
console-conf does not allow to set up dns for static ip
Status in netplan:
Fix Released
Status in Snappy:
New
Status in nplan package in Ubuntu:
Fix Released
Status in subiquity package in Ubuntu:
Fix Released
Status in nplan source package in Xenial:
Fix Released
Status in subiquity source package in Xenial:
Won't Fix
Status in nplan source package in Yakkety:
Fix Released
Status in subiquity source package in Yakkety:
Won't Fix
Bug description:
[Impact]
subiquity and other nplan users may need to include DNS information when setting up a system.
[Test case]
1) set up a system with a netplan configuration including the nameserver: key for an interface, such as the following:
network:
ethernets:
enxb827ebd3f20f:
addresses: [192.168.0.200/24]
nameservers: 192.168.0.10
version: 2
Verify that the nameserver settings are properly installed to the
system (see /etc/resolv.conf or /run/systemd/resolve/resolv.conf)
[Regression potential]
Existing configurations that do not include nameserver configs should continue to work as-is; without nameserver data if using static addresses, or with the nameserver data retrieved from DHCP.
[Original bug report]
There's no way to setup DNS info for static IP configuration, which leads to broken name resolution:
fgimenez@localhost:~$ cat /etc/netplan/00-snapd-config.yaml
# This is the network config written by 'console-conf'
network:
ethernets:
enxb827ebd3f20f:
addresses: [192.168.0.200/24]
version: 2
fgimenez@localhost:~$ ping www.ubuntu.com
ping: unknown host www.ubuntu.com
fgimenez@localhost:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
Selecting DHCP config from console-conf all works fine:
fgimenez@localhost:~$ cat /etc/netplan/00-snapd-config.yaml
# This is the network config written by 'console-conf'
network:
ethernets:
enxb827ebd3f20f:
addresses: []
dhcp4: true
version: 2
fgimenez@localhost:~$ ping www.ubuntu.com
PING www.ubuntu.com (91.189.90.59) 56(84) bytes of data.
64 bytes from www.ubuntu.com (91.189.90.59): icmp_seq=1 ttl=51 time=34.0 ms
64 bytes from www.ubuntu.com (91.189.90.59): icmp_seq=2 ttl=51 time=39.4 ms
64 bytes from www.ubuntu.com (91.189.90.59): icmp_seq=3 ttl=51 time=37.0 ms
^C
--- www.ubuntu.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 34.066/36.882/39.496/2.221 ms
fgimenez@localhost:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1626617/+subscriptions