On 11/9/2020 7:32 AM, Lev Serebryakov wrote:
> On 07.11.2020 2:46, Eric Joyner wrote:
>
>> The other issue is that I still don't know which devices need a
>> restart / which devices do not, or whether a restart is strictly
>> necessary and if there is another way to do this without worrying
>>
On 07.11.2020 2:46, Eric Joyner wrote:
The other issue is that I still don't know which devices need a restart / which
devices do not, or whether a restart is strictly necessary and if there is
another way to do this without worrying about restarting the device.
Could this be copied from
Ah -- I didn't implement the fix I had in that bugzilla correctly -- em and
igb devices will use the same function instead of using two different ones
even though it seems em devices generally require the interface restart yet
igb devices do not.
The other issue is that I still don't know which
On 11/6/2020 5:32 PM, Eric Joyner wrote:
> Could you reply to that issue with what you've found?
>
> Though, as far as I can recall, igb(4) devices are not supposed to do
> the iflib reset talked about in the bug, so I wouldn't expect to see a
> link flap on those.
>
Hi Eric,
I have added my
Could you reply to that issue with what you've found?
Though, as far as I can recall, igb(4) devices are not supposed to do
the iflib reset talked about in the bug, so I wouldn't expect to see a link
flap on those.
- Eric
On Fri, Nov 6, 2020 at 12:48 PM mike tancsa wrote:
> On 11/6/2020 2:17
On 11/6/2020 2:17 PM, mike tancsa wrote:
> On 5/31/2020 5:39 PM, Lev Serebryakov wrote:
>> Hello Ian,
>>
>> Thursday, May 28, 2020, 2:45:48 AM, you wrote:
>>
>>> I noticed that my VLAN interfaces stopped working after a recent build.
>>> tcpdump showed traffic leaving leaving and entering the
On 5/31/2020 5:39 PM, Lev Serebryakov wrote:
> Hello Ian,
>
> Thursday, May 28, 2020, 2:45:48 AM, you wrote:
>
>> I noticed that my VLAN interfaces stopped working after a recent build.
>> tcpdump showed traffic leaving leaving and entering the interface but no
>> host on the network actually
Hello Ian,
Thursday, May 28, 2020, 2:45:48 AM, you wrote:
> I noticed that my VLAN interfaces stopped working after a recent build.
> tcpdump showed traffic leaving leaving and entering the interface but no
> host on the network actually received any packets from this host. A
> binary search
Hi
I'm told the content was stripped from my emails...
I noticed that my VLAN interfaces stopped working after a recent build.
tcpdump showed traffic leaving leaving and entering the interface but no
host on the network actually received any packets from this host. A
binary search led me
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Le 27/05/2020 à 09:33, Marek Zarychta a écrit :
> W dniu 27.05.2020 o 09:19, Martin MATO pisze:
>> I was about to fill a bug report about this.
>> My network card in that case is a 82574L intel based adapter
>> As a workaround; bringing down and up the link by ifconfig(8) (and not
>> by
W dniu 27.05.2020 o 09:19, Martin MATO pisze:
> I was about to fill a bug report about this.
> My network card in that case is a 82574L intel based adapter
> As a workaround; bringing down and up the link by ifconfig(8) (and not
> by unplug/replug the ethernet cable)
> restore the connectivity
-based authentication)
and also i narrowed down when the problem appears, and it is at this
revision (r360902)
Do you have filled a bug report?
>
> envoyé : 26 mai 2020 à 23:53
> de : Ian FREISLICH
> à : curr...@freebsd.org
> objet : r360902 breaks VLAN interface on
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
15 matches
Mail list logo
