I’m trying to forward LoRa Packets to my LoRaWAN server. This server only supports IPv6.
RouterOS does not seem to be able to forward packets to it. I only get errors in the log, regardless of whether I’m using the IP address, or a domain:
IPv6 support is installed, but disabled by default as of 6.46.4.
First make a backup; you can export your config by clicking on New Terminal, then issue:
/export file=myLoraWanGW.rsc
Click on Files, locate myLoraWanGW.rsc, right click, download.
You can open this file with any text editor (like Wordpad on windows) in case you wan’t to check your previous config details, or reuse the commands to build up your configuration.
To enable IPv6:
Go to System > Packages, IPV6 is disabled by default. Select it then click enable, and reboot.
Once it boots back, do a System > Reset Configuration, to defaults so that default IPv6 firewall rules are deployed on your firewall.
At that point you can reconfig it either manually, or by copying and pasting the bits you need (e.g. IPv4, or LoRa bits) on a New Terminal from the .rsc file, which contains all the CLI commands that create that exported configuration.
Yeah, I know that, which is a very sad thing in itself.. Mikrotik should fix that as well.
But obviously I have IPv6 enabled and I am also able to ping the LoRaWAN server in question using the integrated ping utility, but only with it’s raw address, not using the Domain.
Trying the Domain gives the following error message:
[admin@lora] > ping gateway.domain
invalid value for argument address:
invalid value of mac-address, mac address required
invalid value for argument ipv6-address
failure: dns name exists, but no appropriate record
Yes, the DNS does resolve AAAA records, it is not the fault of my DNS servers.
It looks like IPv6 support is fundamentally broken with RouterOS.
The firewall is completely disabled.
Even though the Router does have IPv6 connectivity, none of “IPv6”, “[IPv6]” or “gateway.domain” works for the LoRa server. The error message is always the same “Couldn’t resolve xy”.
So it looks like the LoRa packages does not resolve the address correctly or is using an IPv4-only socket.
The ping utility cannot resolve IPv6 addresses from domain name.
Yes, that is a bug. But it is unrelated to the problem you are trying to solve, so don’t get distracted by that.
Go back to the solution suggested above (install LoRa only AFTER IPv6 was enabled).
Where did it say that?
I’ve tried it anyway: I’ve uninstalled the LoRa module, rebooted, installed the LoRa module. Didn’t help.
Actually it would be totally ridiculous, if this would have helped, so I’m still kind of glad it did not help.
Did you reset to defaults after enabling IPv6?
That is another bug: IPv6 is disabled by default, and at the time the default settings are made there is no IPv6 so its default settings are not made.
Only when IPv6 is first enabled and THEN a reset to defaults is done, the IPv6 settings are made.
I agree it is ridiculous. The only positive thing is that IPv6 is enabled by default in v7 beta.
Basic IPv6 support is included since RouterOS 6.47beta48.
While the module still is not able to resolve AAAA records correctly, at least static IPv6 addresses do work now.
