Here is the output:
I noticed it seems to be picking up some ip / address info from an IPv6
tunnel to Hurricane Electric.
I never configured this host with any such IPv6 information however.
The tunnel is using 2001:470:b148::/48 .
Here is an attempt to traceroute to google:
[root at onion ~]# traceroute6 google.com
traceroute to google.com (2001:4860:4008:802::1001), 30 hops max, 80 byte
packets
1 fe80::205:32ff:fee8:8b61%eth0 (fe80::205:32ff:fee8:8b61%eth0) 1.729 ms
5.032 ms 5.331 ms
2 * * *
3 * * *
[root at onion ~]# ip -6 add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::215:5dff:fe02:830a/64 scope link
valid_lft forever preferred_lft forever
[root at onion ~]# ip -6 route
unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376
hoplimit 4294967295
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436
advmss 16376 hoplimit 4294967295
2001:470:b148::/48 dev eth0 proto kernel metric 256 expires 0sec mtu
1500 advmss 1440 hoplimit 4294967295
unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss
16376 hoplimit 4294967295
unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss
16376 hoplimit 4294967295
unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss
16376 hoplimit 4294967295
unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss
16376 hoplimit 4294967295
unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss
16376 hoplimit 4294967295
unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss
16376 hoplimit 4294967295
unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss
16376 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit
4294967295
default via fe80::205:32ff:fee8:8b61 dev eth0 proto kernel metric 1024
expires 0sec mtu 1500 advmss 1440 hoplimit 64
On Thu, Jun 21, 2012 at 3:16 AM, Gert Doering <gert at space.net> wrote:
> Hi,
>
> On Thu, Jun 21, 2012 at 02:28:31AM -0400, Mansoor Nathani wrote:
> > Since Gmail has enabled AAAA records for some of its MX hosts, my IPv4
> only
> > machine gets the Gmail IPv6 address and attempts to deliver email. Its
> only
> > when the timeout has been reached will it try the IPv4 address.
> >
> > I am curious if anyone else is experiencing this or perhaps I need to do
> > something on the CentOS 6 box to disable IPv6 till the time when it has
> > native IPv6 capability.
> >
> > Jun 21 02:14:47 onion postfix/cleanup[1494]: 435AD1A110A:
> > message-id=<20120621061447.435AD1A110A at host.domain>
> > Jun 21 02:14:47 onion postfix/qmgr[1348]: 435AD1A110A:
> > from=<user at host.domain>, size=448, nrcpt=1 (queue active)
> > Jun 21 02:15:09 onion postfix/smtp[1497]: connect to
> > gmail-smtp-in-v4v6.l.google.com[2001:4860:b007::1b]:25: Connection
> timed out
>
> The more interesting question, actually, is why it actually has to wait
> for IPv6 to time-out if your machine is IPv4-only - it should immediately
> fail for IPv6, and then try IPv4.
>
> What does "ip -6 route" show on your machine?
>
> I'd guess that your machine thinks it *does* have IPv6, because a friendly
> Windows box in the neighbourhood announced a 2002 prefix...
>
> *Broken* IPv6 is what causes these problems, "no IPv6" is handled just fine
> (but then, for outgoing mail sent by a MTA, 30 seconds delay do not
> *really*
> cause harm)
>
> Gert Doering
> -- NetMaster
> --
> have you enabled IPv6 on something today...?
>
> SpaceNet AG Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen HRB: 136055 (AG Muenchen)
> Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20120621/d81b6c90/attachment.htm>