Date: Wed, 28 Sep 2016 20:10:22 +0300 From: Andrew Savchenko <gradiometric@gmail.com> To: Jack Vogel <jfvogel@gmail.com> Cc: Freddie Cash <fjwcash@gmail.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: "igb" interfaces aren't picking up media on boot Message-ID: <CAPUkqa5jNDDCZXSjaO=jA_5=VV0L4hppneCJchdb7bbwpfrY9g@mail.gmail.com> In-Reply-To: <CAFOYbckpgd0KONjSPqp_zYt6mys%2B-T0Jbp5JzF4bWrLpwUWyRw@mail.gmail.com> References: <CAPUkqa7-oRuparA_dhLmT8J17w6GVeqMfaFvjzHVDir--6qvSA@mail.gmail.com> <653b4473-558b-5ef8-41b7-080ec6c5584d@multiplay.co.uk> <2A35EA60C3C77D438915767F458D65688394B821@ORSMSX111.amr.corp.intel.com> <CAPUkqa7ngE9ptd8oYRYjCru5Kh7H_LSOqi6gVpy-eUqiR5jwVQ@mail.gmail.com> <CAOjFWZ7XE%2B26fewtuudN1FwKP1be%2BQLcFsy64z3c__303kmGxg@mail.gmail.com> <CAPUkqa4BkZjmSepC2uWUKWeGJWwVjRyKyE85DzEJyKxKtyVrjg@mail.gmail.com> <CAFOYbckzmxxOD1oh7OtqZLDshu9F8pdjWDPpggEBE0no3rRDog@mail.gmail.com> <CAPUkqa706MsVTu16o9TfWZeRzKgrHfo%2B3JpWLKsyvGr6b-XUdA@mail.gmail.com> <CAFOYbckpgd0KONjSPqp_zYt6mys%2B-T0Jbp5JzF4bWrLpwUWyRw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I would love to, but it's the property of Datacenter :D All I can do is to adapt my box to it. On Wed, Sep 28, 2016 at 8:09 PM, Jack Vogel <jfvogel@gmail.com> wrote: > So, time to ditch the DLink I'd say :) > > On Wed, Sep 28, 2016 at 9:29 AM, Andrew Savchenko <gradiometric@gmail.com= > > wrote: > >> I've been using this particular NIC under FreeBSD 10.0-REL connected via >> cross cable to another Intel NIC / two different routers / TP-Link switc= h >> without any similar issues. The problem shows only with the mentioned DL= ink >> switch. >> >> On Wed, Sep 28, 2016 at 7:20 PM, Jack Vogel <jfvogel@gmail.com> wrote: >> >>> 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 < >>> gradiometric@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 <fjwcash@gmail.com> >>>> wrote: >>>> >>>> > On Wed, Sep 28, 2016 at 8:02 AM, Andrew Savchenko < >>>> gradiometric@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: >>>> >> >>>> > >>>> > =E2=80=8BDo 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 su= re >>>> > 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.=E2=80=8B >>>> > >>>> > >>>> > -- >>>> > Freddie Cash >>>> > fjwcash@gmail.com >>>> > >>>> _______________________________________________ >>>> freebsd-net@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-net >>>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >>> >>> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPUkqa5jNDDCZXSjaO=jA_5=VV0L4hppneCJchdb7bbwpfrY9g>