On Monday, 15 בOctober 2007 16:20, Michael Ben-Nes wrote: > Hi, > > I'm working on a project that require me to ssh to a US server. > The problem is that through Netvision & Bezeqint the performance are > horrible ( though Bezeqint its almost always faster then Netvision ) > > I don't mind paying double for a better connection. Waiting 10 sec to see > something happens over ssh is too much. > > The IP of the server is 216.139.210.179 and its located at HostWay data > center in Texas. > > Any recommendations?
Hi Miki, The problem you described can have various reasons to it, so I will add a few disclaimers. 1. Israeli ISPs shift traffic over lines from time to time, due to their notorious tendency to buy STM1 links, due to them being cheaper (a STM4 takes time to fill, and while it's not full, they waste money). Thus, their STM-1s get filled up quickly, and they shift traffic based on alot of variables, depends on what you've bought, the kind of traffic you pass through, etc. 2. There are four "virtual" segments to check. a. One is your local loop (meaning the connection from your office to the ISP, and I include in this the connection inside you office). b. Two is the connectivity of the edge router that you connect to on the ISP side to the ISP internal core network. c. The international connectivity of the ISP in regards to the IP block which you are part of, since they don't advertise all IP blocks equally, including possible QoS tagging they may do, or other traffic shaping. d. The local loop of the ISP you want to get, including the connectivity in the LAN of the hosting place, or company. I suggest you try to isolate each of these, and see where the network problem is. Of course that `a.` will be very easy to check, `b.` you'll have to take the word of your ISP, but you can nudge them, `c.` is the same as `b.` but the possibility of the ISP lying to you about it is higher, and `d.` is hard to check unless you have connections on the other end of the pond. 10 seconds delays are very unusual on today's Internet that connects western world countries. It can result from various reasons, including congestion, packet loss (which can be either due to congestion, or due to "virtual congestion" because of QoS, or due to duplex mismatch), or something fishy in the ssh client side or the SSH server side. Usually, you wont have to debug all the possible interractions of the variables described above to find the culprit. It usually takes me not more than 1/3 of the possible checks, with a very difficult problem. Use common sense, and use "GOOD TOOLS". Be systematic. Write stuff down. > Best, > Miki --Ariel -- Ariel Biener e-mail: [EMAIL PROTECTED] PGP: http://www.tau.ac.il/~ariel/pgp.html ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
