Re: netstat *:* udp sockets

2018-12-17 Thread Ted Unangst
Sebastian Benoit wrote: > > > or what should it show? Only sockets that are bound > > > but not connected (local port != 0 but remote addr/port = 0)? > > > > see my other mail for that diff. > > here. Ok for one or the other? as a non expert, this matches my expectation of what "listening"

Re: netstat *:* udp sockets

2018-12-17 Thread Claudio Jeker
On Mon, Dec 17, 2018 at 06:05:00PM +0100, Sebastian Benoit wrote: > Sebastian Benoit(benoit-li...@fb12.de) on 2018.12.17 17:59:49 +0100: > > Claudio Jeker(cje...@diehard.n-r-g.com) on 2018.12.17 08:25:07 +0100: > > > On Sun, Dec 16, 2018 at 05:09:06PM -0500, Ted Unangst wrote: > > > > Claudio

Re: netstat *:* udp sockets

2018-12-17 Thread Sebastian Benoit
Sebastian Benoit(benoit-li...@fb12.de) on 2018.12.17 17:59:49 +0100: > Claudio Jeker(cje...@diehard.n-r-g.com) on 2018.12.17 08:25:07 +0100: > > On Sun, Dec 16, 2018 at 05:09:06PM -0500, Ted Unangst wrote: > > > Claudio Jeker wrote: > > > > On Fri, Dec 14, 2018 at 01:26:25PM -0500, Ted Unangst

Re: netstat *:* udp sockets

2018-12-17 Thread Sebastian Benoit
Claudio Jeker(cje...@diehard.n-r-g.com) on 2018.12.17 08:25:07 +0100: > On Sun, Dec 16, 2018 at 05:09:06PM -0500, Ted Unangst wrote: > > Claudio Jeker wrote: > > > On Fri, Dec 14, 2018 at 01:26:25PM -0500, Ted Unangst wrote: > > > > Philip Guenther wrote: > > > > > And, perhaps more directly, how

Re: netstat *:* udp sockets

2018-12-17 Thread Consus
On 08:25 Mon 17 Dec, Claudio Jeker wrote: > On Sun, Dec 16, 2018 at 05:09:06PM -0500, Ted Unangst wrote: > > Claudio Jeker wrote: > > > On Fri, Dec 14, 2018 at 01:26:25PM -0500, Ted Unangst wrote: > > > > Philip Guenther wrote: > > > > > And, perhaps more directly, how would I block this in

Re: netstat *:* udp sockets

2018-12-16 Thread Claudio Jeker
On Sun, Dec 16, 2018 at 05:09:06PM -0500, Ted Unangst wrote: > Claudio Jeker wrote: > > On Fri, Dec 14, 2018 at 01:26:25PM -0500, Ted Unangst wrote: > > > Philip Guenther wrote: > > > > And, perhaps more directly, how would I block this in pf.conf? > > > > > > > > > > > > > Excellent choice,

Re: netstat *:* udp sockets

2018-12-16 Thread Ted Unangst
Claudio Jeker wrote: > On Fri, Dec 14, 2018 at 01:26:25PM -0500, Ted Unangst wrote: > > Philip Guenther wrote: > > > And, perhaps more directly, how would I block this in pf.conf? > > > > > > > > > > Excellent choice, blocking dhclient from receiving the leases that it > > > requests. > > > "What

Re: netstat *:* udp sockets

2018-12-16 Thread Claudio Jeker
On Fri, Dec 14, 2018 at 01:26:25PM -0500, Ted Unangst wrote: > Philip Guenther wrote: > > And, perhaps more directly, how would I block this in pf.conf? > > > > > > > Excellent choice, blocking dhclient from receiving the leases that it > > requests. > > "What problem are you trying to solve?" >

Re: netstat *:* udp sockets

2018-12-14 Thread Theo de Raadt
>Ted Unangst wrote: >> Philip Guenther wrote: >> > And, perhaps more directly, how would I block this in pf.conf? >> > > >> > >> > Excellent choice, blocking dhclient from receiving the leases that it >> > requests. >> > "What problem are you trying to solve?" >> >> Well, this may be something

Re: netstat *:* udp sockets

2018-12-14 Thread Theo de Raadt
>Philip Guenther wrote: >> And, perhaps more directly, how would I block this in pf.conf? >> > >> >> Excellent choice, blocking dhclient from receiving the leases that it >> requests. >> "What problem are you trying to solve?" > >Well, this may be something of a lost cause, but I would prefer

Re: netstat *:* udp sockets

2018-12-14 Thread Ted Unangst
Ted Unangst wrote: > Philip Guenther wrote: > > And, perhaps more directly, how would I block this in pf.conf? > > > > > > > Excellent choice, blocking dhclient from receiving the leases that it > > requests. > > "What problem are you trying to solve?" > > Well, this may be something of a lost

Re: netstat *:* udp sockets

2018-12-14 Thread Ted Unangst
Philip Guenther wrote: > And, perhaps more directly, how would I block this in pf.conf? > > > > Excellent choice, blocking dhclient from receiving the leases that it > requests. > "What problem are you trying to solve?" Well, this may be something of a lost cause, but I would prefer that chrome

Re: netstat *:* udp sockets

2018-12-14 Thread Stuart Henderson
On 2018-12-14, Sebastian Benoit wrote: > As for chrome, i have no idea what it is doing... ;) My first guess would be maybe it's using this to send probes for QUIC / HTTP/3. I don't see that in chromium here but maybe something in testing (they run different "field trials" for different people)

Re: netstat *:* udp sockets

2018-12-14 Thread Consus
On 13:38 Thu 13 Dec, Ted Unangst wrote: > netstat -an tells me I am listening to all the udp. > > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address(state) > udp 0 0 *.**.* >

Re: netstat *:* udp sockets

2018-12-14 Thread Sebastian Benoit
Ted Unangst(t...@tedunangst.com) on 2018.12.13 13:38:58 -0500: > netstat -an tells me I am listening to all the udp. > > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address(state) > udp 0 0 *.*

Re: netstat *:* udp sockets

2018-12-14 Thread Janne Johansson
Den fre 14 dec. 2018 kl 03:58 skrev Philip Guenther : > On Thu, Dec 13, 2018 at 10:40 AM Ted Unangst wrote: > > netstat -an tells me I am listening to all the udp. > > > > Active Internet connections (including servers) > > Proto Recv-Q Send-Q Local Address Foreign Address > > (state)

Re: netstat *:* udp sockets

2018-12-13 Thread Philip Guenther
On Thu, Dec 13, 2018 at 10:40 AM Ted Unangst wrote: > netstat -an tells me I am listening to all the udp. > > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address > (state) > udp 0 0 *.**.* > udp