Re: What's changed relating to localhost then?
I've just updated to 5.2-BETA today and have noticed that my spamd is now rejecting all connections from spamc because they are not coming from 127.0.0.1 any more. It's now using my public IP address of 82.x.x.x: Nov 22 14:38:30 womble spamd[657]: unauthorized connection from 82-32-25-111.cable.ubr04.azte.blueyonder.co.uk [82.32.25.111] at port 49167 I noticed somebody reported a similar thing earlier. It was me, I'm glad not to be dumb. I note also that metacity takes ages to start. I'm waiting a new change to network code in order to compile another -CURRENT. I'm actually in the process of reverting to a -current of 2003.11.14.00.00.00 because my xl0 ethernet card is acting up as mentioned in another thread so I want to see if it works with that kernel. (Can't go further back due to statfs). Also one of my machines running 5.2-BETA just hung dead within 5 minutes of booting. I don't have DDB etc configured though so can't tell why. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's changed relating to localhost then?
I noticed the same thing yesterday when postgresql stopped working properly because there wasn't an entry for my public IP in the pg_hba.conf file. If you telnet to 127.0.0.1 the system still believes you are coming from your public IP. Bizarre that. Other IPs don't act that way. My system has two public IPs and 127.0.0.1. If I telnet to myself on either of the public IPs then I appear from the correct IP. However 127.0.0.1 no longer seems to work that way and that does break a number of things that expect to be connected to by 127.0.0.1 -Steve On Sat, Nov 22, 2003 at 02:46:54PM +, Matt Smith wrote: I've just updated to 5.2-BETA today and have noticed that my spamd is now rejecting all connections from spamc because they are not coming from 127.0.0.1 any more. It's now using my public IP address of 82.x.x.x: Nov 22 14:38:30 womble spamd[657]: unauthorized connection from 82-32-25-111.cable.ubr04.azte.blueyonder.co.uk [82.32.25.111] at port 49167 I noticed somebody reported a similar thing earlier. I'm actually in the process of reverting to a -current of 2003.11.14.00.00.00 because my xl0 ethernet card is acting up as mentioned in another thread so I want to see if it works with that kernel. (Can't go further back due to statfs). Also one of my machines running 5.2-BETA just hung dead within 5 minutes of booting. I don't have DDB etc configured though so can't tell why. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's changed relating to localhost then?
Matt Smith wrote: I've just updated to 5.2-BETA today and have noticed that my spamd is now rejecting all connections from spamc because they are not coming from 127.0.0.1 any more. It's now using my public IP address of 82.x.x.x: Yes, same problem here: at first, amavis refused to accept mails from postfix and when I started to try to fix it (without having enough black coffee inside) I got postfix to bounce all undelivered mail (~100-200 mails lost). :-/ I got amavis+postfix working again, but they still don't use the loopback interface. It would be nice if someone could help me to understand the reason for this. :) thanks, Uwe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's changed relating to localhost then?
Steve Ames [EMAIL PROTECTED] writes: If you telnet to 127.0.0.1 the system still believes you are coming from your public IP. Bizarre that. Other IPs don't act that way. My system has two public IPs and 127.0.0.1. If I telnet to myself on either of the public IPs then I appear from the correct IP. However 127.0.0.1 no longer seems to work that way and that does break a number of things that expect to be connected to by 127.0.0.1 I can confirm this behaviour. It is possible to force the local address to 127.0.0.1 though. [EMAIL PROTECTED] ~]$ telnet 127.0.0.1 25 [19:39] Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 borg.borderworlds.dk ESMTP Postfix Nov 22 19:39:44 borg postfix/smtpd[2683]: connect from borg.borderworlds.dk[10.1.0.2] [EMAIL PROTECTED] ~]$ telnet -s 127.0.0.1 127.0.0.1 25 [19:40] Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 borg.borderworlds.dk ESMTP Postfix Nov 22 19:40:06 borg postfix/smtpd[2683]: connect from localhost[127.0.0.1] Fortunately this behaviour didn't break anything here, but it does seem broken nonetheless. I updated my machine earlier today and got 5.2-BETA: FreeBSD borg.borderworlds.dk 5.2-BETA FreeBSD 5.2-BETA #3: Sat Nov 22 13:25:47 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BORG i386 -- Best regards Christian Laursen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: What's changed relating to localhost then?
From: Christian Laursen [mailto:[EMAIL PROTECTED] Steve Ames [EMAIL PROTECTED] writes: If you telnet to 127.0.0.1 the system still believes you are coming from your public IP. Bizarre that. Other IPs don't act that way. My system has two public IPs and 127.0.0.1. If I telnet to myself on either of the public IPs then I appear from the correct IP. However 127.0.0.1 no longer seems to work that way and that does break a number of things that expect to be connected to by 127.0.0.1 I can confirm this behaviour. It is possible to force the local address to 127.0.0.1 though. [EMAIL PROTECTED] ~]$ telnet 127.0.0.1 25 [19:39] Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 borg.borderworlds.dk ESMTP Postfix Nov 22 19:39:44 borg postfix/smtpd[2683]: connect from borg.borderworlds.dk[10.1.0.2] [EMAIL PROTECTED] ~]$ telnet -s 127.0.0.1 127.0.0.1 25 [19:40] Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 borg.borderworlds.dk ESMTP Postfix Nov 22 19:40:06 borg postfix/smtpd[2683]: connect from localhost[127.0.0.1] Fortunately this behaviour didn't break anything here, but it does seem broken nonetheless. This seems to break amd: amd[751]: Map support for: root, passwd, hesiod, union, nis, ndbm, file, error. amd[751]: AMFS: nfs, link, nfsx, nfsl, host, linkx, program, union, inherit, ufs, amd[751]: cdfs, pcfs, auto, direct, toplvl, error. amd[751]: FS: cd9660, nfs, nfs3, msdosfs, ufs, unionfs. amd[751]: Network 1: wire=10.128.2.0 (netnumber=10.128.2). amd[751]: Network 2: wire=192.168.3.0 (netnumber=192.168.3). amd[751]: My ip addr is 127.0.0.1 amd[752]: released controlling tty using setsid() amd[752]: file server localhost, type local, state starts up amd[753]: /phaedrus: disabling nfs congestion window amd[752]: ignoring request from 10.128.2.57:1018, expected 127.0.0.1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
