HELP Sat 121 Latency issues

[bajadudes]

whats this?

3 * 843 ms * 172.30.48.93
4 * 764 ms 838 ms 172.30.48.254

no idea who they are or why they are in there

[Phranc]

That's a local address either in his modem or the NOC.

[bajadudes]

Anyone with a starband connection see this inbetween their modem and the NOC path when doing a tracert? I don't think I ever have. it's usually all 148's until it leaves the NOC.

I do now notice it in previous posts in this thread.

I have quite a few customers using a cisco VPN without any issues save the obvious slowdown.

[allend15]

Anyone with a starband connection see this inbetween their modem and the NOC path when doing a tracert? I don't think I ever have. it's usually all 148's until it leaves the NOC.

I do now notice it in previous posts in this thread.

I have quite a few customers using a cisco VPN without any issues save the obvious slowdown.

Just to be clear. Anything I have put in here is when I am not on VPN. I maybe tracing the route to our vpn server in california but i am not logged onto vpn when I do it. Actually I just tried to ping our server in CA (while logged into VPN) and get 100%loss.

then I pinged yahoo.com (while logged into VPN) and I get 1% loss. Not sure what this all means.

[bajadudes]

I think it means that VPN for you on SB is FUBAR.

[allend15]

I think it means that VPN for you on SB is FUBAR.

Except that up until June I had no issues. Never lost my vpn connection. Right now it is screaming fast (for vpn) and have no issues until about the time the Wet Coast comes on-line.

Yesterday the SB dude I talked to was trying to get his supervisor (who was in a meeting) to check into this issue as they have been having packet loss issues. The computer and data I have posted is non-vpn releated other than that the server i was pinging is a vpn server. It's still bad for yahoo.com (not right now but later).

While writing this the satellite link went down. lovely!

[Ag2000CO]

whats this?

3 * 843 ms * 172.30.48.93
4 * 764 ms 838 ms 172.30.48.254

no idea who they are or why they are in there

I get the same thing. I just assumed they were servers dealing with the SAT, traffic management, etc. communications pre-processor ahead of the NOC

1 * 1 ms 192.168.2.1
2 * 2 ms vsat-148-63-... (my modem)
3 * 599 ms 172.30.48.91
4 * 598 ms 172.30.48.254
5 * 500 ms misc-148-78-243-36.pool.starband.net

[bajadudes]

I understand that it used to work and I sincerely hope they resolve your issue. However in the long and storied history of issues that have presented themselves on this and the previous starbandusers forum there are innumerable instances of something working and then suddenly not working because of some change on the engineering end. Mysteriously they sometimes start working again or they never work right again.

Right now the way things seem to be configured, it aint working for you when the west coast starts to come online......that points to congestion being the issue

there are not many ways to mitigate that and all solutions have other effects on the network as a whole.

let churn lower the contention ratio ( fewer customers less revenue )

change the data rate (Affects overall speeds for everyone)

change the modulation ( lower Ebno in fringe areas )

change the coding rate ( lower Ebno in fringe areas )

I am not defending these anomalies, just pointing them out.

[Vance G]

whats this?

3 * 843 ms * 172.30.48.93
4 * 764 ms 838 ms 172.30.48.254

no idea who they are or why they are in there

172.x.x.x. are shown as Admin/RX_IP for SkyEdge stuff. You can see them in Sky Manage.

[Vance G]

I understand that it used to work and I sincerely hope they resolve your issue. However in the long and storied history of issues that have presented themselves on this and the previous starbandusers forum there are innumerable instances of something working and then suddenly not working because of some change on the engineering end. Mysteriously they sometimes start working again or they never work right again.

Right now the way things seem to be configured, it aint working for you when the west coast starts to come online......that points to congestion being the issue

there are not many ways to mitigate that and all solutions have other effects on the network as a whole.

let churn lower the contention ratio ( fewer customers less revenue )

change the data rate (Affects overall speeds for everyone)

change the modulation ( lower Ebno in fringe areas )

change the coding rate ( lower Ebno in fringe areas )

I am not defending these anomalies, just pointing them out.

Ya gotta be kidding. We just have to wait until so many people get pissed off they go to WB or Hughes?

That's no way to run a business...

[allend15]

I understand that it used to work and I sincerely hope they resolve your issue. However in the long and storied history of issues that have presented themselves on this and the previous starbandusers forum there are innumerable instances of something working and then suddenly not working because of some change on the engineering end. Mysteriously they sometimes start working again or they never work right again.

Right now the way things seem to be configured, it aint working for you when the west coast starts to come online......that points to congestion being the issue

there are not many ways to mitigate that and all solutions have other effects on the network as a whole.

let churn lower the contention ratio ( fewer customers less revenue )

change the data rate (Affects overall speeds for everyone)

change the modulation ( lower Ebno in fringe areas )

change the coding rate ( lower Ebno in fringe areas )

I am not defending these anomalies, just pointing them out.

Ya gotta be kidding. We just have to wait until so many people get pissed off they go to WB or Hughes?

That's no way to run a business...

I am seriously thinking WB. I hear next year they are putting up a new satellite.

I have asked them to move me to cluster 092 and see if that solves the problem and they have said that won't matter. That cluster is also having packet loss issues. I don't know. I am running out of patience.

[bajadudes]

well they are working on it so who knows maybe they will figure out how to resolve it.

If you go to WB let us know how it works out.

Vance thanks for the info on the 172, IP addy

[allend15]

UPDATE! Because there are people still with ASI issues they tweaked the system so everyone would still be able to use the network and not have any FCC issues. HOWEVER they asked if I wanted to move to cluster 092 and see if that would be better and YES it has been. No drops since moving to cluster 092 on Monday 8/2. Yippee!

Thanks for all the help out there. I learned a lot.