1 message in net.sourceforge.lists.courier-users[courier-users] specifying IPv6 sourc...
FromSent OnAttachments
Bernd WurstFeb 24, 2005 2:59 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] specifying IPv6 source addressActions...
From:Bernd Wurst (ber@bwurst.org)
Date:Feb 24, 2005 2:59:59 am
List:net.sourceforge.lists.courier-users

Hi

My courier-mta is set up now; me and my server are getting friends now. ;-)

So I have one more problem about the IPv6 connectivity. My server has an IPv6 tunnel to my upstream IPv6 broker. Additionally, I have several tunnels to my own clients and an address range for the use on the server.

So, now I have one of my IPv6-addresses (out of my address range) associated with the server's hostname. But if I connect to the outside IPv6-world, the kernel associates the endpoint address of my upstream tunnel for this connection. When I connect to one of my client-tunnel-endpoints, the kernel assiociates the local IPv6-address of that tunnel.

So the HELO-check at the other end always fails for IPv6-connects because the hostname does not resolve to the connecting IP-address.

Is there any solution? I know about the option "SOURCE_ADDRESS", but how could this be set for IPv6 only? Any hints?

cu, Bernd