| 1 |
On Sat, 25 Mar 2017 12:36:04 +0100 Alarig Le Lay wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> On one of my machines, I have two public IPv6 from two different |
| 5 |
> providers (one natively, another by VPN). I use ip -6 rule to make both |
| 6 |
> pingable. |
| 7 |
> |
| 8 |
> I see some strange things on the native one. It stops responding from |
| 9 |
> time to time. Here are some examples of mtr: |
| 10 |
> https://paste.swordarmor.fr/raw/mXVT |
| 11 |
> |
| 12 |
> At this time, the other IPv6 (bulbizarre.swordarmor.fr) works normally. |
| 13 |
> |
| 14 |
> And if I do the same test on another machine in the same LAN, no loss: |
| 15 |
> https://paste.swordarmor.fr/raw/XGbK |
| 16 |
> |
| 17 |
> I have this routing table: |
| 18 |
> alarig@bulbizarre ~ $ ip -6 rule list |
| 19 |
> 0: from all lookup local |
| 20 |
> 31010: from 2a01:cb08:898c:fc00:9913:b7a:b9bf:d30c lookup 3215 |
| 21 |
> 31100: from all lookup 51083 |
| 22 |
> 32766: from all lookup main |
| 23 |
> alarig@bulbizarre ~ $ ip -6 route show |
| 24 |
> 2a00:5881:4008:400::/64 dev tun0 proto kernel metric 256 pref medium |
| 25 |
> 2a01:cb08:898c:fc00::/64 dev eth0 proto kernel metric 4 pref medium |
| 26 |
> fe80::/64 dev eth0 proto kernel metric 256 pref medium |
| 27 |
> fe80::/64 dev tun0 proto kernel metric 256 pref medium |
| 28 |
> fe80::/64 dev tun-mysql proto kernel metric 256 pref medium |
| 29 |
> default via fe80::20d:b9ff:fe3a:1fa1 dev eth0 metric 4 pref medium |
| 30 |
> alarig@bulbizarre ~ $ ip -6 route show table 3215 |
| 31 |
> 2a01:cb08:898c:fc00::/64 dev eth0 metric 1024 pref medium |
| 32 |
> default via fe80::20d:b9ff:fe3a:1fa1 dev eth0 metric 1024 pref medium |
| 33 |
> alarig@bulbizarre ~ $ ip -6 route show table 51083 |
| 34 |
> default dev tun0 metric 1024 pref medium |
| 35 |
> |
| 36 |
> I’m using the kernel 4.9.16-gentoo. |
| 37 |
> |
| 38 |
> I’m running out of ideas, so I ask for your help :) |
| 39 |
|
| 40 |
Run tcpdump -w on both sides. Compare dumps when connection stalls |
| 41 |
and when it works fine. Many reasons are possible, it's hard to |
| 42 |
guess from data you provided. |
| 43 |
|
| 44 |
But it makes me wonder why you have default via VPN and given |
| 45 |
address via eth0. This may lead to undesirable consequences like |
| 46 |
VPN carrier (or some aux request) trying to go through its own VPN |
| 47 |
tunnel. |
| 48 |
|
| 49 |
Best regards, |
| 50 |
Andrew Savchenko |
Archives