Can someone of the tech team/ moderator confirm that this is not possible please?
So I can talk to my prof for my master thesis and look for an alternative solution…
I’d just like to make an observation with regards The Things Network, and this forum & Kickstarter etc; We the loyal backers that have/or are wait the gateways need the communications to be better, communication from The Things Network is at best slow and inconsistent. (correct me if I’m wrong) I’ve not received or seen any acknowledgement from the team with regards any issues or what cause of action that those reporting issues need to take; yet the team and founder is re-tweeting and like all positive comments, which leads me to believe the either he/team is unaware of all these gateways that have issues or simply us backers are getting ignored as they try to push for more sales and promotion of the product as the conference!?
I was so hopeful but feel like I’ve forked out £££ for a product that has suffered delay after delay and has then been delivered with some fundament issues across the product range; as before happy to work to get this resolved; but not to be ignored by The Things Network team or see them liking good comments and hiding way from the true picture of this project.
I guess my frustration is starting to show, but I feel I like many other have given a fare chance for a response/acknowledgement
I agree. I’m lucky that mine works. But I fully understand your frustration.
In fact, as I’ve said before, TTN team should focus on getting product out, documentation out, and helping those with problems.
The upcoming conference is nice… but should be lower priority really. And the lack of an official statement or response on these forums about what they are doing to help the unlucky backers with dead on arrival gateway is not professional.
Yes Grahame, I fully agree. Most of the backers could settle for a bit of tweaking to make things work smoothly, is my estimate. However, there appear to be quite a number of people having very similar issues with the TTN-gateway. And lots of ideas, suggestions and test results are doing the rounds, also from users that managed to activate their gateways. But, apart from some forum moderation and participating in these technical discussions, there is nothing from The Things Network. No acknowledgment, no task force announcement, no status & outlook. This needs to improve.
@vanesp and lets face it the conference is quite frankly a waste of time if us backers get ignored and start to voice the lack of support and communication from the team; as any reasonable investor/business wouldn’t like the bad press
FYI; I’m trying hard to kickstart an official response; you can follow me on twitter @GrahameHorner
I’ll hopefully get someone to reply or DM me after my tweet
@wienke please whip your team into shape and get some form of issue desk and/or acknowledgement announcement released to backers about gateway issues #weareheretohelp but cant except begin #ignored
My understanding is that TTN is relying on the folks at TWTG to try to identify and fix the problems related to the gateways; for example, in this forum, TTN core team member, Hylke Visser, wrote the following when Leondegeling was among the first to report the reboot problem…
Dec '17 - Hi @Leondegeling , I saw the debug log you sent us and notified our hardware experts at twtg.io about it. I’ll ping them again to see if they found anything. As for the source code, our colleagues are also working on getting the source code…
I can’t recall yet any instances where someone has reported having multiple gateways with one or more working and also one or more that doesn’t. Anyone know of any such circumstance?
Haven’t read that either. Your question indicates that you suspect the problem might be “the environment”: network router or ISP. Likely, because from the outside, it looks like the TTN-gateway goes through the activation process but somehow can not complete the activation process with the server(s) involved.
but no official report or communication to all backers (from what I can see) about what/or how to help resolve or communicate to the team information that could possibly help determine the root course. Microsoft, Apple, Google are big companies an get bad press for the number of bugs/issues, but all we are asking here is something that the team should already be able to do issue a communication to the fact the gateways have issues, and forum to log you have issues along with some details firmware version/logs etc. to help us help you (TTN) and (TWGT.IO)
We the backers aren’t bothered about the commercial/structure of the business or the support network (or lack of) behind the scenes, we just want to help this work and resolve issues; so again better communications please…
I can confirm that I personally have a commercial internet connection and my gateway is connection is to the DMZ; I can also confirm that the firewall logging doesn’t should any traffic out from the TTN gateway is blocked or in fact any traffic has actual been sent? also my ISP has confirmed in the past that they don’t block any traffic/ports on commercial connections
And, is it clear / shown that the TTN-gateway knows where to go on the local network? For that, it needs to know the gateway address and it needs to have access to a DNS-server that responds in time. It gets this information upon request, when connecting to the internet, presumably the local DHCP-server. Have not traced that yet, but it is worth investigating.
Yes, I was wondering about that possibility, thinking those who are experiencing problems might wish to try in multiple environments. But it may be that very few folks have multiple gateways and it’s a hardware problem. If someone has one working and one that doesn’t, it’d certainly be interesting to know what happened if the LoRa module were swapped from one to the other (though I’d probably be too nervous about inflicting damage to try that). I worry that problems in the manufacturing process may have resulted in incapacity in some LoRa modules and/or the connector. If that’s the case, part of the reason for lack of communication may be that various parties (TTN, TWGT, manufacturer, module maker) are trying to sort out where, if anywhere, any liability rests amidst lawyerly advice to work things out privately.
forget finger pointing solves nothing; simple acknowledgement would be “we are aware that we are receiving a number of reports with regards to problems with gateway activation/connectivity intermittent/cycling reboots; we are working to identify the root cause with our 3rd party vendors, at this time we haven’t been able to establish a pattern however rest assured that we will work with the community to identify/resolve these issues. In the meantime we have setup a issue logging process where backers can raise a ticket with information regards their gateway and environmental configuration and see progress/suggestions on what to try to help resolve the issues seen.”
I have a slip-slip DNS configuration and a DHCP server within my DMZ and can confirm that the TTN gateway gets issued a IP address and the router.eu.thethings.network appears in the DNS cache which resolves to 52.169.76.203 and a tracert showns that the route is possibly problematic, however I would personal not expect this to reboot the gateway and as the firewall shows no traffic to the router ? that doesn’t sound like it could be the issue
Tracing route to bridge.eu.thethings.network [52.169.76.203]
over a maximum of 30 hops: