IPv6 address is not displayed in 'Start SSH' invitation during booting the installer

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

------- Comment From <email address hidden> 2016-03-03 06:19 EDT-------
A problem fix is attached on the Debian bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816600

This bug was fixed in the package network-console - 1.54

---------------
network-console (1.54) unstable; urgency=medium

  [ Dimitri John Ledkov ]
  * Adjust regexpes to include all ipv4 and ipv6 addresses, list all ip
    addresses (sans loopback) in the template instructions, and use only
    the first ip address in the example command. Closes: #816600 LP:
    #1552368
  * Adjust variable name in template translations.

 -- Dimitri John Ledkov <email address hidden> Fri, 01 Apr 2016 11:52:11 +0100

debian-installer will need a rebuild.

This bug was fixed in the package debian-installer - 20101020ubuntu445

---------------
debian-installer (20101020ubuntu445) xenial; urgency=medium

  * Add necessory files to enable FTP Load / IPL on s390x, ported from
    debian-cd.
  * Drop s390-dasd, is now pulled in via hw-detect /
    harddrive-detection-dasd.
  * Rebuild with ipv6 capable network-console. LP: #1552368

 -- Dimitri John Ledkov <email address hidden> Tue, 05 Apr 2016 09:51:35 +0100

------- Comment From <email address hidden> 2016-04-06 08:04 EDT-------
The package debian-installer - 20101020ubuntu445 was used for fix verification.
But the bug looks like not fixed, two problems take place:

1. The listed IPv6 address fe80::ff:fe73:ed45 is not the address which was used in the parm.file
(netcfg/get_ipaddress=fd00:9:152:48:1822:ffff:162:25/80)

2. It is impossible to connect via SSH neither to fe80::ff:fe73:ed45, nor to fd00:9:152:48:1822:ffff:162:25:

ubuntu@s8330049:~> ssh installer@fe80::ff:fe73:ed45
ssh: connect to host fe80::ff:fe73:ed45 port 22: Invalid argument
ubuntu@s8330049:~> ssh installer@fd00:9:152:48:1822:ffff:162:25
ssh: connect to host fd00:9:152:48:1822:ffff:162:25 port 22: No route to host

So it is impossible to continue the installation.

------- Comment (attachment only) From <email address hidden> 2016-04-06 08:05 EDT-------

------- Comment (attachment only) From <email address hidden> 2016-04-06 08:06 EDT-------

@irina-yashina

please open a new bug report

please include full installer logs (/var/log/installer from the installed system, or if you didn't complete the install, /var/log/syslog from the running d-i after the bug was reproduced)

all available IP addresses should be listed from now on. As standard with fe80 ipv6 addresses one must also specify the local interface from the client one wishes to use to connect to an fe80 address.

the actual bug you are trying to report now is that fd00:9:152:48:1822:ffff:162:25/80 was expected to be used and configured, but was not at all configured nor used. There are hints that an ipv4 address 9.152.162.25 was used instead.

This is entirely out of scope for this bug report. This bug report is about not showing ipv6 addresses whats-so-ever in the network-console package, and nothing to do with which ip addresses netcfg packages chooses to configure. Please open a new bug report with requested installer logs.

------- Comment From <email address hidden> 2016-04-06 10:47 EDT-------
Fixed with installer version 445.

Detecting link on encf5f0; please
wait...
Generating SSH host key
Continue installation remotely using SSH
----------------------------------------
Start SSH
To continue the installation, please use an SSH client to connect to the IP
address fd00:9:152:48:1822:ffff:162:104 fe80::a2:fff:fe00:3c and log in as the
"installer" user. For example:
ssh installer@fd00:9:152:48:1822:ffff:162:104
The fingerprint of this SSH server's host key is:
SHA256:o/pHy0rY7REGJy4dknd1fCO9zPXmaUUDcyHPwu4wOWc
Please check this carefully against the fingerprint reported by your SSH
client.
?Press enter to continue?

... and login to the system is possible, as advised - if you have a machine with IPv6 connection:
ubuntu@s8330049:~> ssh installer@fd00:9:152:48:1822:ffff:162:104

closing this bug.