Hi every one!
Following problem needs to be solved.
I have 14 servers (VPS) that are used for iota nodes. They have been running fine for a long time. Now my server provider had to switch there set of IPs for the data center my servers are in, resulting in a new IP for each of my servers.
So I contacted my neighbors to please update my IPs to the new ones.
After they did that it showed that I still got data (new transactions) from them, but non of my neighbors received anything from me.
To find and fix the issue is rather important for me, as not only 14 servers are now running useless, but also this is something that should be fixed for the future. Imagine a IoT device that gets deployed by the end user, but it can't communicate because transactions get blocked.
Here is a trace rout I did to one of my neighbors:
4GB-Repeater-Server1:~# traceroute 62.176.XXX.XX
traceroute to 62.176.XXX.XX (62.176.XXX.XX), 30 hops max, 60 byte packets
1 18.104.22.168 (22.214.171.124) 0.084 ms 0.020 ms 0.017 ms
2 * * *
3 126.96.36.199 (188.8.131.52) 0.482 ms 0.458 ms 0.431 ms
4 ae32.cr3-dal3.ip4.gtt.net (184.108.40.206) 1.078 ms 1.050 ms 1.017 ms
5 be3257.ccr41.dfw03.atlas.cogentco.com (220.127.116.11) 1.376 ms 1.279 ms 2.869 ms
6 be2763.ccr21.dfw01.atlas.cogentco.com (18.104.22.168) 0.808 ms 0.818 ms 0.786 ms
7 be2432.ccr21.mci01.atlas.cogentco.com (22.214.171.124) 10.941 ms 10.959 ms 10.866 ms
8 be2831.ccr41.ord01.atlas.cogentco.com (126.96.36.199) 24.623 ms 24.683 ms 24.534 ms
9 be2717.ccr21.cle04.atlas.cogentco.com (188.8.131.52) 39.419 ms 38.922 ms 39.396 ms
10 be2993.ccr21.yyz02.atlas.cogentco.com (184.108.40.206) 39.512 ms 39.461 ms 38.986 ms
11 be2090.ccr21.ymq01.atlas.cogentco.com (220.127.116.11) 46.428 ms 46.885 ms 46.362 ms
12 be3042.ccr21.lpl01.atlas.cogentco.com (18.104.22.168) 125.376 ms 116.614 ms 116.574 ms
13 be2182.ccr41.ams03.atlas.cogentco.com (22.214.171.124) 122.218 ms 122.301 ms 121.729 ms
14 be2815.ccr41.ham01.atlas.cogentco.com (126.96.36.199) 132.486 ms 132.826 ms 132.433 ms
15 188.8.131.52 (184.108.40.206) 141.503 ms 140.932 ms 141.468 ms
16 dsl5.wobline.de (220.127.116.11) 143.627 ms 144.023 ms 144.197 ms
17 * * *
18 * * *
So if I understand it right udp Traffic doesn't get past the dsl5.wobline.de (18.104.22.168)
Thing is, I don't know to much about network routing and can't find much about it on google. And can't find anything about why Traffic would get stuck in the middle of the way.
30 Gi bounty
For the person who can find where and what the problem is (which includes explaining it in a human understandable way) and how to fix it, will get rewarded with 30 Gi. (30 Gi are about 300$ at current market rate)
Setting up a VPN server to re-raute the trafic dose not count as a solution, as I don't want to circumnavigate the problem but rather fix it.
The problem was that my Server provider did not disable the old IP yet and that some how interfered with the new one.
Disabling the old IP solved the issue.
So first find the venet of old IP with "ifconfig" (in my case venet0:0)
And then disable it with "ifdown venet0:0"