Mailing List Archive: v6 disconnect

v6 disconnect

Jul 23, 2002, 3:52 PM

Post #1 of 3 (388 views)

why did i get the disconnect from the v6 connection?

randy

---

delivering message 17X8Rf-000Fpb-00
Connecting to rip.psg.com [2001:418:1::39.25] ... connected
LOG: 0 MAIN
Remote host rip.psg.com [2001:418:1::39] closed connection after initial connection
Connecting to rip.psg.com [147.28.0.39.25] ... connected
SMTP<< 220 rip.psg.com ESMTP Exim 4.10 Tue, 23 Jul 2002 15:51:51 -0700
SMTP>> EHLO psg.com
SMTP<< 250-rip.psg.com Hello smmsp at psg.com [147.28.0.62]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250 HELP
SMTP>> MAIL FROM:<owner-ipng@sunroof.eng.sun.com> SIZE=10531
SMTP>> RCPT TO:<randy@rip.psg.com>
SMTP>> DATA
SMTP<< 250 OK
SMTP<< 250 Accepted
SMTP<< 354 Enter message, ending with "." on a line by itself
SMTP>> writing message and terminating "."
SMTP<< 250 OK id=17X8VT-0008kp-00
SMTP>> QUIT
LOG: 0 MAIN
=> randy@rip.psg.com <randy@psg.com> R=hubbed_hosts T=remote_smtp H=rip.psg.com [147.28.0.39]
LOG: 0 MAIN
Completed

Re: v6 disconnect [ In reply to ]

ph10 at cus

Jul 24, 2002, 2:14 AM

Post #2 of 3 (388 views)

Permalink

On Tue, 23 Jul 2002, Randy Bush wrote:

> why did i get the disconnect from the v6 connection?

What does the Exim log say?

> Connecting to rip.psg.com [2001:418:1::39.25] ... connected
> LOG: 0 MAIN
> Remote host rip.psg.com [2001:418:1::39] closed connection after initial connection

If the log says nothing, turn on logging of all SMTP (dis)connection
activity (log_selector = +smtp_connection in Exim 4) and try again.

If you still get nothing, it looks like the connection isn't even making
it as far as Exim. Are you running TCPwrappers or anything? Using inetd?

Philip

--
Philip Hazel University of Cambridge Computing Service,
ph10@cus.cam.ac.uk Cambridge, England. Phone: +44 1223 334714.

Re: v6 disconnect [ In reply to ]

randy at psg

Jul 24, 2002, 6:43 AM

Post #3 of 3 (378 views)

Permalink

>> why did i get the disconnect from the v6 connection?
> What does the Exim log say?

it turned out to be that freebsd 4.6-stable's /etc/hosts.allow
does not deal well with ipv6 addresses.

randy