Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-16 Thread Ian Smith
On Tue, 15 Sep 2015 07:51:11 -0600 (MDT), Warren Block wrote: > On Tue, 15 Sep 2015, Ian Smith wrote: > O. Hartmann wrote: > > > But that is an other issue and it is most likely > > > due to the outdated documentation (that doc still uses port 37 for NTP > > > purposes and referes to the ou

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread O. Hartmann
Am Tue, 15 Sep 2015 21:08:51 +1000 (EST) Ian Smith schrieb: > On Tue, 15 Sep 2015 09:47:57 +0200, O. Hartmann wrote: > > On Tue, 15 Sep 2015 10:21:21 +0300 > > Kimmo Paasiala wrote: > > > > > On Tue, Sep 15, 2015 at 10:06 AM, O. Hartmann > > > wrote: > > > > Hopefully, I'm right on this

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread Warren Block
On Tue, 15 Sep 2015, Ian Smith wrote: > But that is an other issue and it is most likely > due to the outdated documentation (that doc still uses port 37 for NTP > purposes and referes to the outdated divert mechanism using natd, see the > recent handbook). The internet is also full of ambigous

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread Ian Smith
On Tue, 15 Sep 2015 09:47:57 +0200, O. Hartmann wrote: > On Tue, 15 Sep 2015 10:21:21 +0300 > Kimmo Paasiala wrote: > > > On Tue, Sep 15, 2015 at 10:06 AM, O. Hartmann > > wrote: > > > Hopefully, I'm right on this list. if not, please forward. > > > > > > Running CURRENT as of FreeBSD 1

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread O. Hartmann
On Tue, 15 Sep 2015 12:59:15 +0300 Alexander V. Chernikov wrote: > > > 15.09.2015, 10:48, "O. Hartmann" : > > On Tue, 15 Sep 2015 10:21:21 +0300 > > Kimmo Paasiala wrote: > > > >>  On Tue, Sep 15, 2015 at 10:06 AM, O. Hartmann > >>   wrote: > >>  > Hopefully, I'm right on this list. if not, pl

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread Alexander V . Chernikov
15.09.2015, 10:48, "O. Hartmann" : > On Tue, 15 Sep 2015 10:21:21 +0300 > Kimmo Paasiala wrote: > >>  On Tue, Sep 15, 2015 at 10:06 AM, O. Hartmann >>   wrote: >>  > Hopefully, I'm right on this list. if not, please forward. >>  > >>  > Running CURRENT as of FreeBSD 11.0-CURRENT #3 r287780: Mon

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread O. Hartmann
On Tue, 15 Sep 2015 10:21:21 +0300 Kimmo Paasiala wrote: > On Tue, Sep 15, 2015 at 10:06 AM, O. Hartmann > wrote: > > Hopefully, I'm right on this list. if not, please forward. > > > > Running CURRENT as of FreeBSD 11.0-CURRENT #3 r287780: Mon Sep 14 13:34:16 > > CEST 2015 amd64, I check via nm

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread O. Hartmann
On Tue, 15 Sep 2015 00:13:33 -0700 Xin Li wrote: > > > On 9/15/15 00:06, O. Hartmann wrote: > > Hopefully, I'm right on this list. if not, please forward. > > > > Running CURRENT as of FreeBSD 11.0-CURRENT #3 r287780: Mon Sep 14 13:34:16 > > CEST 2015 amd64, I check via nmap for open sockets

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread Kimmo Paasiala
On Tue, Sep 15, 2015 at 10:06 AM, O. Hartmann wrote: > Hopefully, I'm right on this list. if not, please forward. > > Running CURRENT as of FreeBSD 11.0-CURRENT #3 r287780: Mon Sep 14 13:34:16 > CEST 2015 amd64, I check via nmap for open sockets since I had trouble > protecting a server with IPFW

Re: HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread Xin Li
On 9/15/15 00:06, O. Hartmann wrote: > Hopefully, I'm right on this list. if not, please forward. > > Running CURRENT as of FreeBSD 11.0-CURRENT #3 r287780: Mon Sep 14 13:34:16 > CEST 2015 amd64, I check via nmap for open sockets since I had trouble > protecting a server with IPFW and NAT. > >

HELP! Mysterious socket 843/tcp listening on CURRENT system

2015-09-15 Thread O. Hartmann
Hopefully, I'm right on this list. if not, please forward. Running CURRENT as of FreeBSD 11.0-CURRENT #3 r287780: Mon Sep 14 13:34:16 CEST 2015 amd64, I check via nmap for open sockets since I had trouble protecting a server with IPFW and NAT. I see a service (nmap) Host is up (0.041s latency).