Network Interface name change

[Sami Halabi]

Hi,
the simest way is to write a script that seeks for MACs and sets names upon
system restart.

of course if anyone has an elegant way or patch its bretter.

Sami
בתאריך 13 באפר׳ 2015 19:14,‏ "Raimund Sacherer" <rs at logitravel.com> כתב:

> Hello,
>
> We have one firewall (out of a cluster) in a very remote area and it
> displays erratic behaviour. On reboot, sometimes it initialises network
> port 0 correctly and sometimes it does not.
>
> I firmly believe it has to do with the KVM port being active on port 0 and
> I had lot's of troubles with it (working/not working) so it's a gamble if
> port 0 can be initialised on reboot or not. And more often then not it
> doesn't come up correctly.
>
> When it does not work I get this in the boot log:
>
> em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xf060-0xf07f mem
> 0xf7c00000-0xf7c1ffff,0xf7c34000-0xf7c34fff irq 20 at device 25.0 on pci0
> em0: Using an MSI interrupt
> em0: Setup of Shared code failed
> device_attach: em0 attach returned 6
>
>
>
> My real problem is that once this happens the port which should be em1
> will now be em0 and then all my port assignments don't work anymore. In
> anticipation of this possible error I configured the VLANs on the switches
> accordingly so at least I can get access to the firewall and can work on
> it, but I do not know how I can force e.g. that MAC XX is always em1 (or
> em2, em3) regardless of what the BIOS or the boot process think it should
> be.
>
>
> Thank you,
> Best
> Ray
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>