Good afternoon,

I am trying to generate an image for a Raspberry Pi 3 that includes a 
`/etc/network/interfaces` file which causes the Pi to start with an "up" eth0 
connection with only an IPv6 link local address.

The Pi will be connected to an active switch on boot so the copper ethernet 
interface will by electrically up.  So far I have found that unless I set a 
static IPv4 address or connect to a network that uses DHCP to handout IPv4 
addresses by eth0 interface does not come up on boot.  Based on reading the 
interfaces man page I have attempted the following variations I in the 
interfaces file:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
iface eth0 inet6 manual


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet6 manual


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet6 static



auto lo
iface lo inet loopback

auto eth0
iface eth0 inet6 manual
                autoconf 1


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
iface eth0 inet6 manual
                autoconf 1


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
iface eth0 inet6 auto


auto lo
iface lo inet loopback

auto eth0
#iface eth0 inet manual
iface eth0 inet6 auto



This could well be a more general problem with my understanding of how to write 
IPv6 interface files than something specific to the Raspberry Pi running a 
Yocto build.  It is much easier for me to send this email question now though, 
before I start trying to mess around with the same settings on my Ubunut PC to 
see if I can get the behaviour I want out of that.

Any advice or suggestions would be greatfully received.

Regards,

Thomas A. F. Thorne MEng. AUS MIET
Software Engineer

Tel: +44 3450 130 030<tel:+44-3450-130-030>
Email: thomas.tho...@net2edge.com<mailto:thomas.tho...@net2edge.com>
Web: http://www.Net2Edge.com/<http://www.net2edge.com/>

[Net2Edge Logo]

-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to