Re: Problem with receiving packets right after remote-interface is up

2015-09-08 Thread M. V. via freebsd-net
Hi guys, On Sun, 9/6/15, Artem Belevich wrote: > While you can indeed set speed/duplex manually, you will also need > to make sure both have have proper clock master/slave >  selection  which is normally done via autonegotiation. On > Freebsd some interfaces support "mediaopt master" > option ..

Re: Problem with receiving packets right after remote-interface is up

2015-09-06 Thread Artem Belevich
On Sun, Sep 6, 2015 at 2:31 PM, M. V. wrote: > > About disabling auto-negotiation and media options: > My interfaces didn't support master/slave option. I changed interface > media to both "1000BASET" and "100BASETX" instead of auto, but problem was > still there. but interestingly, when I change

Re: Problem with receiving packets right after remote-interface is up

2015-09-06 Thread M. V. via freebsd-net
Thank you guys for your answers. On Sat, Sep 5, 2015 at 2:44 PM, Luigi Rizzo wrote: > You may be able to avoid the issue if you avoid autonegotiation > and manually set the media type, speed and duplex. On Sun, 9/6/15, Artem Belevich wrote: > While you can indeed set speed/duplex manually, you

Re: Problem with receiving packets right after remote-interface is up

2015-09-05 Thread Artem Belevich
On Sat, Sep 5, 2015 at 2:44 PM, Luigi Rizzo wrote: > You may be able to avoid the issue if you avoid autonegotiation and > manually set the media type, speed and duplex. > Technically, 1G ethernet *requires* autonegotiation. http://standards.ieee.org/findstds/interps/IEEE802.3af-2003interp-6.pdf

Re: Problem with receiving packets right after remote-interface is up

2015-09-05 Thread Luigi Rizzo
You may be able to avoid the issue if you avoid autonegotiation and manually set the media type, speed and duplex. Cheers Luigi On Saturday, September 5, 2015, M. V. via freebsd-net < freebsd-net@freebsd.org> wrote: > Hi, > > Our product is being tested with Spirent TestCenter, and we're facing

Problem with receiving packets right after remote-interface is up

2015-09-05 Thread M. V. via freebsd-net
Hi, Our product is being tested with Spirent TestCenter, and we're facing an unusual problem with the tests. We use NICs with intel 82574 and 82576 on FreeBSD 9.2 with latest em and igb drivers (we also tested this on FreeBSD-10.1) It seems what Spirent TestCenter does to start any individual t