meshctrl.js throws missing netif error on deviceInfo read about meshcentral HOT 10 CLOSED

from what ive learn use ' on linux and " with windows,
and IF no special characters like $ @ in the nodeid then use without both

from meshcentral.

Just a followup. I'm making some assumptions here, but it is erroring on returning netinfo. I was able on the first device to pull that info through the web console tab.

> netinfo
{
  lo: {
    0: {
      mac: "00:00:00:00:00:00"
      type: "ethernet"
      status: "up"
      address: "127.0.0.1"
      family: "IPv4"
      netmask: "255.0.0.0"
    }
    1: {
      mac: "00:00:00:00:00:00"
      type: "ethernet"
      status: "up"
      address: "::1"
      family: "IPv6"
      netmask: "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff"
    }
  }
  enp0s31f6: {
    0: {
      mac: "11:11:11:11:11:11"
      type: "ethernet"
      status: "up"
    }
  }
  wlp1s0: {
    0: {
      mac: "22:22:22:22:22:22"
      type: "ethernet"
      status: "up"
      address: "XXX.XXX.XXX.XXX"
      family: "IPv4"
      gateway: "XXX.XXX.XXX.XXX"
      netmask: "255.255.255.0"
    }
    1: {
      mac: "22:22:22:22:22:22"
      type: "ethernet"
      status: "up"
      address: "fe11::"fe11:"fe11:"fe11:"fe11%3"
      family: "IPv6"
      netmask: "ffff:ffff:ffff:ffff::"
    }
  }
  bridge0: {
    0: {
      mac: "22:22:22:22:22:22"
      type: "ethernet"
      status: "up"
      address: ""fe11::"fe11:"fe11:"fe11:"fe11%4"
      family: "IPv6"
      netmask: "ffff:ffff:ffff:ffff::"
    }
  }
  vnet0: {
    0: {
      mac: "22:22:22:22:22:22"
      type: "ethernet"
      status: "up"
      address: "fe11::"fe11:"fe11:"fe11:"fe11%4"
      family: "IPv6"
      netmask: "ffff:ffff:ffff:ffff::"
    }
  }
  wg0: {
    0: {
      status: "up"
      address: "XXX.XXX.XXX.XXX"
      family: "IPv4"
      netmask: "255.255.255.255"
    }
  }

from meshcentral.

A side question here. Is it possible to pull the Node ID through the Web GUI? I'm currently using the listDevices command which is not convenient for testing.

from meshcentral.

i can replicate the issue, looking into it now for you 👍

from meshcentral.

the issue is because your nodeid will have a $ in it which isnt phased correctly at the command line
try putting nodeid with ' around instead --id 'LONGNODE$ID'

from meshcentral.

@si458 You are correct. The executed command works with ' but not " for the nodeid. I can also confirm the not working nodeid has a $ in it whereas the devices that worked did not have the $.

I think you've nailed this one. Any idea how to get the nodeid out of the webgui? Would just be convenient for testing.

from meshcentral.

@timaw7 the nodeid is actually part of the URl itself
https://meshcentral.myserver.com/?viewmode=10&gotonode=lupekvnEmP$6OBe0yhtXEzBl9FUAcuyF@T7fs1gIQxCDGgK4l1YBk0Ziua01TLZA
so in this example its the gotonode= value
and to be honest after a quick check, the is actually nowhere listing the node id haha, not even in the console tab!
will add a nodeid option into the console tab, so you can type nodeid and it will return its id for you! 👍

from meshcentral.

@si458 I see it in the URI now. Right in front of my face. Yeah at least on the console tab would be ideal.

I've confirmed that this works in a script for all my devices (over 80+). Also a side note, this fixes another issue I was having. Some device calls were not returning at all as opposed to erroring like above. This apparently fixes it all. Thanks for the help! Closing out the issue.

from meshcentral.

side note: just added Node ID: into the info output in the console tab hehe e8da6a6

from meshcentral.

side note: 7cf14a2 ive pushed a fix to show invalid device id if no data at all was returned

from meshcentral.