Closed petenorth closed 6 years ago
Hi @petenorth: The Things Gateway does not run a linux based OS so there is no shell.
I configured the gateway using the conole based registration process where the list of routers is restricted to those that are part of the The Things Network
This is not true. You can enter any plaintext into the field and it will accept it. So entering an IP address such as 192.168.1.5
should set the MQTT
address to 192.168.1.5:1883
. This would then be where your uplinks are published to.
If you set a private network server on the same IP, this should redirect the uplinks (and downlinks) to that network server (We have not tried to do this so far but technically it should work. )
How do I view the logs? Is it possible to logon to the OS of the gateway? SSH into it?
You need to use an FTDI with USB to do this. These are read-only debug logs: https://www.thethingsnetwork.org/docs/gateways/gateway/faq.html#q-i-want-to-get-in-depth-insightread-debug-messages-of-my-gateway-is-that-possible
I am presuming that it is running the gateway bridge and therefore only communicates using gRPC over MQTT.
The communication between the gateway and the backend is only via MQTT
. There is no gRPC involved.
Good luck and let us know how it goes.
Thanks Krishna for the thorough answer I'll update this issue with what I discover!
@KrishnaIyer Just an update, the TTN web console doesn't accept a IP address such as you described.
@petenorth : Yes it does. I tried it before answering this post.
I have been able to set the router to any string by using the ttnctl command line tool
OK have worked out why the different behaviour!
When creating a gateway via 'register gateway' the router field can be updated as you say.
For an existing router the screen does not allow the router field to be updated to an IP address it seems to have extra validation.
Thanks,
Peter.
You can still do it using ‘ttnctl’. Erase the existing setting on the gateway and de-activate it.
*re-activate it
@petenorth : Upon checking our V2 stack, we cannot support this feature currently as it requires updates to our Account Server. We have added this to our internal features list in V3. Closing this issue for now.
I am trying to create a gateway but it is saying gateway already created. yes, I did create a gateway with the same pycom board but with a different id. please help me what to do now?
This is a question
What do you want to do? What do you expect?
I would like to be able to use the ttn gateway to connect to other (private) networks (this is 'as well as' i.e. for prototyping purposes, I still intend to have my gateway connected to TTN most of the time :-)
What steps did you take? (Give as many details as possible so that we can reproduce it)
I configured the gateway using the conole based registration process where the list of routers is restricted to those that are part of the The Things Network
What went wrong? What is missing?
An option to configure the gateway to use different router address and port (presumably the port it uses is 1883 rather than the UDP server port of the router 1700)
What firmware is running on your gateway?
Not sure - how do I find this?
What do the logs show?
How do I view the logs? Is it possible to logon to the OS of the gateway? SSH into it?
If there was a way of SSH onto the gateway then presumably a configuration file could be edited with a different router and port address? I am presuming that it is running the gateway bridge and therefore only communicates using gRPC over MQTT.
Any Screenshots or Photos?
N/A
Do you think you can try to fix this yourself and submit a pull request?
Not without some help explaining how to open a shell in the device.