+ Responder ao Tópico



  1. Vai uma lista de variaveis pro hotspot, veja se alguma te serve:

    Variables
    All of the Servlet HTML pages use variables to show user specific values. Variable names appear only in the HTML source of the servlet pages - they are automatically replaced with the respective values by the HotSpot Servlet. For each variable there is an example of its possible value included in brackets. All the described variables are valid in all servlet pages, but some of them just might be empty at the time they are accesses (for example, there is no uptime before a user has logged in).
    • Common server variables:
      • hostname - DNS name or IP address (if DNS name is not given) of the HotSpot Servlet ("hotspot.example.net")
      • identity - RouterOS identity name ("MikroTik")
      • login-by - authentication method used by user
      • plain-passwd - a "yes/no" representation of whether HTTP-PAP login method is allowed ("no")
      • server-address - HotSpot server address ("10.5.50.1:80")
      • server-name - name of hotspot server
      • ssl-login - a "yes/no" representation of whether HTTPS method was used to access that servlet page ("no")
      • server-name - HotSpot server name (set in the /ip hotspot menu, as the name property)
      • interface-name - physical HotSpot interface name (in case of bridged interfaces, this will return the actual bridge port name)
    • Links:
      • link-login - link to login page including original URL requested ("http://10.5.50.1/login?dst=http://www.example.com/")
      • link-login-plain - link to login page, not including original URL requested ("http://10.5.50.1/login")
      • link-logout - link to logout page ("http://10.5.50.1/logout")
      • link-status - link to status page ("http://10.5.50.1/status")
      • link-orig - original URL requested ("http://www.example.com/")
    • General client information
      • domain - domain name of the user ("mt.lv")
      • interface-name - name of the physical interface, on which client is connected (in case of bridge, it will contain the name of bridge port)
      • ip - IP address of the client ("10.5.50.2")
      • logged-in - "yes" if the user is logged in, otherwise - "no" ("yes")
      • mac - MAC address of the user ("01:23:45:67:89:AB")
      • trial - a "yes/no" representation of whether the user has access to trial time. If users trial time has expired, the value is "no"
      • username - the name of the user ("John")
    • User status information:
      • idle-timeout - idle timeout ("20m" or "" if none)
      • idle-timeout-secs - idle timeout in seconds ("88" or "0" if there is such timeout)
      • limit-bytes-in - byte limit for send ("1000000" or "---" if there is no limit)
      • limit-bytes-out - byte limit for receive ("1000000" or "---" if there is no limit)
      • refresh-timeout - status page refresh timeout ("1m30s" or "" if none)
      • refresh-timeout-secs - status page refresh timeout in seconds ("90s" or "0" if none)
      • session-timeout - session time left for the user ("5h" or "" if none)
      • session-timeout-secs - session time left for the user, in seconds ("3475" or "0" if there is such timeout)
      • session-time-left - session time left for the user ("5h" or "" if none)
      • session-time-left-secs - session time left for the user, in seconds ("3475" or "0" if there is such timeout)
      • uptime - current session uptime ("10h2m33s")
      • uptime-secs - current session uptime in seconds ("125")
    • Traffic counters, which are available only in status page:
      • bytes-in - number of bytes received from the user ("15423")
      • bytes-in-nice - user-friendly form of number of bytes received from the user ("15423")
      • bytes-out - number of bytes sent to the user ("11352")
      • bytes-out-nice - user-friendly form of number of bytes sent to the user ("11352")
      • packets-in - number of packets received from the user ("251")
      • packets-out - number of packets sent to the user ("211")
      • remain-bytes-in - remaining bytes until limit-bytes-in will be reached ("337465" or "---" if there is no limit)
      • remain-bytes-out - remaining bytes until limit-bytes-out will be reached ("124455" or "---" if there is no limit)
    • Miscellaneous variables
      • session-id - value of 'session-id' parameter in the last request
      • var - value of 'var' parameter in the last request
      • error - error message, if something failed ("invalid username or password")
      • error-orig - original error message (without translations retrieved from errors.txt), if something failed ("invalid username or password")
      • chap-id - value of chap ID ("\371")
      • chap-challenge - value of chap challenge ("\357\015\330\013\021\234\145 \245\303\253\142\246\133\175\3 75\316")
      • popup - whether to pop-up checkbox ("true" or "false")
      • advert-pending - whether an advertisement is pending to be displayed ("yes" or "no")
    • RADIUS-related variables
      • radius<id> - show the attribute identified with <id> in text string form (in case RADIUS authentication was used; "" otherwise)
      • radius<id>u - show the attribute identified with <id> in unsigned form (in case RADIUS authentication was used; "0" otherwise)
      • radius<id>-<vnd-id> - show the attribute identified with <id> and vendor ID <vnd-id> in text string form (in case RADIUS authentication was used; "" otherwise)
      • radius<id>-<vnd-id>u - show the attribute identified with <id> and vendor ID <vnd-id> in unsigned form (in case RADIUS authentication was used; "0" otherwise)
    Creditos para a pessoa que postou nesse post.

    Abraços a todos

  2. Citação Postado originalmente por edcomrocha Ver Post
    Vai uma lista de variaveis pro hotspot, veja se alguma te serve:



    Creditos para a pessoa que postou nesse post.

    Abraços a todos
    Cara, muito boom esses codigos seus ! parabens a vc e apessoa que postou esse tópico !

    Parabéns !

    me add no msn awe: hylberth@gmail.com



  3. Cara, como faço pra mostrar o profile e para o cliente ?

  4. Ola amigo.

    Acredito que o limite para o numero de clientes não estará no Hardware, pois possuo um server mikrotik com 1,8 Ghz de processador AMD (só não consegui o modelo exato), 512MB de memória e HD de 320 GB e atendo 1500 clientes, sendo geralmente um pico máximo de 700 clientes simultâneos. Não se preocupe tanto com o Hardware (a não ser as interfaces de rede levando em consideração o link transitavel por elas) pois no meu caso mesmo de 1,8 Ghz de processamento ocupo no máximo 50% de processamento, de 512 de memória utilizo no máximo 25% e de HD não chega nem gerar porcentagem ( menos de 1%).

    Resumindo: O mikrotik é um excelente sistema e que onera pouco hardware, acredito que um hardware confiável é indiscutivel, mas o grande segredo são as configurações.

    Abraços.

    Rodrigo Godoy



  5. Citação Postado originalmente por Hylberth Ver Post
    Cara, muito boom esses codigos seus ! parabens a vc e apessoa que postou esse tópico !

    Parabéns !

    me add no msn awe: hylberth@gmail.com
    olha minha em ccsClique na imagem para uma versão maior

Nome:	         Novo(a) Imagem de bitmap.jpg
Visualizações:	154
Tamanho: 	29,3 KB
ID:      	25079






Tópicos Similares

  1. Respostas: 21
    Último Post: 19-06-2015, 06:57
  2. Respostas: 3
    Último Post: 20-09-2013, 16:55
  3. Respostas: 8
    Último Post: 18-05-2013, 21:19
  4. Hotspot - direcionar para pagina e nao para status
    Por geovaneboth no fórum Redes
    Respostas: 2
    Último Post: 23-02-2013, 07:59
  5. Hotspot - Não direciona para página de login
    Por MarcianoMarques no fórum Redes
    Respostas: 2
    Último Post: 07-02-2013, 11:11

Visite: BR-Linux ·  VivaOLinux ·  Dicas-L