Date: Sat, 30 Sep 2017 18:19:30 -0700 From: Lee Brown <leeb@ratnaling.org> To: freebsd-net <freebsd-net@freebsd.org> Subject: Re: Problem with igb NIC on fresh 11 Install Message-ID: <CAFPNf58V3nHL%2Bde_uwmC0fJwQAvUCK8w6HFqiEGc4Wyf7ShePA@mail.gmail.com> In-Reply-To: <100a8795-8b3c-e1b4-5fab-e79565761f6a@FreeBSD.org> References: <CAFPNf5-AjO2hq796i58RQ9oDe0WmoWd_wU2onFU20Ff3eAXheQ@mail.gmail.com> <CAFPNf5_fTmSgaD3DN2erg04LUbZKdKJvGVyNL-cmFs=srTrWKw@mail.gmail.com> <100a8795-8b3c-e1b4-5fab-e79565761f6a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
OCR conversion is why the text is garbled. It appears if the parent NIC has no address assigned to it, it remains in the DOWN state. Manually UP-ing the igb0 interface got the VLAN's working. Adding VLANs to an interface doesn't UP the NIC and it took me a long time to realize that. Apparently I've never configured a pure trunk on FreeBSD before! The one-way traffic without VLAN (igb0 got an ip address so it went UP) was because the switch's port configuration was intentionally blocking VLAN1 (aka untagged packets), which apparently means block egress but allow ingress. Thanks for the feedback Matt. On Sat, Sep 30, 2017 at 5:41 PM, Matt Joras <mjoras@freebsd.org> wrote: > On 09/30/2017 11:36, Lee Brown wrote: > > It looks like the driver is not passing packets from the VLAN layer to > the > > NIC. Switch counters verify this and netstat seems to indicate the same. > > ... > > root@rtr-net-r1: - # ifconfig igb0 > > igb0: flags=8c02<EIRORDCRST,ORCTIVE,SIMPLEX,MULTICRST> metric 0 mtu 1500 > > igb0 looks to be OACTIVE, (though I'm not sure why all your A's are > swapped with R's). When it's OACTIVE it will drop packets and generally > behave as if the link is down. Does igb0 stay in OACTIVE indefinitely, > or does it go back to a normal state at any point? > > Matt > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFPNf58V3nHL%2Bde_uwmC0fJwQAvUCK8w6HFqiEGc4Wyf7ShePA>