Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 28 20:42
    eduardoveiga synchronize #523
  • Oct 28 20:42

    eduardoveiga on namespace

    wip (compare)

  • Oct 28 16:27

    gustavosbarreto on agent_info

    (compare)

  • Oct 28 16:27

    gustavosbarreto on master

    agent: add platform, arch to de… (compare)

  • Oct 28 16:27
    gustavosbarreto closed #524
  • Oct 28 16:14
    gustavosbarreto synchronize #524
  • Oct 28 16:14

    gustavosbarreto on agent_info

    agent: add platform, arch to de… (compare)

  • Oct 28 16:06
    gustavosbarreto opened #524
  • Oct 28 14:35

    gustavosbarreto on agent_info

    agent: add platform, arch to de… (compare)

  • Oct 28 11:59
    eduardoveiga labeled #523
  • Oct 28 11:59
    eduardoveiga opened #523
  • Oct 28 11:59
    eduardoveiga review_requested #523
  • Oct 28 11:58

    eduardoveiga on namespace

    wip (compare)

  • Oct 27 22:15

    eduardoveiga on namespace

    wip (compare)

  • Oct 27 19:44

    eduardoveiga on namespace

    wip (compare)

  • Oct 27 17:51

    eduardoveiga on namespace

    wip (compare)

  • Oct 26 21:00

    gustavosbarreto on master

    agent: override default handler… (compare)

  • Oct 26 21:00

    gustavosbarreto on agent_handler

    (compare)

  • Oct 26 21:00
    gustavosbarreto closed #522
  • Oct 26 20:49
    eduardoveiga review_requested #522
Otavio Salvador
@otavio
Hello there!
Fabiano da Rosa Gomes
@gomes-fdr
boa tarde Otavio, uma dúvida com relação ao shellhub - com o agent rodando no dispositivo que desejo acessar, eu tenho acesso aos processos do dispositivo? Pergunto pq por estar rodando em um container, imaginamos que teriamos acesso apenas aos processos do container...
Luis Gustavo S. Barreto
@gustavosbarreto
Boa tarde
Fabiano da Rosa Gomes
@gomes-fdr
opa, tudo bem Luis, pode me ajudar nessa duvida?
Luis Gustavo S. Barreto
@gustavosbarreto
Fabiano, como o container roda em modo privilegiado ele tem acesso aos processos do "host" da máquina
Então quando tu fizer SSH para o dispositivo tu vai estar "dentro" da máquina apesar do agent rodar no container
Fabiano da Rosa Gomes
@gomes-fdr
interessante - era justamente essa a nossa dúvida, pq nosso desejo é justamente controlar os processos e nossas apps que estaram rodando fora do container do agent
Luis Gustavo S. Barreto
@gustavosbarreto
Fizemos isso utilizando uma feature de "namespace" do kernel linux
Fabiano da Rosa Gomes
@gomes-fdr
grato Luis, vou levar isso adiante para iniciarmos alguns testes praticos
Luis Gustavo S. Barreto
@gustavosbarreto
Se tiver alguma dúvida no processo pode ir largando aqui que nós vamos respondendo
Fabiano da Rosa Gomes
@gomes-fdr
Muito obrigado pela atenção Luis, vamos testar e te dou um retorno na sequencia - abraço!
Otavio Salvador
@otavio
@gustavosbarreto eu revisei a PR da Domarys mas a PR nao apareceu aqui. Tinhamos que vincular os outros repositorios aqui tb.
gapaluec
@gapaluec
Can I replace port 22 with any other port number? And what all changes are required to do the same?
Luis Gustavo S. Barreto
@gustavosbarreto
@gapaluec Hi
Otavio Salvador
@otavio
@gapaluec you wish to change the port on the server side, or on the target side?
Luis Gustavo S. Barreto
@gustavosbarreto
@gapaluec Edit docker-compose.yml file and replace the port 22 with something else in ports section of ssh service
gapaluec
@gapaluec

@gustavosbarreto I did change the docker-compose.yml, but still the endpoint API was returning 22
{"api":"localhost", "ssh": "localhost:22", "mqtt": "localhost:1883"}

Also, there should be an option to change "localhost" returned by endpoint to a valid domain name / ip address... As I was trying shellhub on AWS with a domain name.

Luis Gustavo S. Barreto
@gustavosbarreto
@gapaluec
Luis Gustavo S. Barreto
@gustavosbarreto
@gapaluec can you please open a issue for this?
Luis Gustavo S. Barreto
@gustavosbarreto
Luis Gustavo S. Barreto
@gustavosbarreto
surfinside
@surfinside
Hello,
I would like mount an ssh tunnel, unfortunately I have an error
channel 2: open failed: unknown channel type: unsupported channel type
debug1: channel 2: free: direct-tcpip: listening port 443 for 10.10.10.1 port 443, connect from 127.0.0.1 port 51926 to 127.0.0.1 port 443, nchannels 4
channel 3: open failed: unknown channel type: unsupported channel type
debug1: channel 3: free: direct-tcpip: listening port 443 for 10.10.10.1 port 443, connect from 127.0.0.1 port 51927 to 127.0.0.1 port 443, nchannels 3
MyPC - > INTERNET -> ShellHub <- INTERNET <- Router (10.10.10.1/24) <- RPi (Up on ShellHub (10.10.10.xxx/24))
MyPC:443 = https://10.10.10.1
I thank you in advance
Luis Gustavo S. Barreto
@gustavosbarreto
@surfinside Are you trying to create a tunnel through ShellHub server?
I think this is not supported by ShellHub