* Per Jessen <per@computer.org> [09-07-19 03:31]:
Patrick Shanahan wrote:
On the system where you run fetchmail, could you show us output from:
ip addr ip route show ip -6 route show
ip addr: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:e3:b5:ad:f1:2f brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2600:1702:1031:3f91:9c18:980c:30e6:1d80/64 scope global temporary dynamic valid_lft 544938sec preferred_lft 25938sec
Perfect! You have IPv6 on your local network.
ip -6 route show: 2600:1702:1031:3f90::/64 dev eth0 proto kernel metric 256 expires 3287sec pref medium 2600:1702:1031:3f91::/64 dev eth0 proto kernel metric 256 expires 2360523sec pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::de7f:a4ff:fe21:cd8d dev eth0 proto ra metric 1024 expires 1487sec hoplimit 64 pref medium
The latter, default ipv6 route, is your uplink router, so in principle it ought to work. From here, accessing imap.gmail.com over ipv6 does work, but clearly yours does not.
What does 'ping6 imap.gmail.com' say? I'm hoping it will say destination unreachable. I suspect a routing issue.
I think you have two options -
a) force your system(s) to only use ipv4 b) try to solve the uplink ipv6 issue
fortunately or unfortunately depending on ones position, restarting network on the server appears to have solved the problem. "a" worked for a short time before I restarted the network and now ping6s times are respectable. wahoo:~ > ping6 imap.gmail.com PING imap.gmail.com(qn-in-x6d.1e100.net) 56 data bytes 64 bytes from qn-in-x6d.1e100.net: icmp_seq=1 ttl=44 time=50.5 ms 64 bytes from qn-in-x6d.1e100.net: icmp_seq=2 ttl=44 time=50.5 ms I cannot say with *any* certainty what was actually wrong, only that resetting the network appears to have solved the mail problem. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org