[sles-beta] Network Interfaces change name between install and first boot

Darren Thompson darrent at akurit.com.au
Thu Sep 4 15:24:44 MDT 2014


Tom/team

Is this a case where the "ugly but constant" port naming scheme may be more
useful than the more traditional eth(X) port names?

Darren

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au


On 5 September 2014 05:37, Tom Parker <tparker at cbnco.com> wrote:

> Hello
>
> We are doing some RC2 testing with booting servers using /boot on
> microSD cards and / on iscsi with software initiators.
>
> We have run into problems today on our test PC that has 1 onboard nic
> and 1 PCI nic with 4 ports.  During the installation process the onboard
> nic appears as eth3 but after the first reboot it is eth0.
>
> This is obviously causing havoc with the network setup as dracut is
> setting up the wrong interface on first boot and / is not found.
>
> Should I submit an SR for this?
>
> Tom
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140905/cd334e9a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140905/cd334e9a/attachment.jpg>


More information about the sles-beta mailing list