Gateway status not connected, no data visible


#1

Hi,

I have a problem with the correct working of this gateway.

Gateway Lorank 8
BeagleBoard.org Debian Image 2016-05-13
Linux lorank8 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l GNU/Linux
running Poly-packet forwarder,

TTN entry in global_conf.json:
{ “server_address”: “router.eu.thethings.network”,
“serv_port_up”: 1700,
“serv_port_down”: 1700,

and: “stat_format”: “semtech”,

added in local_conf.json:
“gps”: true,
“fake_gps”: true,

Frequency Plan : Europe868MHz
Router; ttn-router-eu
Starting poly_pkt_fwd in foreground:

##### 2018-08-23 18:46:40 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 2
# CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 2 (104 bytes)
# PUSH_DATA datagrams sent: 3 (816 bytes)
# PUSH_DATA acknowledged: 0.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (0.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### BEACON IS DISABLED!
### [JIT] ###
# INFO: JIT queue contains 0 packets.
# INFO: JIT queue contains 0 beacons.
### [GPS] ###
# No time keeping possible due to fake gps.
# Manual GPS coordinates: latitude 51.41279, longitude 5.47990, altitude 18 m
### [PERFORMANCE] ###
# Upstream radio packet quality: 100.00%.
# Upstream datagram acknowledgment quality for server "52.18.106.103" is 0.00%.
# Upstream datagram acknowledgment quality for server "router.eu.thethings.network" is 0.00%.
# Downstream heart beat acknowledgment quality for server "52.18.106.103" is 0.00%.
# Downstream heart beat acknowledgment quality for server "router.eu.thethings.network" is 0.00%.
# Downstream datagram content quality for server "52.18.106.103" is 0.00%.
# Downstream datagram content quality for server "router.eu.thethings.network" is 0.00%.
# Downstream radio transmission quality for server "52.18.106.103" is 0.00%.
# Downstream radio transmission quality for server "router.eu.thethings.network" is 0.00%.
# Semtech status report send.
##### END #####

This gateway has a static IP address and has recently been registered.
The status remains “not connected”, and although it seems that data is forwarded, it is not visible at the TTN Console.
The gateway is visible on http://noc.thethingsnetwork.org: and I can ping to 8.8.8.8 (google) but tracroute gives:

root@lorank8:~# traceroute www.google.com
www.google.com: Name or service not known

I created a dns-nameservers 8.8.8.8 8.8.4.4 entry in /etc/network/interfaces but that had no effect

Is this a DNS issue? Does anyone have an idea how I can solve this?

Kind regard,
Marco


#2

Hi Marco… pls format :wink:


#3

Sure, that’s looks better :wink:


#4

tnx Marco !


#5

Done!

root @ lorank8: ~ / lorank8v1 # host router.eu.thethings.network
Host router.eu.thethings.network not found: 2 (SERVFAIL)

It appears to be a DNS issue; this gateway has a static ip and for this version I had to do some adjustments

BeagleBoard.org Debian Image 2016-05-13
Linux lorank8 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l GNU/Linux

/etc/resolv.conf has 2 entries:
Generated by Connection Manager
nameserver 127.0.0.1
name server :: 1

Adding an entry nameserver 8.8.8.8 (google dns) has no effect because after a reboot this has been removed from the resolv.conf (symlink with avahi deamon). I could not remove this symlink.

Adding an entry nameserver 8.8.8.8 in / etc / network / interfaces also had no effect.

Solution is to remove Connman:
Apt remove connman

I made a backup from resolv.conf
cp /etc/resolv.conf /etc/resolv.conf_backup
resolv.conf removed:
rm /etc/resolv.conf
cp /etc/resolv.conf_backup /etc/resolv.conf (symlink has been removed)
Add name servers in resolv.conf (eg.nameserver 8.8.8.8 and nameserver 8.8.8.4)

reboot (ifdown eth0 gives problems if executed via ssh ;-))

root @ lorank8: ~ / lorank8v1 # host router.eu.thethings.network
router.eu.thethings.network is an alias for bridge.eu.thethings.network.
bridge.eu.thethings.network has address 52.169.76.203

That took me many hours, but I learned a lot again … and the status on the TTN Console is: “connected”