[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Python 2 and test/vm/netbsd
From: |
Samuel Thibault |
Subject: |
Re: Python 2 and test/vm/netbsd |
Date: |
Tue, 22 Oct 2019 15:10:52 +0200 |
User-agent: |
NeoMutt/20170609 (1.8.3) |
Samuel Thibault, le ven. 18 oct. 2019 18:00:19 +0200, a ecrit:
> Philippe Mathieu-Daudé, le ven. 18 oct. 2019 16:58:00 +0200, a ecrit:
> > On 10/18/19 4:29 PM, Eduardo Habkost wrote:
> > > In addition to that, the connect() error should be generating a
> > > ICMP6_UNREACH message, and I'd expect the NetBSD guest to notice
> > > it instead of waiting for timeout.
> >
> > Is this missing in SLiRP?
>
> It was implemented at the time of introduction of IPv6 in SLIRP. Perhaps
> NetBSD has a slightly different behavior which makes the implementation
> fail to notice the error.
It definitely is there in tcp_input(): on tcp_fconnect() error an
ICMP6_UNREACH message is sent. I can confirm that this works with a
Linux host and Linux guest.
Samuel
- Re: Python 2 and test/vm/netbsd, (continued)
- Re: Python 2 and test/vm/netbsd, Gerd Hoffmann, 2019/10/18
- Re: Python 2 and test/vm/netbsd, Eduardo Habkost, 2019/10/18
- Re: Python 2 and test/vm/netbsd, Philippe Mathieu-Daudé, 2019/10/18
- Re: Python 2 and test/vm/netbsd, Samuel Thibault, 2019/10/18
- Re: Python 2 and test/vm/netbsd, Eduardo Habkost, 2019/10/18
- Re: Python 2 and test/vm/netbsd, Samuel Thibault, 2019/10/22
- Re: Python 2 and test/vm/netbsd, Kamil Rytarowski, 2019/10/22
- Re: Python 2 and test/vm/netbsd,
Samuel Thibault <=