On Sat, Nov 19, 2016 at 07:59:15AM +0100, postfix wrote:
> I changed this network to "real" IPV6 (before I used 6TO4
> tunnelling). Now, every host and every program (including postfix)
> rushes to use IPV6. But there are problems with postfix: on one
> Host (postfix-2.10.1-6.el7.x86_64) I had i
An fe80:: IP address is not formally attached to any particular
interface. It "just happens" as part of the autoconfigure regime.
To use one in a listen or bind type statement, you would have to
expressly state which interface you wish to use.
For example, you need to use the argument "-I eth0" (
postfix:
> Nov 19 06:13:02 tico postfix/master[23428]: fatal: bind
> fe80::4216:7eff:fea7:c56b port 587: Invalid argument
I have never seen this problem.
As a fix, don't specify link-local interfaces in main.cf:inet_interfaces.
Wietse
postfix wrote on 19/11/2016 07:59:
I know that this error comes from the fact, that the IPV6 stack misses the
interface name when binding. The postfix information page "Postfix IPv6 Support"
is really not helpful in that situation, specifying "that IPV6 is hardly used
smtp_bind_address6 coul
> > mynetworks = 192.168.97.0/28, 127.0.0.0/8, [::1]/128, [fe80::]/64,
> > [fec0::]/64
>
> Just delete [fe80::]/64 and [fec0::]/64.
> No client will use link local and site local address of your server
> therefore listening on these is absolute unnecessary.
^
Eeeer... _filter
> mynetworks = 192.168.97.0/28, 127.0.0.0/8, [::1]/128, [fe80::]/64, [fec0::]/64
Just delete [fe80::]/64 and [fec0::]/64.
No client will use link local and site local address of your server
therefore listening on these is absolute unnecessary.
Gabor
Hi postfixers
I changed this network to "real" IPV6 (before I used 6TO4 tunnelling).
Now, every host and every program (including postfix) rushes to use
IPV6. But there are problems with postfix: on one Host
(postfix-2.10.1-6.el7.x86_64) I had in the logs:
Nov 19 06:13:01 tico postfix/postfix