Code Monkey home page Code Monkey logo

network-analyzer's Introduction

network-analyzer

overkill tool to help non-technical gamers troubleshoot network-related netplay issues

Getting Started

Prerequisites

  • ~500 MB of disk space
  • Virtualization (VT-x/AMD-V) enabled in your BIOS
  • VirtualBox installed
  • Vagrant installed
  • Reboot after installing VirtualBox

Usage

Initial setup

  • Download and extract Network Analyzer
  • Open a command prompt / terminal in the analyzer directory
  • Create and configure the virtual machine with:
$ vagrant up
  • This may take a few minutes to complete
  • Check the output for the following, and visit the link in your browser
==> default: You can view the analyzer at one or more of the following addresses...
Connection to 127.0.0.1 closed.
    default: http://10.0.2.64/smokeping
    default: http://192.168.1.64/smokeping

Updating configs

  • To change targets edit config/UserTargets.yml
    (There are example configs in the examples directory)
  • To change other smokeping config, edit data/smokeping/* after the initial setup
  • Open a command prompt / terminal in the analyzer directory
  • Reload the configuration with:
$ vagrant reload
  • This may take a few minutes to complete
  • Refresh your browser after it finishes
  • If refreshing fails, check the output a different link

Shutting down the analyzer

  • Open a command prompt / terminal in the analyzer directory
  • Shutdown the virtual machine with:
$ vagrant suspend

Checking if the analyzer is running

  • Open a command prompt / terminal in the analyzer directory
  • Check th status of the analyzer with:
$ vagrant status

Deleting the analyzer

  • Open a command prompt / terminal in the directory
  • Delete the virtual machine with:
$ vagrant destroy
  • This will delete the entire virtual machine and smokeping stats
  • The smokeping config is saved in the data directory

FAQ

  • Q: How do I check for and/or enable virtualization on my machine?
    A: There's a lot of guides on the internet, but this one seems good

  • Q: Why does vagrant take so long on Windows?
    A: It's a known issue, see Vagrant CLI on Windows is very slow

  • Q: Isn't this just smokeping?
    A: Yes, for now; but maybe it will do other things later!

  • Q: This seems like overkill, is there not an easier way?
    A: Yea, probably

License

License is Unlicense.

network-analyzer's People

Contributors

cennis91 avatar

Watchers

James Cloos avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.