Date: Fri, 21 Sep 2001 19:30:21 +0200 From: "Ruben de Groot" <ruben@1729.net> To: <freebsd-questions@FreeBSD.ORG> Cc: "Andreas Ntaflos" <ntaflos.andreas@gmx.net> Subject: Re: connection attempt to 127.0.0.1:xxx from 127.0.0.1:yyy? Message-ID: <000e01c142c3$1702cd00$0801a8c0@lan.1729.net> References: <20010921172704.A7202@Bender.ANT>
next in thread | previous in thread | raw e-mail | index | archive | help
This is not a connection being blocked. Some process is making an auth request on the loopback interface, but there's nobody listening. If you don't want this message in your logs you could uncomment one of the lines starting with #auth in /etc/inetd.conf. greetings, Ruben ----- Original Message ----- From: "Andreas Ntaflos" <ntaflos.andreas@gmx.net> To: <freebsd-questions@FreeBSD.ORG> Sent: Friday, September 21, 2001 5:27 PM Subject: connection attempt to 127.0.0.1:xxx from 127.0.0.1:yyy? > Hello questions, > I am wondering why syslog shows me such messages.. > > /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1376 > for example. > > log_in_vain is enabled, but why should connections on the > loopback interface be blocked? This is also beyond the ipfilter firewalling > rules/level, which do/does allow any kind of traffic on the loop- > back if/localhost. I noticed this when I used mpg123 to play > mp3s, which always worked well (I cron'ed it to wake me up > in the morning for example), but some weeks ago or so it > stopped and I don't know why this could be. > > Anyone have an idea? > -- > Andreas Ntaflos, ANT > ntaflos.andreas@gmx.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000e01c142c3$1702cd00$0801a8c0>