Good to see someone was listening as the UK & EU Versions now closer & more realistic…still an unjustified delta for a small plastic shoe IMHO but progress;-)
Best would be a single SKU with both types included, would make ordering/stocking easier and reduce overal costs (both for RS & for those of us operating across boarders). Having a little bag with various plug option components that are fit on location is after alll standard operating mode for many networking devices per my earlier comments., also as of tonight there are 120 of 1 Sku and 270 of the other - there could be 390 of a common SKU @wienkegiezeman
I have opend the following connections for the TTIG on the firewall:
TTN Connection: TCP / UDP: router.REGION.thethings.network Port:1700
TTN Regestration: TCP: lns.REGION.thethings.network Port: 443
TTN CUPS: TCP: mh.sm.tc Port: 7007
Replace the REGION with your configured region, like eu
Yes, in the post i mixed the rules of my ESP8266 singel channel gateway and those of my TTIG GW.
The TTIG use only websockets over TCP 443 for communication with the backend.
Gateway status is presented in console (When console operates, but I am not going in to that on this topic) but information derived from behaviour is different from what we know with UDP and protobuf type connected gateways.
With UDP and protobuf connected gateways everytime data is received from the gateway the last seen time is updated. The data that triggers the last seen time can be uplink data packets or status or link-ckeck-data. Using TTNCTL you get the same time as form consol at which the gateway is seen.
In the case of TTIG I observed a different behaviour. Here only uplink packets change the last seen time in console. Any other data will not update the last seen time. TTNCTL is no presenting an up to date last seen time.
As a result of this, a fully operational TTIG that has not received any uplink packet since powering on can have a last seen time in console of hours or many days ago!.
I think this is information you might want to know.
Correction: TTNCTL is not updated by any link activity!