On Wed, Jan 20, 2021 at 08:41:34AM -, Sakthi Nathiarasan wrote:
> HI, There is a problem here. If we are not setting any IPv4 address, by
> default it is setting IPV4 link-local. Which shouldn't be the case.
Do you have the avahi-autoipd package installed? This may not be coming
from netplan.
HI, There is a problem here. If we are not setting any IPv4 address, by
default it is setting IPV4 link-local. Which shouldn't be the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771704
Title:
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
* tests/integra
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Hello Steve, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
** Changed in: netplan.io (Ubuntu Bionic)
Status: Fix Released => 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/1771704
Title:
support for ipv4 link-local addressing
To manage
This bug was fixed in the package netplan.io - 0.40.1~18.04.2
---
netplan.io (0.40.1~18.04.2) bionic; urgency=medium
* Fix typo breaking rename on 'netplan apply'. (LP: #1770082)
netplan.io (0.40.1~18.04.1) bionic; urgency=medium
* Backport netplan 0.40.1 to 18.04. (LP: #1793309
Verification done on bionic with netplan.io 0.40.1~18.04.2:
I have checked that with ipv4 link-local enabled as per the use-case, an
ipv4 link-local address is correctly set up by systemd-networkd as
requested by the netplan config.
ubuntu@nice-baboon:~$ sudo vi /etc/netplan/50-cloud-init.yaml
ub
Hello Steve, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hi Steve,
No worries, that sounds fair enough. I will file the bugs as separate
issues in the next few days then.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771704
Title:
suppo
I think we should not block the SRU of the netplan that allows users to
declare their intended network config. There will be some work to get
the backends to catch up, and that's ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Hi,
I added this to my netplan-config-tester and it's turned up a couple of
issues with NetworkManager.
1) If a static IPv4 address is specified and link-local: [ipv4] is
specified, there is no link-local address added. The documentation
doesn't make this clear; it only refers to DHCP conflicting
root@harmless-perch:~# dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
Marking verfication-done:
I have checked that the excerpt:
link-local: [ ipv4 ]
(or ipv6)
Is accepted in netplan.io configuration file
Hello Steve, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40~18.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Changed in: netplan
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771704
Title:
support for ipv4 link-local addressing
To manage notifications about t
** Description changed:
+ [Impact]
+ Ubuntu users who make use of IPv4 link-local addresses.
+
+ [Test case]
+ 1) Add 'link-local: [ ipv4 ]' to the netplan configuration.
+ 2) Run 'sudo netplan apply'
+
+ [Regression Potential]
+ Enabling link local means additional addresses are available on th
This bug was fixed in the package netplan.io - 0.39
---
netplan.io (0.39) cosmic; urgency=medium
* New upstream release:
- Allow link-local addresses to be configured. (LP: #1771704)
- Forces bridges with no addresses to be brought online. (LP: #1736975)
-- Mathieu Trudel-
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771704
Title:
support for ipv4 link-local addressing
To manage notifi
18 matches
Mail list logo
