Re: Re: Samba matchname: host name/address mismatch: ::ffff:127.0.0.1 != localhost
On Thu, Aug 19, 2010 at 11:58 AM, Roger Lynn <Roger@rilynn.me.uk> wrote:
>
> Just to let you know, your second suggestion worked, thank you. The mailing
> list seams to be eating my email. Feel free to forward this to the list if
> you think it would be helpful.
> Thanks,
> Roger
>
> -------- Original Message --------
> Subject: Re: Samba matchname: host name/address mismatch: ::ffff:127.0.0.1
> != localhost
> Date: Wed, 18 Aug 2010 09:49:58 +0100
> From: Roger Lynn <Roger@rilynn.me.uk>
> To: debian-user@lists.debian.org
> In-Reply-To: <[🔎] AANLkTikKcLLbmFHO83egsh4E5COxTxghDro4UmHwb7kT@mail.gmail.com>
> References: <[🔎] 4C6568B1.5020007@rilynn.me.uk>
> <[🔎] AANLkTikKcLLbmFHO83egsh4E5COxTxghDro4UmHwb7kT@mail.gmail.com>
>
> Resending, as the previous attempt hasn't shown up on the list archives
> despite being accepted by liszt.debian.org. I assume it's disappeared into a
> black hole somewhere.
>
> On Fri, 13 Aug 2010 13:47:14 -0400, Tom H <tomh0665@gmail.com> wrote:
>> On Fri, Aug 13, 2010 at 11:45 AM, Roger Lynn <Roger@rilynn.me.uk> wrote:
>> > Since upgrading from etch to lenny when it came out, all my Samba logs have
>> > been full of lines like:
>> >
>> > [2010/08/13 15:07:11, 0] lib/util_sock.c:matchname(1749)
>> > matchname: host name/address mismatch: ::ffff:127.0.0.1 != localhost
>> > [2010/08/13 15:07:11, 0] lib/util_sock.c:get_peer_name(1870)
>> > Matchname failed on localhost ::ffff:127.0.0.1
>> >
>> > As accessing files from Windows clients still works I've been able to work
>> > around it, so I've ignored it, but now I think it's preventing me from
>> > adding printers. There are lots of similar reports around, but I can't find
>> > any solutions. I am using only Debian Lenny packages with security updates
>> > and proposed updates. I am using dnsmasq for DNS. My smb.conf file is below.
>> > I have not knowingly done any customisation or configuration relating to IPv6.
>> >
>> > Is this a bug in my configuration, samba or somewhere else, possibly dnsmasq?
>> >
>> > Obviously this is IPv6 related. As I can't find any way of disabling IPv6 in
>> > Samba, the simplest solution appears to be to disable IPv6 on the entire
>> > machine. Has anyone got any better suggestions?
>>
>> A possible hack: add the hybrid (or whatever it is actually called)
>> "::ffff:127.0.0.1" ipv6 address to the "hosts allow" line.
>
> That didn't work, and wouldn't help for the other machines on the network
> that all have the same problem.
>
>> You might be able to disable ipv6 just for samba by adding
>> bind interfaces only = yes
>> interfaces = 127.0.0.1 host_ip_address
>> to smb.conf
>
> That did work, thank you. This seems to be just working around the problem
> rather than solving it properly, but I don't care.
> I've also discovered that Samba must be explicitly configured to use UTF8
> character set to talk to CUPS, which doesn't seem to be documented anywhere.
> Thanks again,
You're welcome. The first suggestion was a WAG so I'm not completely
surprised that it would fail. It turns out that the correct name for
the "::ffff:..." address is "ipv4-mapped ipv6 address" and that my WAG
failed because: "The IPv4-mapped address, 0:0:0:0:0:FFFF:w.x.y.z or
::FFFF:w.x.y.z, is used to represent an IPv4-only node to an IPv6
node. It is used only for internal representation. The IPv4-mapped
address is never used as a source or destination address for an IPv6
packet. The IPv6 protocol does not support the use of IPv4-mapped
addresses."
I agree that the second suggestion is a workaround but since samba
doesn't seem have a "noipv6" option like, for example, sshd, there
isn't really a choice... If you aren't using ipv6, you could disable
it through grub.
Reply to: