jail - vnet bug - ping: UDP connect: No route to host

2021-04-10 Thread Özkan KIRIK
Hello, There is something wrong about routing lookup on vnet-jails. Although my jail doesn't have IPv6 address, it tries to use IPv6 by default and get "ping: UDP connect: No route to host" error. But it works by forcing to use IPv4. The problem is reproducable. This is a fresh insallation of Fre

Re: NFS Mount Hangs

2021-04-10 Thread Rick Macklem
tue...@freebsd.org wrote: >Rick wrote: [stuff snipped] >>> With r367492 you don't get the upcall with the same error state? Or you >>> don't get an error on a write() call, when there should be one? > If Send-Q is 0 when the network is partitioned, after healing, the krpc sees > no activity on >

AW: NFS Mount Hangs

2021-04-10 Thread Scheffenegger, Richard
I went through all the instances, where there would be an immediate soupcall triggered (before r367492). If the problem is related to a race condition, where the socket is unlocked before the upcall, I can change the patch in such a way, to retain the lock on the socket all through TCP processi

Re: NFS Mount Hangs

2021-04-10 Thread tuexen
> On 10. Apr 2021, at 17:56, Rick Macklem wrote: > > Scheffenegger, Richard wrote: >>> Rick wrote: >>> Hi Rick, >>> Well, I have some good news and some bad news (the bad is mostly for Richard). The only message logged is: tcpflags 0x4; tcp_do_segment: Timestamp missi

Re: NFS Mount Hangs

2021-04-10 Thread Rick Macklem
Scheffenegger, Richard wrote: >>Rick wrote: >> Hi Rick, >> >>> Well, I have some good news and some bad news (the bad is mostly for >>> Richard). >>> >>> The only message logged is: >>> tcpflags 0x4; tcp_do_segment: Timestamp missing, segment processed >>> normally >>> Btw, I did get one additio

Re: NFS Mount Hangs

2021-04-10 Thread tuexen
> On 10. Apr 2021, at 17:04, Rick Macklem wrote: > > tue...@freebsd.org wrote: >>> On 10. Apr 2021, at 02:44, Rick Macklem wrote: >>> >>> tue...@freebsd.org wrote: > On 6. Apr 2021, at 01:24, Rick Macklem wrote: > > tue...@freebsd.org wrote: > [stuff snipped] >> OK. What i

Re: NFS Mount Hangs

2021-04-10 Thread Rick Macklem
tue...@freebsd.org wrote: >> On 10. Apr 2021, at 02:44, Rick Macklem wrote: >> >> tue...@freebsd.org wrote: On 6. Apr 2021, at 01:24, Rick Macklem wrote: tue...@freebsd.org wrote: [stuff snipped] > OK. What is the FreeBSD version you are using? main Dec. 23, 2020. >>>

Re: NFS Mount Hangs

2021-04-10 Thread Scheffenegger, Richard
Von: tue...@freebsd.org Gesendet: Samstag, April 10, 2021 2:19 PM An: Scheffenegger, Richard Cc: Rick Macklem; Youssef GHORBAL; freebsd-net@freebsd.org Betreff: Re: NFS Mount Hangs NetApp Security WARNING: This is an external email. Do not click links or open

Re: NFS Mount Hangs

2021-04-10 Thread tuexen
> On 10. Apr 2021, at 11:19, Scheffenegger, Richard > wrote: > > Hi Rick, > >> Well, I have some good news and some bad news (the bad is mostly for >> Richard). >> >> The only message logged is: >> tcpflags 0x4; tcp_do_segment: Timestamp missing, segment processed >> normally >> >> But...th

Re: NFS Mount Hangs

2021-04-10 Thread tuexen
> On 10. Apr 2021, at 02:44, Rick Macklem wrote: > > tue...@freebsd.org wrote: >>> On 6. Apr 2021, at 01:24, Rick Macklem wrote: >>> >>> tue...@freebsd.org wrote: >>> [stuff snipped] OK. What is the FreeBSD version you are using? >>> main Dec. 23, 2020. >>> It seems that the TC

[Bug 240944] em(4): Crash with Intel 82571EB NIC with AMD Piledriver and Steamroller APUs

2021-04-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240944 Alin changed: What|Removed |Added CC||alin...@yahoo.com --- Comment #6 from Alin

AW: NFS Mount Hangs

2021-04-10 Thread Scheffenegger, Richard
Hi Rick, > Well, I have some good news and some bad news (the bad is mostly for Richard). > > The only message logged is: > tcpflags 0x4; tcp_do_segment: Timestamp missing, segment processed > normally > > But...the RST battle no longer occurs. Just one RST that works and then the > SYN gets SYN