No connection of Mikrotik wap lr8 gateway to TTN

Gateways MikroTik Gateways
1

Hi everybody,

I have a problem with my Mikrotik lr8 gateway to connect to the TTN. It keeps staying disconnected.
I am new to LoRaWAN and in the posts I read, I could not find a solution to my problem.

My gateway is connected to the PC via LAN using the default IP 192.168.88.1 which I set manually with the subnet mask 255.255.0.0. The DNS server settings I left open.

As gateway server address I used “eu1.cloud.thethings.network” or “TTN V3 (eu1)” respectively in both, the TTN setting and the gateway setting. The gateway log shows continuously the error message: “lora-dl: [TTN V3 (eu1)] Couldn’t resolve eu1.cloud.thethings.network”

My Gateway EUI (= Hardware ID) is 503035412D3E4750. I used the same value as Gateway ID. My frequency plan is EU_863_870_TTN.

I attached the configuration which I got from my gateway. I hope this might give some additional hints about the problem.

I would appreciate a lot if you could assist me to get my gateway running. Please let my know, if you need additional information.

Many regards, Gerhard

gateway configuration:

mar/08/2024 22:16:45 by RouterOS 6.49.7

software id = 80HX-WA3L

model = RBwAPR-2nD

serial number = HEP098F3AE0

/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX
country=germany distance=indoors frequency=auto installation=outdoor
mode=ap-bridge ssid=MikroTik-0145E1 wireless-protocol=802.11
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=hotspot
/ip pool
add name=dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=dhcp disabled=no interface=wlan1 name=defconf
/lora servers
add address=eu.mikrotik.thethings.industries down-port=1700 name=TTN-EU
up-port=1700
add address=us.mikrotik.thethings.industries down-port=1700 name=TTN-US
up-port=1700
add address=eu1.cloud.thethings.industries down-port=1700 name=
“TTS Cloud (eu1)” up-port=1700
add address=nam1.cloud.thethings.industries down-port=1700 name=
“TTS Cloud (nam1)” up-port=1700
add address=au1.cloud.thethings.industries down-port=1700 name=
“TTS Cloud (au1)” up-port=1700
add address=eu1.cloud.thethings.network down-port=1700 name=“TTN V3 (eu1)”
up-port=1700
add address=nam1.cloud.thethings.network down-port=1700 name=“TTN V3 (nam1)”
up-port=1700
add address=au1.cloud.thethings.network down-port=1700 name=“TTN V3 (au1)”
up-port=1700
/interface list member
add comment=defconf interface=wlan1 list=LAN
add comment=defconf interface=ether1 list=WAN
add list=LAN
/ip address
add address=192.168.88.1/24 interface=ether1 network=192.168.88.0
/ip dhcp-client
add comment=defconf disabled=no interface=ether1
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=192.168.88.1 gateway=
192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
/ip firewall filter
add action=accept chain=input comment=“enable ether1” dst-port=80
in-interface=ether1 protocol=tcp
add action=accept chain=forward comment=“defconf: accept in ipsec policy”
ipsec-policy=in,ipsec
add action=accept chain=forward comment=“defconf: accept out ipsec policy”
ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment=“defconf: fasttrack”
connection-state=established,related
add action=accept chain=forward comment=
“defconf: accept established,related, untracked” connection-state=
established,related,untracked
add action=drop chain=forward comment=“defconf: drop invalid”
connection-state=invalid
add action=drop chain=forward comment=
“defconf: drop all from WAN not DSTNATed” connection-nat-state=!dstnat
connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment=“defconf: masquerade”
ipsec-policy=out,none out-interface-list=WAN
/lora
set 0 antenna=uFL disabled=no name=“Dold Gateway1” servers=“TTN V3 (eu1)”

2

and

How can it resolve DNS lookups if it doesn’t know the IP address of any DNS servers?

3

Thanks a lot for the immediate reply.

Well, sorry I am not that familiar with DNS and DHCP etc.
Could you give me some advice how to set up my Ehternet-Port.

My gateway is connected via LAN on my PC. My internet connection to access the TTN server is connected via WLAN.

Here are my settings (ipconfig/all):
C:\Users\User>ipconfig/all

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : DESKTOP-2MJ1SLP
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : fritz.box

Ethernet-Adapter Ethernet:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physische Adresse . . . . . . . . : 78-F2-9E-F1-67-83
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 2:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physische Adresse . . . . . . . . : 86-EF-18-9D-44-B9
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physische Adresse . . . . . . . . : 84-EF-18-9D-44-BA
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WLAN:

Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3165
Physische Adresse . . . . . . . . : 84-EF-18-9D-44-B9
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::75d2:ab6:3e56:5664%17(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.178.20(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Donnerstag, 7. März 2024 21:09:35
Lease läuft ab. . . . . . . . . . : Dienstag, 19. März 2024 13:13:45
Standardgateway . . . . . . . . . : 192.168.178.1
DHCP-Server . . . . . . . . . . . : 192.168.178.1
DHCPv6-IAID . . . . . . . . . . . : 176484120
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-27-4C-5A-4C-78-F2-9E-F1-67-83
DNS-Server . . . . . . . . . . . : 192.168.178.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physische Adresse . . . . . . . . : 84-EF-18-9D-44-BD
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

These are my TCP/IPv4 settings:

IP address: 192.168.88.25
subnet mask: 255.255.0.0
default gateway: . . .

DNS server address:
preferred DNS server: . . .
alternative DNS server: . . .

Please let me know if I can provide additional information.

Many regards, Gerhard

4

Is your gateway connected to your PC or to your FritzBox? The gateway has to be connected to the internet eg. by a router.

5

This appears to be connected to the PC directly, as it is an unconventional IP address. There will be few tutorials that will recommend this to be configured from a router standpoint.

6

You have a conflicting configuration on the MikroTik. Keep in mind a MikroTik device starts out as an router/access point and LoRaWAN has been added later.

To make the MikroTik work you first need to connect it to internet. That can be done using UTP cable or WLAN. By default MikroTik expects you to use a cable connection and connect your PC to the access point the devices creates. By connecting your PC to the LAN port you keep the MikroTik from connecting to the internet (you can setup the MikroTik to use WLAN to connect to your fritzbox but that requires more knowledge of setting up routers)

I would suggest resetting the router to default configuration, use a network cable to connect it to your fritzbox, connect the PC to the access point the mikrotik provides and check if you can still connect to the web using that PC. If that works you can start setting up LoRaWAN.

7

Hi all,

let’s start with the good news - my gateway seems to be up and working !!!

I followed your advice and disconnected the gateway from the PC, made a reset and connected it to the Fritz Box via LAN cable and immediatelly after that I got a connected status with traffic in the live data box.

Well, I guess I really should spend some time and take some lessons in network technology now.

My understanding was, I have to set the Ethernet interface adapter (TCP/IPv4) settings manually to the address 192.168.88.1 to get access to the gateway connected to my PC. I mean I had access, but at the same time probably blocked something else. Now I switched back the settings to automatic mode and using the winbox tool to connect to the gateway I found out that the actual address to connect to the gateway is 192.168.178.117 (assigned by DHCP?)

After all it works and I like to thank you all for your kind assistance.

Many regards, Gerhard