So, I would check into the link partner, often times it can be the culprit, try the nic in a simple back-to-back setup and see if it makes a diff, etc. etc...
Jack On Wed, Sep 28, 2016 at 9:03 AM, Andrew Savchenko <gradiomet...@gmail.com> wrote: > Nope, unfortunately they stay dead (aka "no carrier") until `netif > restart`. > > On Wed, Sep 28, 2016 at 6:12 PM, Freddie Cash <fjwc...@gmail.com> wrote: > > > On Wed, Sep 28, 2016 at 8:02 AM, Andrew Savchenko < > gradiomet...@gmail.com> > > wrote: > > > >> MAC's and IP's are abviously changed. > >> For the moment being I have "solved" this by a tiny script in /etc/rc.d/ > >> that restarts networking & routing after the system boot: > >> > > > > Do the NICs eventually pick up carrier status if you leave it after > > boot? Could it just be slow picking up status changes? We had a couple > > em(4) or igb(4) (forget now) NICs that were like that. Took a good > minute > > after boot before the NIC was finished initialising and detected the > link. > > > > If that's the case, and you don't mind the wait (and want to make sure > > networking is working once the boot is complete), you can use the > netwait_* > > options in /etc/rc.conf. That will pause the boot process until either > the > > network link status changes to up, and/or you can ping the default > gateway > > or any other IP on the network. > > > > Worked for us. Might work for you. > > > > > > -- > > Freddie Cash > > fjwc...@gmail.com > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
