Port forwarding and IP-adressing

Try&Error to get communication with TTN …

My test-TTN-Gateway by cable now connected to my LAN at easily accessible location (to support any required maintenance etc.).
WLAN-interface still as ‘independent’ WAP, and will stay that way until cabled TTN-interface OK, and then remains as ‘hidden emergency’ side-entry.
At TTN-Console now Gateway reported as ‘Disconnected’.
Looking for causes for that report, in hindsight perhaps not best setup, because forgot that forwarding for port 1700 becomes a requirement, and (relative to internet) at my LAN the TTN-Gateway is behind multiple, chained routers mostly operating with DHCP, in combination with many clients with fixed IP-addresses.
That configuration on purpose to get reliable communication between the ‘residents’ at certain (W)LAN-segments, and for easy access for the ‘temps’ and ‘mobiles’.

Advise requested from other users:
would it be a practical solution to set all routers to apply semi-fixed IP for mutual communication?
That is:

  • leave all routers in the chain at DHCP, but in the routers set that selected MAC-adresses should get a defined fixed IP-address.
    Those fixed IP-addresses are the entry-ports to the next router in the chain.
  • set forwarding for port 1700 for those selected fixed IP-adresses
  • result is that the routers form a chain with semi-fixed IP-adresses which is open at port 1700

A variant is to connect the TTN-Gateway to the ‘first’ router nearest to external internet-interface, but the negative, practical aspect is that this internet-interface is located at a well-shielded place in the house, probably not favourable for LoraWAN: for decent operation that means running of an extra cable to better position of the TTN-Gateway. As alternative, use Wifi-interface for the TTN-Gateway not really favourable, based on experience with normal Wifi of that ‘first’ router.

Meanwhile trying to setup this concept, but still short opinion requested of more experienced users, whether this concept is ‘wise’ (or ‘why not’).

Any one of which can be the problem! You need to be clear of any impediements to full internet connection, with no port blocking…1700 is a key one - but it depends on how you have the device configured - you have not yet told us (per other threads). Fundamentally what PF are you using? Which servcer instance? That will inform us as to what ports you REALLY need.

Tip: to check if your GW configured ok simply tether to you mobile phone and use that and bypass all the other connection prevention devices you have blocking the way! :slight_smile:

Another option to test is take GW to that 1st device and connect directly either Enet or WiFi and test your set up there - if good (as with mobile teher) then you know its the crap and layering in the middle that you need to resolve, if 1st instance or mobile have problems likely = your GW set up or TTN config that you have got wrong. Note also some service providers have a history of thinking they own the internet vs just supplying a service and may be filtering/blocking specific ports, which you might want to check on also…

If we recommend something that brings your house of cards crashing down, how will that sit?

Five gateways in this office, haven’t touched any of them in months and months. And any maintenance needed is done over the network. So proximity in the same building/complex is not a thing.

Network setups like this would be somewhat off-topic for the forum - it’s not feasible to help people with their infrastructure and given the technical nature of LoRaWAN there is an expectation that you can do networking 101.

Hopefully you’ve come across the KISS acronym? Now is the time to deploy it. Just plug in / connect to WiFi to the router that’s actually connected to your internet line. Not buying an extra cable to get your kit working and asking us to unravel your knitting is pushing the boundaries of good will.

It need not be permanent - once you’ve got it working, you can then fiddle about with it to your hearts content. But perhaps spare us your self-generated pain.

And start telling us actual details - like make/model of gateway, configuration, cluster you are using as you have been asked before.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.