Package: miredo
Version: 1.2.6-4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I use miredo in a virtual machine that gets address from dhcp.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I start the virtual machine.
* What was the outcome of this action?
Miredo fails to start because it tries to lookup a hostname before dhcp
completes.
* What outcome did you expect instead?
Miredo should wait for dhcp complete and then start.
*** End of the template - remove these template lines ***
This is the journal showing the bug:
You can see that it tries to resolve a hostname "teredo-debian.remlab.net"
before dhcp is up.
čen 07 23:16:01 debian-a64 kernel: NET: Registered protocol family 17
čen 07 23:16:01 debian-a64 systemd[1]: Started Raise network interfaces.
čen 07 23:16:01 debian-a64 systemd[1]: Reached target Network.
čen 07 23:16:01 debian-a64 systemd[1]: Starting Permit User Sessions...
čen 07 23:16:01 debian-a64 systemd[1]: Starting Teredo IPv6 tunneling...
čen 07 23:16:01 debian-a64 systemd[1]: Starting OpenBSD Secure Shell server...
čen 07 23:16:01 debian-a64 systemd[1]: Started Permit User Sessions.
čen 07 23:16:01 debian-a64 systemd[1]: Started Serial Getty on ttyAMA0.
čen 07 23:16:01 debian-a64 miredo-checkconf[326]: Invalid hostname
"teredo-debian.remlab.net" at line 6: Dočasná chyba při vyhodnocování jména
čen 07 23:16:01 debian-a64 miredo-checkconf[326]: Server address not specified
čen 07 23:16:01 debian-a64 miredo-checkconf[326]: Fatal configuration error
čen 07 23:16:01 debian-a64 systemd[1]: Started Getty on tty1.
čen 07 23:16:01 debian-a64 dhclient[289]: Listening on
LPF/enp1s0/52:54:00:e3:9b:73
čen 07 23:16:01 debian-a64 sh[268]: Listening on LPF/enp1s0/52:54:00:e3:9b:73
čen 07 23:16:01 debian-a64 sh[268]: Sending on LPF/enp1s0/52:54:00:e3:9b:73
čen 07 23:16:01 debian-a64 sh[268]: Sending on Socket/fallback
čen 07 23:16:01 debian-a64 sh[268]: DHCPDISCOVER on enp1s0 to 255.255.255.255
port 67 interval 7
čen 07 23:16:01 debian-a64 sh[268]: DHCPREQUEST of 192.168.208.2 on enp1s0 to
255.255.255.255 port 67
čen 07 23:16:01 debian-a64 dhclient[289]: Sending on
LPF/enp1s0/52:54:00:e3:9b:73
čen 07 23:16:01 debian-a64 systemd[1]: Reached target Login Prompts.
čen 07 23:16:01 debian-a64 sh[268]: DHCPOFFER of 192.168.208.2 from
192.168.208.1
čen 07 23:16:01 debian-a64 sh[268]: DHCPACK of 192.168.208.2 from 192.168.208.1
čen 07 23:16:01 debian-a64 dhclient[289]: Sending on Socket/fallback
čen 07 23:16:01 debian-a64 dhclient[289]: DHCPDISCOVER on enp1s0 to
255.255.255.255 port 67 interval 7
čen 07 23:16:01 debian-a64 dhclient[289]: DHCPREQUEST of 192.168.208.2 on
enp1s0 to 255.255.255.255 port 67
čen 07 23:16:01 debian-a64 dhclient[289]: DHCPOFFER of 192.168.208.2 from
192.168.208.1
čen 07 23:16:01 debian-a64 dhclient[289]: DHCPACK of 192.168.208.2 from
192.168.208.1
čen 07 23:16:01 debian-a64 systemd[1]: miredo.service: Control process exited,
code=exited status=255
čen 07 23:16:01 debian-a64 systemd[1]: miredo.service: Failed with result
'exit-code'.
čen 07 23:16:01 debian-a64 systemd[1]: Failed to start Teredo IPv6 tunneling.
čen 07 23:16:01 debian-a64 dhclient[289]: bound to 192.168.208.2 -- renewal in
1364 seconds.
čen 07 23:16:01 debian-a64 sh[268]: bound to 192.168.208.2 -- renewal in 1364
seconds.
čen 07 23:16:01 debian-a64 sshd[342]: Server listening on 0.0.0.0 port 22.
čen 07 23:16:01 debian-a64 sshd[342]: Server listening on :: port 22.
čen 07 23:16:01 debian-a64 systemd[1]: Started OpenBSD Secure Shell server.
čen 07 23:16:01 debian-a64 systemd[1]: Reached target Multi-User System.
čen 07 23:16:01 debian-a64 systemd[1]: Reached target Graphical Interface.
čen 07 23:16:01 debian-a64 systemd[1]: Starting Update UTMP about System
Runlevel Changes...
čen 07 23:16:01 debian-a64 systemd[1]: Started Update UTMP about System
Runlevel Changes.
čen 07 23:16:01 debian-a64 systemd[1]: Startup finished in 21.829s (kernel) +
861ms (userspace) = 22.691s.
čen 07 23:16:01 debian-a64 systemd[1]: Reloading OpenBSD Secure Shell server.
čen 07 23:16:01 debian-a64 sh[268]: enp1s0=enp1s0
čen 07 23:16:01 debian-a64 sshd[342]: Received SIGHUP; restarting.
čen 07 23:16:01 debian-a64 systemd[1]: Reloaded OpenBSD Secure Shell server.
čen 07 23:16:01 debian-a64 sshd[342]: Server listening on 0.0.0.0 port 22.
čen 07 23:16:01 debian-a64 sshd[342]: Server listening on :: port 22.
čen 07 23:16:01 debian-a64 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link
becomes ready
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 4.17.0 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8),
LANGUAGE=cs_CZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages miredo depends on:
ii adduser 3.117
ii init-system-helpers 1.51
ii iproute2 4.16.0-4
ii libc6 2.27-3
ii libcap2 1:2.25-1.2
ii libjudydebian1 1.0.5-5
ii lsb-base 9.20170808
ii udev 238-5
miredo recommends no packages.
miredo suggests no packages.
-- no debconf information
