em(4) does not autonegotiate when fixed media is set

2022-03-02 Thread J.R. Oldroyd
An em(4) interface configured with fixed media/mediatype settings, as in: ifconfig em0 media 100baseTX mediatype full-duplex does not respond to autonegotiation from the switch it is connected to. (Actually, it does for 1000base but not for 100base or 10base.) As a result, the switch may e

Re: em(4) does not autonegotiate when fixed media is set

2022-03-02 Thread tuexen
> On 2. Mar 2022, at 16:33, J.R. Oldroyd wrote: > > An em(4) interface configured with fixed media/mediatype settings, as in: > ifconfig em0 media 100baseTX mediatype full-duplex > does not respond to autonegotiation from the switch it is connected to. > (Actually, it does for 1000base but

Re: em(4) does not autonegotiate when fixed media is set

2022-03-02 Thread Lutz Donnerhacke
On Wed, Mar 02, 2022 at 04:40:38PM +0100, tue...@freebsd.org wrote: > Is that what is expected? When using the above command I would expect > that 100MBit/sec is used, not that the card negotiates with the peer > something else. But my expectations might be wrong... Negotation of a given subset is

Re: em(4) does not autonegotiate when fixed media is set

2022-03-02 Thread J.R. Oldroyd
On Wed, 2 Mar 2022 17:21:22 +0100 Lutz Donnerhacke wrote: > > On Wed, Mar 02, 2022 at 04:40:38PM +0100, tue...@freebsd.org wrote: > > Is that what is expected? When using the above command I would expect > > that 100MBit/sec is used, not that the card negotiates with the peer > > something else. B

Re: em(4) does not autonegotiate when fixed media is set

2022-03-02 Thread tuexen
> On 2. Mar 2022, at 18:04, J.R. Oldroyd wrote: > > On Wed, 2 Mar 2022 17:21:22 +0100 Lutz Donnerhacke > wrote: >> >> On Wed, Mar 02, 2022 at 04:40:38PM +0100, tue...@freebsd.org wrote: >>> Is that what is expected? When using the above command I would expect >>> that 100MBit/sec is used, not

Re: Current with RSS and EPAIR and without INET6.

2022-03-02 Thread Santiago Martinez
Hi Kristof, sorry for my late reply. Im testing without INET. I will keep you updated. Santi On 2/28/22 21:20, Kristof Provost wrote: On 28 Feb 2022, at 21:16, Santiago Martinez wrote: Hi there , yes good point , the first ifdef should go inside the RSS ifdef . Will modify it to also work w

[Bug 262172] UNIX Domain bind() - distinguish between random garbage and alive listening socket

2022-03-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262172 Mike Karels changed: What|Removed |Added CC||kar...@freebsd.org --- Comment #4 fr

[Bug 262172] UNIX Domain bind() - distinguish between random garbage and alive listening socket

2022-03-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262172 --- Comment #5 from f...@cantconnect.ru --- Even disabled by default, it may be used by aware applications in the following way: EADDRINUSE -> assume really busy address, print an error and fail, EEXIST -> remove stale socket and try again,

Re: Current with RSS and EPAIR and without INET6.

2022-03-02 Thread Santiago Martinez
Hi Kristof and Zhenlei, I have updated the patch as requested (wrapped the ifdef INET|INET6 inside the ifdef RSS). It now works without INET6 or without INET. (only tested module loading and interface creation on both cases v4/6). Best regards. Santi @@ -73,8 +73,12 @@__FBSDID("$FreeBSD$"

[Bug 262172] UNIX Domain bind() - distinguish between random garbage and alive listening socket

2022-03-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262172 --- Comment #6 from f...@cantconnect.ru --- Created attachment 232216 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232216&action=edit new patch -- You are receiving this mail because: You are the assignee for the bug.