Re: inetd echo localhost

2023-07-21 Thread Alexander Bluhm
On Fri, Jul 21, 2023 at 03:05:41PM +0200, Claudio Jeker wrote: > On Fri, Jul 21, 2023 at 03:17:35PM +0300, Vitaliy Makkoveev wrote: > > On Thu, Jul 20, 2023 at 09:57:00PM +0200, Alexander Bluhm wrote: > > > Hi, > > > > > > I wonder why UDP echo does not work with inetd on 127.0.0.1. > > > > > >

Re: inetd echo localhost

2023-07-21 Thread Claudio Jeker
On Fri, Jul 21, 2023 at 03:17:35PM +0300, Vitaliy Makkoveev wrote: > On Thu, Jul 20, 2023 at 09:57:00PM +0200, Alexander Bluhm wrote: > > Hi, > > > > I wonder why UDP echo does not work with inetd on 127.0.0.1. > > > > Note that it is default off. One of my regress machines has it > > enabled

Re: inetd echo localhost

2023-07-21 Thread Vitaliy Makkoveev
On Thu, Jul 20, 2023 at 09:57:00PM +0200, Alexander Bluhm wrote: > Hi, > > I wonder why UDP echo does not work with inetd on 127.0.0.1. > > Note that it is default off. One of my regress machines has it > enabled for other tests. There perl dist/Net-Ping/t/510_ping_udp.t > expects that UDP

inetd echo localhost

2023-07-20 Thread Alexander Bluhm
Hi, I wonder why UDP echo does not work with inetd on 127.0.0.1. Note that it is default off. One of my regress machines has it enabled for other tests. There perl dist/Net-Ping/t/510_ping_udp.t expects that UDP echo works on 127.0.0.1. It was disabled with this commit: