Re: BPF to filter/mod ARP

> Hi group, > > Maybe someone can help me with this question - as I am usually only > looking at L4 and the top side of L3 ;) > > In order to validate a peculiar switches behavior, I want to adjust some > fields in gracious arps sent out by an interface, after a new IP is > assigned or changed

Re: BPF to filter/mod ARP

> On 1. Mar 2023, at 22:10, Scheffenegger, Richard > wrote: > >>> On 1. Mar 2023, at 21:33, Scheffenegger, Richard >>> wrote: >>> >>> Hi group, >>> >>> Maybe someone can help me with this question - as I am usually only looking >>> at L4 and the top side of L3 ;) >> >>> In order to validat

RE: BPF to filter/mod ARP

>> On 1. Mar 2023, at 21:33, Scheffenegger, Richard wrote: >> >> Hi group, >> >> Maybe someone can help me with this question - as I am usually only looking >> at L4 and the top side of L3 ;) > >> In order to validate a peculiar switches behavior, I want to adjust some >> fields in gracious arps

mlx5en & tcpdump -Q

Related to the other issue just mentioned, I found that when trying to perform unidirectional packet captures using the tcpdump -Q option, when trying this against a CX5 NIC, i get this error message: tcpdump: e4a: pcap_setdirection() failed: Setting direction is not implemented on this platfo

Re: BPF to filter/mod ARP

> On 1. Mar 2023, at 21:33, Scheffenegger, Richard wrote: > > Hi group, > > Maybe someone can help me with this question - as I am usually only looking > at L4 and the top side of L3 ;) > > In order to validate a peculiar switches behavior, I want to adjust some > fields in gracious arps sent

BPF to filter/mod ARP

Hi group, Maybe someone can help me with this question - as I am usually only looking at L4 and the top side of L3 ;) In order to validate a peculiar switches behavior, I want to adjust some fields in gracious arps sent out by an interface, after a new IP is assigned or changed. I believe

Re: sshd doesn't disconnect for 30+ minutes after the TCP connection is closed ungracefully

On 1 Mar 2023, at 5:36, Michael Gmelin wrote: >> On 1. Mar 2023, at 11:35, Yuri wrote: >> >> Windows system connects to FreeBSD through ssh and then this connection >> dies because of WiFi or VPN issues. >> >> FreeBSD still has the sshd process alive for this connection for 30+ minutes. >> >> T

Re: sshd doesn't disconnect for 30+ minutes after the TCP connection is closed ungracefully

> On 1. Mar 2023, at 11:35, Yuri wrote: > > Windows system connects to FreeBSD through ssh and then this connection dies > because of WiFi or VPN issues. > > FreeBSD still has the sshd process alive for this connection for 30+ minutes. > > TCP keepalive is enabled on the FreeBSD host: > >

sshd doesn't disconnect for 30+ minutes after the TCP connection is closed ungracefully

Windows system connects to FreeBSD through ssh and then this connection dies because of WiFi or VPN issues. FreeBSD still has the sshd process alive for this connection for 30+ minutes. TCP keepalive is enabled on the FreeBSD host: $ sysctl net.inet.tcp.always_keepalive net.inet.tcp.always_k