[SLOF] [PATCH 0/6] net-snk: More IPv6 fixes and improvements
thuth at redhat.com
Thu Jan 14 20:41:55 AEDT 2016
On 14.01.2016 10:21, Thomas Huth wrote:
> On 14.01.2016 09:18, Alexey Kardashevskiy wrote:
>> For my tests I have a virtual bridge which is not connected anywhere,
>> and 3 guests:
>> 1. "dhcpv6" guest, fc23, one interface, attached to bridge#1, static IP
>> (fd00:4149:4b00::1), running dmasq with DHCP on and TFTP off, with RA
>> and everything.
>> 2. "tftp" guest, fc23, two interfaces - one is attached to bridge#1 and
>> received IPv6 via DHCP (fd00:4149:4b00::bc)
Another question: I assume it also uses the address fd00:4149:4b01::1 ?
Otherwise, you're bootfile URL below does not match.
>> another interface is not
>> attached anywhere and has a static IP (d00:4149:4b01::1); this guest is
>> also running dnsmasq but DHCP is off there and TFTP is on.
>> 3. test guest to boot via IPv6 (so - only SLOF, no disk image or
>> initramdisk), one interface, attached to the same bridge, it gets IP
>> over DHCP (fd00:4149:4b00:0:c041:49ff:fe4b:5 - which is quite weird but
SLOF only gets addresses via stateless autoconfiguration so far, it does
not get addresses via DHCPv6 yet (it only uses DHCPv6 for retrieving the
bootfile URL). That's why you get this address here.
>> and it receives TFTP image name via dhcp6 and tries downloading it
>> but fails.
>> If I move TFTP from 2 to 1 (i.e. from fd00:4149:4b01::1 to
>> fd00:4149:4b00::1), then SLOF can download the image and boot.
>> I tried pinging fd00:4149:4b01::1 from guest#3 (booted it from a disk
>> image, received fd00:4149:4b00::bd from dhcp), it worked so routing
>> works fine (I added a route and enabled forwarding on guest#1).
Another thing to try: Can you download something in SLOF when you
specify the TFTP server and client addresses manually (i.e. without
DHCPv6 and routing involved)? Something like:
More information about the SLOF