ECHOLINK - UDP Paketblockierungen - physikalische Netzwerkkartenadressen
8 views
Skip to first unread message
dk3qv
Jan 28, 2008, 2:57:47 AM1/28/08
to Amateurfunk-Deutschland
Zwischenzeitlich sind mit Hilfe chinesischer IT Unterstützung eine
Reihe von Tests durchgeführt worden, um den Effekt der geblockten UDP
Pakete für den ECHOLINK P2P Betrieb, insbesondere hier aus dem
südostasiatischen Raum, zu untersuchen.
Die Erklärung und Lösung stellt sich danach in recht einfacher Weise,
auch bei der Benutzung von insgesamt 8 verschiedenen Laptops und PCs,
wie folgt da.
Wenn die physikalische Netzkartenadresse den Wert 0C-0C-0C-0C-0C-01
aufweist, erfolgt KEINE UDP Pakete Übertragung zum Empfänger Server.
Weil offensichtlich die Sender Identifikation mit diesem so genannten
default Wert NICHT ausreichend ist.
Alle anderen einstellbaren Netzkartenadressen mit Werten von
0X-0X-0X-0X-0X-0X erlauben in den verschieden benutzten ISP Netzen
einen einwandfreien ECHOLINK Betrieb, unter den unten angegebenen
Portkonditionen.
Hat jemand vergleichbare Erfahrungen der physikalischen
Netzkartenadressen mit Einfluss auf den ECHOLINK Betrieb gemacht ?
----------------------------------------------------------------------------------------------------
Lösungen - UDP Pakete Blockierung beim ISP - nach Routing
Information ?
Seit dem 30.12.2007 lässt sich nach mehr als 6 Monaten kein ECHOLINK
Betrieb mehr erreichen. Der UDP Test verläuft immer negativ.
Gibt es konkrete Möglichkeiten mit Tracing Routings eindeutig
festzustellen, wo die UDP Pakete beim ISP geblockt werden ?
Hat hierzu bereits jemand Erfahrungen gesammelt ?
----------------------------------------------------------------------------------------------------
11.01.2008 19:41:27 - Tracing Route to 68.178.144.151 - DOES NOT WORKS
Hop # 1 63 ms 192.168.1.254
Hop # 2 67 ms 125.26.245.1 125-26-245-1.adsl.totbb.net
Hop # 3 90 ms 203.113.92.229
Hop # 4 86 ms 203.113.54.218
Hop # 5 78 ms 203.113.54.222
Hop # 6 84 ms 203.113.54.226
Hop # 7 85 ms 203.113.54.150
Hop # 8 81 ms 203.113.54.154
Hop # 9 85 ms 203.113.54.158
Hop # 10 84 ms 203.113.24.137
Hop # 11 84 ms 203.113.24.138
Hop # 12 78 ms 203.113.13.126
Hop # 13 84 ms 203.113.24.245 - 203.113.24.0-203.113.24.255 TOT Public
Company Limited Bangkok
Hop # 14 308 ms 61.19.10.13 - 61.19.0.0-61.19.15.255 CAT-IIGservice
Hop # 15 307 ms 202.47.253.130 - 202.47.252.0-202.47.254.255 CAT
TELECOM Data Comm.
Hop # 16 448 ms 166.63.211.141 so-2-1-0-dcr1.tsd.cw.net -
166.63.192.0-166.63.223.255 Cable & Wireless Americas Operations, Inc.
NY
Hop # 17 379 ms 195.66.224.76 ge3-0.pr1.lhr1.uk.above.net -
195.66.224.0-195.66.225.255 LINX-PEER-1London
Hop # 18 392 ms 64.125.27.57 so-0-1-0.mpr1.dca2.us.above.net -
64.124.0.0-64.125.255.255 Abovenet Communications, Inc USA
Hop # 19 402 ms 64.125.29.37 so-5-1-0.mpr2.atl6.us.above.net
Hop # 20 400 ms 64.125.26.13 so-0-0-0.mpr3.iah1.us.above.net
Hop # 21 369 ms 64.125.25.10 so-1-2-0.mpr2.phx2.us.above.net
Hop # 22 366 ms 64.124.113.62 64.124.113.62.godaddy.com
Hop # 23 378 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 24 372 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 25 366 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 26 374 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
11.01.2008 20:01:21 Tracing Route to 68.178.144.151 - DOES NOT WORKS
Hop # 1 167 ms 192.168.1.254
Hop # 2 62 ms 125.26.245.1 125-26-245-1.adsl.totbb.net
Hop # 3 86 ms 203.113.92.229
Hop # 4 88 ms 203.113.54.218
Hop # 5 80 ms 203.113.54.222
Hop # 6 82 ms 203.113.54.226
Hop # 7 85 ms 203.113.54.150
Hop # 8 78 ms 203.113.54.154
Hop # 9 85 ms 203.113.54.158
Hop # 10 87 ms 203.113.24.137
Hop # 11 87 ms 203.113.24.138
Hop # 12 78 ms 203.113.13.126
Hop # 13 83 ms 203.113.24.245
Hop # 14 329 ms 61.19.10.13
Hop # 15 327 ms 202.47.253.130
Hop # 16 414 ms 166.63.211.141 so-2-1-0-dcr1.tsd.cw.net
Hop # 17 379 ms 195.66.224.76 ge3-0.pr1.lhr1.uk.above.net
Hop # 18 397 ms 64.125.27.57 so-0-1-0.mpr1.dca2.us.above.net
Hop # 19 402 ms 64.125.29.37 so-5-1-0.mpr2.atl6.us.above.net
Hop # 20 414 ms 64.125.26.13 so-0-0-0.mpr3.iah1.us.above.net
Hop # 21 381 ms 64.125.25.10 so-1-2-0.mpr2.phx2.us.above.net
Hop # 22 366 ms 64.124.113.62 64.124.113.62.godaddy.com
Hop # 23 380 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 24 374 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 25 382 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 26 383 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
12.01.2008 14:20:12 Tracing Route to 68.178.144.151 - DOES NOT WORKS
Hop # 1 191 ms 192.168.1.254
Hop # 2 64 ms 125.26.245.1 125-26-245-1.adsl.totbb.net
Hop # 3 117 ms 203.113.92.225
Hop # 4 115 ms 203.113.54.209
Hop # 5 116 ms 203.113.54.205
Hop # 6 121 ms 203.113.54.201
Hop # 7 119 ms 203.113.54.141
Hop # 8 127 ms 203.113.54.137
Hop # 9 118 ms 203.113.54.133
Hop # 10 120 ms 203.113.24.137
Hop # 11 127 ms 203.113.24.138
Hop # 12 119 ms 203.113.13.126
Hop # 13 128 ms 203.113.24.241
Hop # 14 585 ms 61.19.10.13
Hop # 15 551 ms 202.47.253.146
Hop # 16 665 ms 166.63.211.141 so-2-1-0-dcr1.tsd.cw.net
Hop # 17 655 ms 195.66.224.76 ge3-0.pr1.lhr1.uk.above.net
Hop # 18 645 ms 64.125.27.57 so-0-1-0.mpr1.dca2.us.above.net
Hop # 19 688 ms 64.125.28.230 so-1-0-0.mpr2.atl6.us.above.net
Hop # 20 652 ms 64.125.27.49 so-0-0-0.mpr1.atl6.us.above.net
Hop # 21 673 ms 64.125.29.62 so-0-1-0.mpr4.iah1.us.above.net
Hop # 22 668 ms 64.125.26.13 so-0-0-0.mpr3.iah1.us.above.net
Hop # 23 628 ms 64.125.25.5
Hop # 24 650 ms 64.124.147.30 available.above.net
Hop # 25 828 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 26 823 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 27 633 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 28 894 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
08.07.2007 20:34:25 - IT WORKS
Tracing Route to 68.178.144.151:
Hop # 1 171 ms 192.168.1.254 dsldevice.lan
Hop # 2 49 ms 125.26.246.49 125-26-246-49.adsl.totbb.net
Hop # 3 68 ms 203.113.72.125
Hop # 4 67 ms 203.113.72.253
Hop # 5 70 ms 203.113.95.225
Hop # 6 69 ms 203.113.54.209
Hop # 7 69 ms 203.113.54.205
Hop # 8 69 ms 203.113.54.201
Hop # 9 67 ms 203.113.54.146
Hop # 10 67 ms 203.113.54.150
Hop # 11 70 ms 203.113.54.154
Hop # 12 68 ms 203.113.54.158
Hop # 13 69 ms 203.113.24.137
Hop # 14 68 ms 203.113.24.138
Hop # 15 70 ms 203.113.13.126 vl101.cs1-cwt.totisp.net
Hop # 16 421 ms 203.113.24.237
Hop # 17 418 ms 61.19.10.13
Hop # 18 67 ms 202.47.253.146
Hop # 19 288 ms 195.22.197.193 pal9-cat-telecom-3-id.pal.seabone.net
Hop # 20 325 ms 213.144.183.15 par31-par2-racc1.par.seabone.net
Hop # 21 735 ms 213.144.183.34 globalcrossing-2-us-
par31.par.seabone.net
Hop # 22 736 ms 67.17.198.42
Hop # 23 737 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 24 728 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 25 377 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 26 754 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
10.07.2007 18:15:48 - DOES NOT WORKS
Tracing Route to 68.178.144.151:
Hop # 1 64 ms 192.168.1.254
Hop # 2 51 ms 125.26.246.49 125-26-246-49.adsl.totbb.net
Hop # 3 83 ms 203.113.72.125
Hop # 4 85 ms 203.113.72.253
Hop # 5 85 ms 203.113.95.226
Hop # 6 83 ms 203.113.54.218
Hop # 7 81 ms 203.113.54.222
Hop # 8 84 ms 203.113.54.226
Hop # 9 85 ms 203.113.54.150
Hop # 10 84 ms 203.113.54.154
Hop # 11 82 ms 203.113.54.158
Hop # 12 84 ms 203.113.24.137
Hop # 13 82 ms 203.113.24.138
Hop # 14 83 ms 203.113.13.126 vl101.cs1-cwt.totisp.net
Hop # 15 711 ms 203.113.24.237
Hop # 16 85 ms 61.19.10.13
Hop # 17 81 ms 202.47.253.130
Hop # 18 586 ms 195.22.197.193 pal9-cat-telecom-3-id.pal.seabone.net
Hop # 19 638 ms 213.144.183.15 par31-par2-racc1.par.seabone.net
Hop # 20 665 ms 213.144.183.34 globalcrossing-2-us-
par31.par.seabone.net
Hop # 21 386 ms 67.17.198.42
Hop # 22 945 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 23 974 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 24 701 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 25 388 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
----------------------------------------------------------------------------------------------------
IP: 125.26.245.141
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
----------------------------------------------------------------------------------------------------
EchoLink Troubleshooter ver 1.2.0.5
Diagnostic Report for
Prepared Friday, January 04, 2008 12:14:54 SE Asia Standard Time
*** System Information ***
Windows XP Service Pack 2
*** Network Options ***
Shared Internet Connection: No
Wireless: No
*** Network Configuration ***
Local IP Address: 125.26.245.93
This is a public address that is directly reachable from the Internet.
This usually indicates that your system does not use a router to
access the Internet.
Connection type: Other
Shared Internet connection: No
Wireless network connection: No
*** TCP Connectivity Test ***
The TCP test FAILED: Cannot connect to server (10061).
This means that EchoLink might not be able to log in to the EchoLink
addressing servers.
The UDP port 5198 test FAILED: Receive failed (10060).
This means that EchoLink cannot communicate with other stations over
the Internet. Be sure your router, firewall, or security software is
allowing EchoLink to receive messages over UDP ports 5198 and 5199,
and that your Internet service provider (ISP) has not blocked this
port.
A few Internet service providers (ISPs) block a range of different UDP
ports, including ports 5198 and 5199 used by EchoLink. Although this
is relatively rare, check with your ISP if the rest of your
configuration appears to be OK.
-----------------------------------------------------------------------------------------
IP: 192.168.1.65
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
IP: 125.26.245.200
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
IP: 192.168.1.64
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
IP: 125.26.245.206
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
--------------------------------------------------------------------------------------------------------------------
[PacketRule]
Name=Echolink
Enable=1
Allow=1
Log=0
Warning=0
Protocol=TCP
Direction=InboundOutbound
LocalPort=5200
[PacketRule]
Name=Echolink
Enable=1
Allow=1
Log=0
Warning=0
Protocol=UDP
Direction=InboundOutbound
LocalPort=5199
[PacketRule]
Name=Echolink
Enable=1
Allow=1
Log=0
Warning=0
Protocol=UDP
Direction=InboundOutbound
LocalPort=5198
------------------------------------------------------------------------------
Reihe von Tests durchgeführt worden, um den Effekt der geblockten UDP
Pakete für den ECHOLINK P2P Betrieb, insbesondere hier aus dem
südostasiatischen Raum, zu untersuchen.
Die Erklärung und Lösung stellt sich danach in recht einfacher Weise,
auch bei der Benutzung von insgesamt 8 verschiedenen Laptops und PCs,
wie folgt da.
Wenn die physikalische Netzkartenadresse den Wert 0C-0C-0C-0C-0C-01
aufweist, erfolgt KEINE UDP Pakete Übertragung zum Empfänger Server.
Weil offensichtlich die Sender Identifikation mit diesem so genannten
default Wert NICHT ausreichend ist.
Alle anderen einstellbaren Netzkartenadressen mit Werten von
0X-0X-0X-0X-0X-0X erlauben in den verschieden benutzten ISP Netzen
einen einwandfreien ECHOLINK Betrieb, unter den unten angegebenen
Portkonditionen.
Hat jemand vergleichbare Erfahrungen der physikalischen
Netzkartenadressen mit Einfluss auf den ECHOLINK Betrieb gemacht ?
----------------------------------------------------------------------------------------------------
Lösungen - UDP Pakete Blockierung beim ISP - nach Routing
Information ?
Seit dem 30.12.2007 lässt sich nach mehr als 6 Monaten kein ECHOLINK
Betrieb mehr erreichen. Der UDP Test verläuft immer negativ.
Gibt es konkrete Möglichkeiten mit Tracing Routings eindeutig
festzustellen, wo die UDP Pakete beim ISP geblockt werden ?
Hat hierzu bereits jemand Erfahrungen gesammelt ?
----------------------------------------------------------------------------------------------------
11.01.2008 19:41:27 - Tracing Route to 68.178.144.151 - DOES NOT WORKS
Hop # 1 63 ms 192.168.1.254
Hop # 2 67 ms 125.26.245.1 125-26-245-1.adsl.totbb.net
Hop # 3 90 ms 203.113.92.229
Hop # 4 86 ms 203.113.54.218
Hop # 5 78 ms 203.113.54.222
Hop # 6 84 ms 203.113.54.226
Hop # 7 85 ms 203.113.54.150
Hop # 8 81 ms 203.113.54.154
Hop # 9 85 ms 203.113.54.158
Hop # 10 84 ms 203.113.24.137
Hop # 11 84 ms 203.113.24.138
Hop # 12 78 ms 203.113.13.126
Hop # 13 84 ms 203.113.24.245 - 203.113.24.0-203.113.24.255 TOT Public
Company Limited Bangkok
Hop # 14 308 ms 61.19.10.13 - 61.19.0.0-61.19.15.255 CAT-IIGservice
Hop # 15 307 ms 202.47.253.130 - 202.47.252.0-202.47.254.255 CAT
TELECOM Data Comm.
Hop # 16 448 ms 166.63.211.141 so-2-1-0-dcr1.tsd.cw.net -
166.63.192.0-166.63.223.255 Cable & Wireless Americas Operations, Inc.
NY
Hop # 17 379 ms 195.66.224.76 ge3-0.pr1.lhr1.uk.above.net -
195.66.224.0-195.66.225.255 LINX-PEER-1London
Hop # 18 392 ms 64.125.27.57 so-0-1-0.mpr1.dca2.us.above.net -
64.124.0.0-64.125.255.255 Abovenet Communications, Inc USA
Hop # 19 402 ms 64.125.29.37 so-5-1-0.mpr2.atl6.us.above.net
Hop # 20 400 ms 64.125.26.13 so-0-0-0.mpr3.iah1.us.above.net
Hop # 21 369 ms 64.125.25.10 so-1-2-0.mpr2.phx2.us.above.net
Hop # 22 366 ms 64.124.113.62 64.124.113.62.godaddy.com
Hop # 23 378 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 24 372 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 25 366 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 26 374 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
11.01.2008 20:01:21 Tracing Route to 68.178.144.151 - DOES NOT WORKS
Hop # 1 167 ms 192.168.1.254
Hop # 2 62 ms 125.26.245.1 125-26-245-1.adsl.totbb.net
Hop # 3 86 ms 203.113.92.229
Hop # 4 88 ms 203.113.54.218
Hop # 5 80 ms 203.113.54.222
Hop # 6 82 ms 203.113.54.226
Hop # 7 85 ms 203.113.54.150
Hop # 8 78 ms 203.113.54.154
Hop # 9 85 ms 203.113.54.158
Hop # 10 87 ms 203.113.24.137
Hop # 11 87 ms 203.113.24.138
Hop # 12 78 ms 203.113.13.126
Hop # 13 83 ms 203.113.24.245
Hop # 14 329 ms 61.19.10.13
Hop # 15 327 ms 202.47.253.130
Hop # 16 414 ms 166.63.211.141 so-2-1-0-dcr1.tsd.cw.net
Hop # 17 379 ms 195.66.224.76 ge3-0.pr1.lhr1.uk.above.net
Hop # 18 397 ms 64.125.27.57 so-0-1-0.mpr1.dca2.us.above.net
Hop # 19 402 ms 64.125.29.37 so-5-1-0.mpr2.atl6.us.above.net
Hop # 20 414 ms 64.125.26.13 so-0-0-0.mpr3.iah1.us.above.net
Hop # 21 381 ms 64.125.25.10 so-1-2-0.mpr2.phx2.us.above.net
Hop # 22 366 ms 64.124.113.62 64.124.113.62.godaddy.com
Hop # 23 380 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 24 374 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 25 382 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 26 383 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
12.01.2008 14:20:12 Tracing Route to 68.178.144.151 - DOES NOT WORKS
Hop # 1 191 ms 192.168.1.254
Hop # 2 64 ms 125.26.245.1 125-26-245-1.adsl.totbb.net
Hop # 3 117 ms 203.113.92.225
Hop # 4 115 ms 203.113.54.209
Hop # 5 116 ms 203.113.54.205
Hop # 6 121 ms 203.113.54.201
Hop # 7 119 ms 203.113.54.141
Hop # 8 127 ms 203.113.54.137
Hop # 9 118 ms 203.113.54.133
Hop # 10 120 ms 203.113.24.137
Hop # 11 127 ms 203.113.24.138
Hop # 12 119 ms 203.113.13.126
Hop # 13 128 ms 203.113.24.241
Hop # 14 585 ms 61.19.10.13
Hop # 15 551 ms 202.47.253.146
Hop # 16 665 ms 166.63.211.141 so-2-1-0-dcr1.tsd.cw.net
Hop # 17 655 ms 195.66.224.76 ge3-0.pr1.lhr1.uk.above.net
Hop # 18 645 ms 64.125.27.57 so-0-1-0.mpr1.dca2.us.above.net
Hop # 19 688 ms 64.125.28.230 so-1-0-0.mpr2.atl6.us.above.net
Hop # 20 652 ms 64.125.27.49 so-0-0-0.mpr1.atl6.us.above.net
Hop # 21 673 ms 64.125.29.62 so-0-1-0.mpr4.iah1.us.above.net
Hop # 22 668 ms 64.125.26.13 so-0-0-0.mpr3.iah1.us.above.net
Hop # 23 628 ms 64.125.25.5
Hop # 24 650 ms 64.124.147.30 available.above.net
Hop # 25 828 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 26 823 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 27 633 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 28 894 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
08.07.2007 20:34:25 - IT WORKS
Tracing Route to 68.178.144.151:
Hop # 1 171 ms 192.168.1.254 dsldevice.lan
Hop # 2 49 ms 125.26.246.49 125-26-246-49.adsl.totbb.net
Hop # 3 68 ms 203.113.72.125
Hop # 4 67 ms 203.113.72.253
Hop # 5 70 ms 203.113.95.225
Hop # 6 69 ms 203.113.54.209
Hop # 7 69 ms 203.113.54.205
Hop # 8 69 ms 203.113.54.201
Hop # 9 67 ms 203.113.54.146
Hop # 10 67 ms 203.113.54.150
Hop # 11 70 ms 203.113.54.154
Hop # 12 68 ms 203.113.54.158
Hop # 13 69 ms 203.113.24.137
Hop # 14 68 ms 203.113.24.138
Hop # 15 70 ms 203.113.13.126 vl101.cs1-cwt.totisp.net
Hop # 16 421 ms 203.113.24.237
Hop # 17 418 ms 61.19.10.13
Hop # 18 67 ms 202.47.253.146
Hop # 19 288 ms 195.22.197.193 pal9-cat-telecom-3-id.pal.seabone.net
Hop # 20 325 ms 213.144.183.15 par31-par2-racc1.par.seabone.net
Hop # 21 735 ms 213.144.183.34 globalcrossing-2-us-
par31.par.seabone.net
Hop # 22 736 ms 67.17.198.42
Hop # 23 737 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 24 728 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 25 377 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 26 754 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
10.07.2007 18:15:48 - DOES NOT WORKS
Tracing Route to 68.178.144.151:
Hop # 1 64 ms 192.168.1.254
Hop # 2 51 ms 125.26.246.49 125-26-246-49.adsl.totbb.net
Hop # 3 83 ms 203.113.72.125
Hop # 4 85 ms 203.113.72.253
Hop # 5 85 ms 203.113.95.226
Hop # 6 83 ms 203.113.54.218
Hop # 7 81 ms 203.113.54.222
Hop # 8 84 ms 203.113.54.226
Hop # 9 85 ms 203.113.54.150
Hop # 10 84 ms 203.113.54.154
Hop # 11 82 ms 203.113.54.158
Hop # 12 84 ms 203.113.24.137
Hop # 13 82 ms 203.113.24.138
Hop # 14 83 ms 203.113.13.126 vl101.cs1-cwt.totisp.net
Hop # 15 711 ms 203.113.24.237
Hop # 16 85 ms 61.19.10.13
Hop # 17 81 ms 202.47.253.130
Hop # 18 586 ms 195.22.197.193 pal9-cat-telecom-3-id.pal.seabone.net
Hop # 19 638 ms 213.144.183.15 par31-par2-racc1.par.seabone.net
Hop # 20 665 ms 213.144.183.34 globalcrossing-2-us-
par31.par.seabone.net
Hop # 21 386 ms 67.17.198.42
Hop # 22 945 ms 208.109.112.137 ip-208-109-112-137.ip.secureserver.net
Hop # 23 974 ms 208.109.112.161 ip-208-109-112-161.ip.secureserver.net
Hop # 24 701 ms 216.69.188.18 ip-216-69-188-18.ip.secureserver.net
Hop # 25 388 ms 68.178.144.151 ip-68-178-144-151.ip.secureserver.net
Trace Route Complete
----------------------------------------------------------------------------------------------------
IP: 125.26.245.141
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
----------------------------------------------------------------------------------------------------
EchoLink Troubleshooter ver 1.2.0.5
Diagnostic Report for
Prepared Friday, January 04, 2008 12:14:54 SE Asia Standard Time
*** System Information ***
Windows XP Service Pack 2
*** Network Options ***
Shared Internet Connection: No
Wireless: No
*** Network Configuration ***
Local IP Address: 125.26.245.93
This is a public address that is directly reachable from the Internet.
This usually indicates that your system does not use a router to
access the Internet.
Connection type: Other
Shared Internet connection: No
Wireless network connection: No
*** TCP Connectivity Test ***
The TCP test FAILED: Cannot connect to server (10061).
This means that EchoLink might not be able to log in to the EchoLink
addressing servers.
The UDP port 5198 test FAILED: Receive failed (10060).
This means that EchoLink cannot communicate with other stations over
the Internet. Be sure your router, firewall, or security software is
allowing EchoLink to receive messages over UDP ports 5198 and 5199,
and that your Internet service provider (ISP) has not blocked this
port.
A few Internet service providers (ISPs) block a range of different UDP
ports, including ports 5198 and 5199 used by EchoLink. Although this
is relatively rare, check with your ISP if the rest of your
configuration appears to be OK.
-----------------------------------------------------------------------------------------
IP: 192.168.1.65
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
IP: 125.26.245.200
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
IP: 192.168.1.64
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
IP: 125.26.245.206
TCP Test: Succeeded.
UDP Test (5198): Receive failed (10060).
Tests complete.
--------------------------------------------------------------------------------------------------------------------
[PacketRule]
Name=Echolink
Enable=1
Allow=1
Log=0
Warning=0
Protocol=TCP
Direction=InboundOutbound
LocalPort=5200
[PacketRule]
Name=Echolink
Enable=1
Allow=1
Log=0
Warning=0
Protocol=UDP
Direction=InboundOutbound
LocalPort=5199
[PacketRule]
Name=Echolink
Enable=1
Allow=1
Log=0
Warning=0
Protocol=UDP
Direction=InboundOutbound
LocalPort=5198
------------------------------------------------------------------------------
Reply all
Reply to author
Forward
0 new messages