Re: [swinog] Swisscom VDSL -> TELIA -> USA problem
On 03.01.2012 23:13, Fredy Kuenzler wrote: Responsetime of hop 12 (80.91.251.98) is much higher than hop 11 (80.91.249.113) and a ping test did show lost packets on hop 12 but not on hop 11. 11 prs-bb1-link.telia.net (80.91.249.113) [AS1299] 25.882 ms 125.402 ms 25.827 ms 12 ash-bb1-link.telia.net (80.91.251.98) [AS1299] 108.584 ms 113.053 ms ash-bb1-link.telia.net (80.91.252.36) [AS1299] 158.407 ms Hop 11 is in Paris, hop 12 in Ashburn. I don't see anomalies considering the latency, as the atlantic is in between. ah, beginner's mistake. :) I was on some geoip page that told me it was in EU and the map showed a point in switzerland. The path seems to be multipath, but this is still ok. The loss / congestion could be on the return path, for proper diagnosis you need a traceroute from the other end, too. Sadly I can't do a traceroute from the other side. Check return pathes to proxies and compare them to the direct link... and, as Victor already said, don't expect guaranteed latecy on a xDSL service... yeah I know about the xDSL, guaranteed latency and "best effort" things. it's just a more or less one-man show and he does not bother about possible outages. the connection was working for about 2 years now and it is only slow on startup (after a 30min startup, the app is working normally). Seems it's just a problem while downloading some initial things. as it seems to be a problem that is catchy to solve, he'll work with the easy solution of using a proxy (startup time: 30seconds). thanks to all others who have answerd! - Thomas ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] Swisscom VDSL -> TELIA -> USA problem
Hi a customer got problems with an application (trading tool) downloading from a server in the USA (206.106.137.3). A traceroute below. Responsetime of hop 12 (80.91.251.98) is much higher than hop 11 (80.91.249.113) and a ping test did show lost packets on hop 12 but not on hop 11. the same application runs fine with a http proxy at LayerOne (init7), a proxy on a hosteurope vps or on a Cablecom connection. Is this the right place to report such a problem and aksing for help? Thank you! - Thomas traceroute to 206.106.137.3 (206.106.137.3), 30 hops max, 60 byte packets 1 192.168.14.1 (192.168.14.1) [AS8151/AS28513] 1.394 ms 1.759 ms 1.362 ms 2 10.136.21.195 (10.136.21.195) [AS65534] 12.432 ms 13.231 ms 12.544 ms 3 22-27.186-195.fws.bluewin.ch (195.186.27.22) [AS3303/AS44038] 17.615 ms 18.040 ms 17.171 ms 4 85-27.186-195.fws.bluewin.ch (195.186.27.85) [AS3303/AS44038] 20.192 ms 17.757 ms 17.520 ms 5 tge2-4.zhhia01p-rtdi01.bluewin.ch (195.186.51.5) [AS3303/AS44038] 17.251 ms 17.302 ms 17.138 ms 6 tge2-4.zhhia01p-rtdi01.bluewin.ch (195.186.51.5) [AS3303/AS44038] 17.072 ms 17.700 ms 16.912 ms 7 net1702.zhhdz09p-rtdi01.bluewin.ch (213.3.247.169) [AS3303/AS44038] 17.966 ms 17.929 ms 17.966 ms 8 202-0-186-195.bluewin.ch (195.186.0.202) [AS3303/AS44038] 21.432 ms 19.125 ms 19.938 ms 9 i79tix-005-ae0.bb.ip-plus.net (138.187.129.7) [AS3303] 17.386 ms 17.596 ms 21.142 ms 10 zch-b1-link.telia.net (213.248.90.237) [AS1299] 17.117 ms 17.686 ms 17.173 ms 11 prs-bb1-link.telia.net (80.91.249.113) [AS1299] 25.882 ms 125.402 ms 25.827 ms 12 ash-bb1-link.telia.net (80.91.251.98) [AS1299] 108.584 ms 113.053 ms ash-bb1-link.telia.net (80.91.252.36) [AS1299] 158.407 ms 13 level3-ic-130870-ash-bb1.c.telia.net (213.248.89.178) [AS1299] 114.600 ms 114.618 ms 124.009 ms 14 vlan80.csw3.Washington1.Level3.net (4.69.149.190) [AS3356] 120.899 ms 120.495 ms 120.235 ms 15 ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) [AS3356] 113.387 ms 114.457 ms ae-82-82.ebr2.Washington1.Level3.net (4.69.134.153) [AS3356] 120.064 ms 16 ae-3-3.ebr1.NewYork2.Level3.net (4.69.132.90) [AS3356] 112.147 ms 112.035 ms 112.211 ms 17 ae-1-100.ebr2.NewYork2.Level3.net (4.69.135.254) [AS3356] 116.964 ms 116.742 ms 110.879 ms 18 ae-5-5.car2.Stamford1.Level3.net (4.69.142.81) [AS3356] 116.335 ms 123.342 ms 116.644 ms 19 INTERACTIVE.car2.Stamford1.Level3.net (4.26.50.110) [AS3356] 122.280 ms 117.676 ms 116.042 ms 20 www.interactivebrokers.com (206.106.137.3) [AS11449] 118.604 ms 117.565 ms 118.602 ms 22ms ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] DNS: Clueless: Strange problems resolving ch domains...
i too see this . But only on debian lenny bind9 installations, not on every host and only since a few days. Maybe some security update introduced a bug. as a workaround i configured forwarders. - Thomas On 29.04.2010 10:50, Christian 'wiwi' Wittenhorst wrote: I got some reports from customers that some CH domains no not resolve... While testing if found: Only two of the [a-f].nic.ch seem to give replies... The ones that answer are exactly the ones that do not have IPv6 addresses... Happens at least for ksz.ch and swisscom.ch. Anyone else sees this? Any ideas? (820)[r...@svn /tmp]# sh ch dig swisscom.ch ns @A.nic.ch ;; Got referral reply from 130.59.1.80, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @A.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig swisscom.ch ns @B.nic.ch ;; Got referral reply from 130.59.211.10, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @B.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig swisscom.ch ns @C.nic.ch ;; Got referral reply from 147.28.0.39, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @C.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig swisscom.ch ns @D.nic.ch ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @D.nic.ch ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24625 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;swisscom.ch. IN NS ;; AUTHORITY SECTION: swisscom.ch.3600IN NS dns2.swisscom.com. swisscom.ch.3600IN NS dns1.swisscom.com. ;; Query time: 218 msec ;; SERVER: 200.160.0.5#53(200.160.0.5) ;; WHEN: Thu Apr 29 10:41:36 2010 ;; MSG SIZE rcvd: 79 dig swisscom.ch ns @E.nic.ch ;; Got referral reply from 204.61.216.47, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @E.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig swisscom.ch ns @F.nic.ch ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @F.nic.ch ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61901 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;swisscom.ch. IN NS ;; AUTHORITY SECTION: swisscom.ch.3600IN NS dns1.swisscom.com. swisscom.ch.3600IN NS dns2.swisscom.com. ;; Query time: 24 msec ;; SERVER: 194.146.106.10#53(194.146.106.10) ;; WHEN: Thu Apr 29 10:41:51 2010 ;; MSG SIZE rcvd: 79 dig ksz.ch ns @A.nic.ch ;; Got referral reply from 130.59.1.80, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @A.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig ksz.ch ns @B.nic.ch ;; Got referral reply from 130.59.211.10, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @B.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig ksz.ch ns @C.nic.ch ;; Got referral reply from 147.28.0.39, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @C.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig ksz.ch ns @D.nic.ch ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @D.nic.ch ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59974 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0 ;; QUESTION SECTION: ;ksz.ch.IN NS ;; AUTHORITY SECTION: ksz.ch. 3600IN NS zug.ch.ns.progon.net. ksz.ch. 3600IN NS udns1.ultradns.net. ksz.ch. 3600IN NS udns2.ultradns.net. ;; Query time: 228 msec ;; SERVER: 200.160.0.5#53(200.160.0.5) ;; WHEN: Thu Apr 29 10:44:25 2010 ;; MSG SIZE rcvd: 107 dig ksz.ch ns @E.nic.ch ;; Got referral reply from 204.61.216.47, trying next server ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @E.nic.ch ;; global options: printcmd ;; connection timed out; no servers could be reached dig ksz.ch ns @F.nic.ch ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @F.nic.ch ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1256 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0 ;; QUESTION SECTION: ;ksz.ch.IN NS ;; AUTHORITY SECTION: ksz.ch. 3600IN NS zug.ch.ns.progon.net. ksz.ch. 3600IN NS udns2.ultradns.net. ksz.ch.
Re: [swinog] mail "problems - port 25 on swisscom dsl (works fine for at least me though)
steven.glog...@swisscom.com wrote: well, actually.. it seems someone from us confirmed it in the comments of http://blog.neocid.li/?p=105 ... -steven well, i'm asking me why swisscom is not able to not filter traffic not going to servers from swisscom. - Thomas ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] mail "problems - port 25 on swisscom dsl
steven.glog...@swisscom.com wrote: did they phoned to the hotline? no maybe they sent spam or so and port 25 has been blocked in order to force the customer to use 587? is there any error message giving more information about problems on the customer side? there was a message: 573 573 Authentifizierte Verbindungen nicht moeglich. Bitte nutzen Sie den Port 587 oder kontaktieren Sie uns unter 0800 800 800. Connexions authentifiees pas possible. Veuillez utiliser le port 587 ou nous appeler au 0800 800 800. Collegamenti autenticati non possibili. Prego voi uso la porta 587 oppure contattare il numero 0800 800 800. Authenticated connections not possible. Please use port 587 or contact us on 0800 800 800. ther is no word "your dsl account got spam complaints" (or anything like that). - Thomas ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] mail "problems - port 25 on swisscom dsl (works fine for at least me though)
Am Wed, 03 Mar 2010 13:26:26 +0100 schrieb Jeroen Massar: > Thomas Mueller wrote: >> hi >> >> customers phoned me that they could not send emails anymore. needed to >> switch to port 587. > > Maybe there is something filtering between you and them. They should be > using port 587 anyway which is supposed to be the submission port. > Unless they are running a fullblown SMTP setup on a DSL link of course. yeah, nothing against port 587, but blocking port 25 without informing customers BEFORE is not the way to go. (most) mail-clients use port 25 if you do not specify it manually. maybe swisscom has reasons to do this - trojans/viruses sending spams maybe? > >> now heard from others that swisscom is blocking port 25 ??? what the >> heck is going on ? > > Which "others" and what metrics do they have? a colleague too got calls from customers not able to send mails anymore. take a look at this blog entry http://blog.neocid.li/?p=105 ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] mail "problems - port 25 on swisscom dsl
hi customers phoned me that they could not send emails anymore. needed to switch to port 587. now heard from others that swisscom is blocking port 25 ??? what the heck is going on ? - Thomas ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] ProLiant & Debian
Am Mon, 15 Feb 2010 09:41:56 +0100 schrieb Schlageter Benjamin: > Hi everybody > > Has someone any experiences with Debian on a ProLiant 120 and/or 160? on ProLiant 110 G5 it's working. on some but not all hp servers debian is officially supported. have a look here: http://h18004.www1.hp.com/products/servers/software/debian/index.html - Thomas ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
