traceroute to yahoo.com (216.109.112.135), 30 hops max, 38 byte packets
1 210.67-19-245.reverse.theplanet.com (67.19.245.210) 2.568 ms 4.205 ms 3.948 ms
2 dsr2-1-vl8.dllstx4.theplanet.com (67.18.116.81) 3.523 ms 4.408 ms 3.971 ms
3 * dsr1-1-v1.dllstx2.theplanet.com (12.96.160.9) 4.500 ms *
4 * dist-vlan21.dsr3-1.dllstx3.theplanet.com (70.85.127.65) 3.445 ms 2.546 ms
5 ae1-0.ibr3.dllstx3.theplanet.com (70.85.127.35) 1.732 ms 5.231 ms 4.846 ms
6 101.ge-0-2-1.cr1.dfw1.us.nlayer.net (69.31.63.1) 5.501 ms 4.393 ms
And the support department tells me "this is normal". Meanwhile my SSH sessions take over a second to respond.
HELP!
Full Version: PACKET LOSS AGAIN
dunno maybe im being a retard but that looks ok to me :shock:
packet lost on dist routers is normal because of low priority on the routers so if its busy at that moment reponsetime on your packet will be delayed.
packet lost on dist routers is normal because of low priority on the routers so if its busy at that moment reponsetime on your packet will be delayed.
A traceroute to yahoo.com is rather useless unless you are working in the yahoo.com datacenter. 
I have been seeing packet loss in the past 2 days, on the entire “ThePlanet” network, and today it started again… 
//EDIT//
Now it seems to be back to normal
//EDIT//
Now it seems to be back to normal
I think, maybe sometime when I AM bored...I'll make a post also claiming about packet loss on the 99.99% SLA ServeMatrix network.
People, PACKET LOSS IS GOING TO HAPPEN - DEAL WITH IT.
If you don't WANT packet loss - get a server with ThePlanet.
People, PACKET LOSS IS GOING TO HAPPEN - DEAL WITH IT.
If you don't WANT packet loss - get a server with ThePlanet.
QUOTE (nForcer)
If you don't WANT packet loss - get a server with ThePlanet.
I have several The Planet servers, and I've gotten plenty of packetloss / downtime over the last few months.
Hey now, stop punching holes in nforcer's argument. He's just likely to get louder. Anyways, I can't see any problems because your running trace routes. Want something done? Get The planet a trace route and 100 pings to your server (summary only will be fine) then open a ticket.
Damn right I'll get louder. Gags, I serioulsy doubt you've had enough packet loss to warrent notice. I think you just posted to say something against me.
Bring proof next time please.
Bring proof next time please.
Also, please give traceroutes to and from your server when reporting packetloss. Since your data will take different routes to get back and forth from you to your server we need to see two traceroutes. Posting a single tracroute does us no good. We need to see the outgoing and return paths in order to properly troubleshoot packet loss.
Stupid question probably but how do I do a traceroute from my server (red hat enterprise with cpanel)
in ssh?
Andrew
in ssh?
Andrew
This is done by running "traceroute" which is in the RPM traceroute (if you have not installed it yet).
I get this when i type
traceroute MY IP in ssh
traceroute MY IP in ssh
CODE
1 traceroute: wrote MY IP38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
2 traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
3 traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
4 traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP38 chars, ret=-1
*
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
2 traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
3 traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
4 traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP38 chars, ret=-1
*
You need to open UDP ports in the range 33434-33534 (or so). Expirement with it to find the correct range. Default is from 33434.
How would I do that, i run APF
Andrew
Andrew
QUOTE (APC Hosting)
How would I do that, i run APF
Andrew
Andrew
CODE
vi /etc/apf/conf.apf
Hit i to enter insert mode
Add in the ports you want to open for inbound (INGRES).
The following is for a cPanel box
CODE
# Common ingress (inbound) TCP ports
IG_TCP_CPORTS="20,21,22,25,26,53,80,110,143,443,465,993,995,2082, 2083,2086,2087,2095,2096,3306,6666"
# Common ingress (inbound) UDP ports
IG_UDP_CPORTS="21,53,465,873"
# Common ICMP (inbound) types
# 'internals/icmp.types' for type definition; 'all' is wildcard for any
IG_ICMP_TYPES="3,5,11,0,30,8"
IG_TCP_CPORTS="20,21,22,25,26,53,80,110,143,443,465,993,995,2082, 2083,2086,2087,2095,2096,3306,6666"
# Common ingress (inbound) UDP ports
IG_UDP_CPORTS="21,53,465,873"
# Common ICMP (inbound) types
# 'internals/icmp.types' for type definition; 'all' is wildcard for any
IG_ICMP_TYPES="3,5,11,0,30,8"
Save and exit - hit 'esc' :wq 'enter'
Start APF
CODE
/usr/local/sbin/apf -s
QUOTE (APC Hosting)
I get this when i type
traceroute MY IP in ssh
traceroute MY IP in ssh
CODE
1 traceroute: wrote MY IP38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*traceroute: sendto: Operation not permitted
traceroute: wrote MY IP 38 chars, ret=-1
*
traceroute: sendto: Operation not permitted
Just to make sure replace "MY IP" with your home system's IP address.
lol I did Its just at work we are on a fixed ip, so replaced before i posted here.
It works
thanks
Andrew
It works
thanks
Andrew
Traceroutes are a horrible way to measure packet loss and latency.
Yep i am getting some serious loss too.
Tried from my FDC server -> Servermatrix Server &
Home Connection -> Servermatrix Server.
Gonna try i the other way around then open a ticket.
I'll post the results if anyone wants them.
Tried from my FDC server -> Servermatrix Server &
Home Connection -> Servermatrix Server.
Gonna try i the other way around then open a ticket.
I'll post the results if anyone wants them.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.