Difference between revisions of "StarV3 Multipractik for Linux"

From StarOS Community Wiki
Jump to navigation Jump to search
m
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
StarV3 Multipractik for Linux is currently a bash application with it's own units and firmware databases in text format that can manipulate with all available options.<br>
StarV3 Multipractik for Linux is currently a bash application with it's own units and firmware databases in text format that can manipulate with all available options.
This page is under heavy development and I will try to add all info and capabilities as soon as possible.<br>
All access is done without need for user to enter passwords (but that is an option).<br>
App for now allows users to see unit database/password, but it can be set that only the root of the system/PC can change them. Configuration files for Sv3Multi resides in /etc folder and is under the root control.


Conversion to SQLite database is underway, with optional MySQL database. This will make it easier to maintain, and will allow for strict user controll (what can user access in the apps menu).
This page is under heavy development and I will try to add all info and capabilities as soon as possible.
 
All access is done without need for user to enter passwords (but that is an option).
 
App for now allows users to see unit database/password, but it can be set that only the root of the system/PC can change them. Configuration files for Sv3Multi resides in /etc folder and is under the roots control.
 
Conversion to SQLite database is underway, with optional MySQL database. This will make it easier to maintain, and will allow for strict user controll (what can user access in the apps menu).
 
Also, there is experimenting/development with StarV3 TUI to be able to download all scripts not accessible for download, and automatic manipulation of TUI screens in order to automaticaly configure units.




Line 40: Line 45:
** SSH login
** SSH login
** Access via Winbox if GUI exists
** Access via Winbox if GUI exists
** Pinging (1400 bytes size)
** Traceroute to the unit


== Linux/Unix hosts ==
== Linux/Unix hosts ==
* Various manipulations
* Various manipulations
** SSH login
** SSH login
** Deleting SSH key from "known hosts" file
** Pinging (1400 bytes size)
** Traceroute to the unit


== Contact ==
== Contact ==

Latest revision as of 07:39, 1 March 2011

StarV3 Multipractik for Linux is currently a bash application with it's own units and firmware databases in text format that can manipulate with all available options.

This page is under heavy development and I will try to add all info and capabilities as soon as possible.

All access is done without need for user to enter passwords (but that is an option).

App for now allows users to see unit database/password, but it can be set that only the root of the system/PC can change them. Configuration files for Sv3Multi resides in /etc folder and is under the roots control.

Conversion to SQLite database is underway, with optional MySQL database. This will make it easier to maintain, and will allow for strict user controll (what can user access in the apps menu).

Also, there is experimenting/development with StarV3 TUI to be able to download all scripts not accessible for download, and automatic manipulation of TUI screens in order to automaticaly configure units.


StarV3/StarOS

  • Backups
    • Config file
    • CBQ script
    • Firewall script
    • NAT
    • SNMP to file
    • Kernel log file
    • System info file
  • Editing
    • CBQ script (in editor of your choice)
    • Firewall script (in editor of your choice)
    • NAT (in editor of your choice)
  • Various manipulations
    • SSH login
    • Deleting SSH key from "known hosts" file
    • Speed tests
    • Upload of firmware
    • Upload of old configs
    • Upload of configs from different unit
    • Automatic password change
    • Rebooting
    • Pinging (1400 bytes size)
    • Traceroute to the unit
    • ...

Mikrotik

  • Backups
    • Full backup with date/time in filename
  • Various manipulations
    • SSH login
    • Access via Winbox if GUI exists
    • Pinging (1400 bytes size)
    • Traceroute to the unit

Linux/Unix hosts

  • Various manipulations
    • SSH login
    • Deleting SSH key from "known hosts" file
    • Pinging (1400 bytes size)
    • Traceroute to the unit

Contact

Ljubomir Ljubojevic (DrLove73)
Novi Sad, Serbia, Europe
office *at* plnet.rs
www.plnet.rs