please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1779721
Title:
** Changed in: systemd (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1779721
Title:
systemd-networkd
No connectivity until systemd-networkd is restarted. Or, in the second case,
connecting over the DHCP interface to restart systemd-networkd. But because
networkd does not have a configuration file for eth0, it doesn't add ...
verbose logs you can run systemctl edit systemd-networkd.
If anyone
In both cases, no network, no static IP address, .. however, restarting
systemd-networkd instantly brings the configuration up, and communication on
the desired IP address starts.
If anyone face laptop problem gets help from this http://lenovotechsupport.com
--
You received this bug
I don’t know if this should be a different bug or a note added here.
I have tried to setup Ubuntu 18.04 (bionic) server as a router. I was
trying to set it up with both IPv4 & IPv6 but the installation (dynamic)
would not allow me to get IP from my ISP after setup was complete. When
starting
This bug in systemd-networkd is affecting our environment also.
We have an RFC-compliant DHCP server that does not reply with Option 54
"Server Identifier". We have made the point to other vendors that this
is indeed compliant with the RFC because there is no routable address to
the DHCP server
This is not really a bug in systemd-networkd. It just adheres more
strictly to the standard.
In this case the DHCP server doesn't send the Option 51 "IP Address
Lease Time" in the DHCPOFFER. RFC2131 declares this a MUST (see Table 3:
Fields and options used by DHCP servers).
I encountered a
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Full log output:
root@ubuntu:~# SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Bus n/a: changing state UNSET → OPENING
Bus n/a: changing state OPENING → AUTHENTICATING
Failed to open
$ sudo env SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
[...]
DHCP CLIENT (0x...): received lease lacks address, server address or lease
lifetime, ignoring
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Setting 'dhcp-identifier: mac' (translates to networkd
'ClientIdentifier=mac' option) makes no difference. One specialty is
that the subnet-mask is 255.255.255.255 (i.e. /32).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The dhclient lease looks ok. It has a largish MTU, but that should be
fine.
Does the dhcp server in question require MAC based client identifiers?
Could you please try:
network:
version: 2
renderer: networkd
ethernets:
all:
match:
name: ens*
dhcp4: yes
/run/systemd/netif/leases is empty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1779721
Title:
systemd-networkd does not configure DHCPv4
Status in netplan.io package
Ok, i must be mistaken about empty match stuff then.
This does look odd.
systemd-networkd should have forked, to run its own dhcp client
implementation. And there should be state data in /run/systemd/netif/
e.g. /leases/ folder should have a lease.
** Changed in: systemd (Ubuntu)
Importance:
Just checked the initial configuration:
```
root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
all:
match: {}
dhcp4:
My interpretation of the documentation was that an empty match entry
matches everything. I changed the configuration to enforce the matching
and it still fails:
```
root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more
An empty match, does not match any interfaces hence none are
configured
What's the output of $ networkctl ? i suspect no interfaces are
maganaged, right?
Note the config mentioned in this bug report looks buggy, and different
from the askubuntu reference - which does appear to have a valid
You can also reproduce this issue with the official cloud image. See
https://askubuntu.com/questions/1030081/ubuntu-18-04-cloud-image-does-
not-get-dhcp-ipv4-address
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
18 matches
Mail list logo
