Problems accessing Viasat Modem page (Surfbeam 2)

  • 1
  • Problem
  • Updated 2 months ago
The Viasat Modem page (192.168.100.1) on the Surfbeam 2 modem no longer loads correctly, Is anyone else having the same issue?
Photo of David S.

David S.

  • 37 Posts
  • 8 Reply Likes
  • Sad because this is the only tool left that Viasat gives us pc users to check our modems status.

Posted 2 months ago

  • 1
Photo of Old Labs

Old Labs

  • 417 Posts
  • 369 Reply Likes
Working fine for me on the same version, UT_3.7.8.7.0 - might want to try a different browser to see if any difference (or flush the Viasat browser cache)
Photo of Voyager

Voyager

  • 594 Posts
  • 159 Reply Likes
Mine is also working fine. I trust you have cycled power with all connected cables removed in addition to trying another browser as already mentioned.
Photo of Steve Frederick-VS1/Beam314

Steve Frederick-VS1/Beam314, Champion

  • 3211 Posts
  • 2066 Reply Likes
Working just fine for me.
Photo of Bob Lexus

Bob Lexus

  • 357 Posts
  • 129 Reply Likes
It is your browser causing that

Either use a different browser or clear your cache & cookies
Photo of David S.

David S.

  • 37 Posts
  • 8 Reply Likes
I have tried different browsers even 2 different operating systems and they all have problems accessing that page. 

May I ask one more question please? A few days ago I was trying to better secure our router, downloaded the latest firmware update, made sure a couple security vulnerabilities were mitigated by changing settings as directed at the Cisco website. But I also blocked java(not javascript) and activeX in the routers firewall page

So my question would be does the Viasat Modem page require java or activeX to display correctly?

Anyway I want to thank you all because without your help I probably would not have remembered that I changed some of the routers settings. 
Photo of ExSatUser

ExSatUser

  • 1879 Posts
  • 1089 Reply Likes
Possibly want to try to unblock and see if it makes a difference.
Photo of Voyager

Voyager

  • 593 Posts
  • 159 Reply Likes
I don’t know what is needed for correct operation, but I do know that if you change the configuration of something and parts of it stop working it is about 99.44% certain that your changes caused the problem.
Photo of Old Labs

Old Labs

  • 415 Posts
  • 369 Reply Likes
Last I checked , the modem status pages used JavaScript and CGI script (no Java nor ActiveX). Make sure your not filtering CGI that's where most of the dynamic info you're missing comes from and the JavaScript invokes the CGI script.
(Edited)
Photo of David S.

David S.

  • 37 Posts
  • 8 Reply Likes
Hi all, 

Just wanted to come back and let you all know it was the blocking of java in the router firewall that was causing the problem, I unchecked the box next to java and the modem status page is back to working normal again.

I'm not sure what CGI is Old Labs but I don't recall a setting for that in our routers firewall settings and I only messed with blocking java and activeX.

Again I want to say thank you to all of you that replied and even if they weren't the right suggestions believe me they did help because it made me remember the changes I made to the router.

Merry Christmas All :)  
Photo of Old Labs

Old Labs

  • 376 Posts
  • 331 Reply Likes
Added info only for those interested...

CGI - common gateway interface. A way to write programs (binary executables) that execute on a web server (in this case the web server embedded in the modem). Written in Java, C, Perl, etc. - frequently associated with Java on the server side where executed.

Examples of how invoked on the Viasat modem(s):

http://192.168.100.1/index.cgi?page=triaStatusData
http://192.168.100.1/index.cgi?page=modemStatusData

The data returned is mapped directly to the status pages you see and should look familiar if you decipher it. The hashtags separate each element. 

Obviously  the problem's related to the Java filtering but more importantly you got it working - I can actually reproduce the exact symptom by simply blocking JavaScript and the CGI still works but never gets invoked.

FWIW, same problem reported in some of the Cisco/Linksys forums - specifically blocking Java winds up blocking some Javascript (although the two are not the same). Famous last words... but I didn't change anything ;)
(Edited)