Guus Snijders via arch-general writes:
> Op 2 feb. 2017 20:58 schreef "Thorsten Jolitz via arch-general" <
> In the first case, perhaps a tunnel provider can help as your current setup
> appears flaky at best. In the second case, it's probably better to find out
> how to disable IPv6 on your mac
Op 2 feb. 2017 20:58 schreef "Thorsten Jolitz via arch-general" <
arch-general@archlinux.org>:
Robin via arch-general writes:
>> - IPv6 is tried , but takes forever and has 100% package loss
>> (frecuent).
>> - pinging IPv6 addresses works (very rare)
[...]
that explains it very well. ping
Robin via arch-general writes:
>> - IPv6 is tried , but takes forever and has 100% package loss
>> (frecuent).
>> - pinging IPv6 addresses works (very rare)
> That's strange. A traceroute with booth working v6 and not working v6
> would be helpful. Also a output of your routing table would be
> - IPv6 is tried , but takes forever and has 100% package loss
> (frecuent).
> - pinging IPv6 addresses works (very rare)
That's strange. A traceroute with booth working v6 and not working v6 would be
helpful. Also a output of your routing table would be nice.
> - pinging pure IPv6 addresse
Damjan Georgievski via arch-general writes:
>> And the most surprising thing is, that it worked for one single moment,
>> see the PS, and stopped working after the next reboot - with all what I
>> tried to make it work still untouched and in place.
>>
>> Any further tipps here?
>
> do you even ha
> And the most surprising thing is, that it worked for one single moment,
> see the PS, and stopped working after the next reboot - with all what I
> tried to make it work still untouched and in place.
>
> Any further tipps here?
do you even have an IPv6 service from your ISP?
try pinging [2a00:14
Thorsten Jolitz via arch-general writes:
Hello,
following up to my own post again.
> Thorsten Jolitz via arch-general writes:
>
> Hello,
> following up to my own post:
>
>> Marcel Hoppe via arch-general writes:
>>
>> Hi Marcel, Hi Robin,
>>
>> thanks for your answers.
>>
>>> I resolved the sam
Thorsten Jolitz via arch-general writes:
Hello,
following up to my own post:
> Marcel Hoppe via arch-general writes:
>
> Hi Marcel, Hi Robin,
>
> thanks for your answers.
>
>> I resolved the same problem 😉 on my systems I run the networkmanager and
>> this works long time - I'm not sure but I t
Thorsten Jolitz via arch-general writes:
Hello,
following up to my own post:
> Marcel Hoppe via arch-general writes:
>
> Hi Marcel, Hi Robin,
>
> thanks for your answers.
>
>> I resolved the same problem 😉 on my systems I run the networkmanager and
>> this works long time - I'm not sure but I t
Marcel Hoppe via arch-general writes:
Hi Marcel, Hi Robin,
thanks for your answers.
> I resolved the same problem 😉 on my systems I run the networkmanager and
> this works long time - I'm not sure but I think the problem was that
> systemd gets or starts its own revolver service. After disablin
Hi,
I resolved the same problem 😉 on my systems I run the networkmanager and
this works long time - I'm not sure but I think the problem was that
systemd gets or starts its own revolver service. After disabling it and
deleting the linked resolve.conf the networkmanager creates it after a
restart a
Hi,
seems like a ipv6 related problem. Your DNS Lookup is v4, first ping is
v6 and second ping is v4 again. Try to ping the ipv4 address of
google.com. But im pretty sure this is not arch related.
Maybe you should try to disable ipv6 system wide and then check if it
works.
Cheers,
Robin
> Hello
Hello List,
sometime age my msmtp imap connections just stopped working.
Investigating the cause, I checked quite a lot of things, and came
across the ping "100% package loss" problem:
With
/etc/resolv.conf
,
| # Generated by resolvconf
| domain Speedport_W_xx
|
| nameserver 192.168.2.1
13 matches
Mail list logo
