Packet forwarder port not responding

Network and Routing The Things Stack v3
#1

Hello, I’m trying to send packets to packet forwarder port:
UDP target IP: eu1.cloud.thethings.network
UDP target port: 1700
message: [2, 68, 68, 0, 25, 55, 38, 55, 73, 80, 56, 33]{“rxpk”:[
{
“time”:“2013-03-31T16:21:17.528002Z”,
“tmst”:3512348611,
“chan”:2,
“rfch”:0,
“freq”:866.349812,
“stat”:1,
“modu”:“LORA”,
“datr”:“SF7BW125”,
“codr”:“4/6”,
“rssi”:-35,
“lsnr”:5.1,
“size”:32,
“data”:"-DS4CGaDCdG+48eJNM3Vai-zDpsR71Pn9CPA9uCON84"
}
]}

It was working few days ago (I was getting responses according to packet_forwarder/PROTOCOL.TXT at master · Lora-net/packet_forwarder · GitHub ) but it doesn’t respond now.
I tried from two independent internet connections.

Is there some problem on the server side? Or have I been blocked?

#2

May this be related? The Things Network Status - Update UDP Gateway Server Configuration of The Things Network

#3

If you are not using a gateway with LoRaWAN packets you should not send data to the life community environment. That environment is for the community to implement LoRaWAN solutions, not for other traffic.

#4

Is there any staging/devel environment instead?

#5

No.

But you can run your own instance on your own server - it’s open source.

#6

I see. But this still doesn’t answer the question if I was blocked or there was an outage. (It works now BTW)

#7

Not sure how to answer the question of “I was doing something off-piste with the live community shared servers and it stopped working, why”

If you were blocked, we won’t actually know as we aren’t staff members here - perhaps you could contact TTI directly?

You say you were using UDP and you linked to a report on the update of UDP gateway server configuration. This seems to have a high degree of correlation.

#8

This exactly. And TTI staff is also not going to have an answer for these kind of questions.

–

I’m not seeing any widespread server-side problems today, so this seems to be specific to what you’re doing.

That’s possible. The Things Stack can (temporarily) block UDP traffic for a specific gateway EUI from your IP address if there is another active connection for the same EUI. This is fully automated and not monitored by human operators.

We actually updated some configuration related to blocking UDP traffic coming from different IP addresses. This should mostly improve connectivity for gateways with LTE backhaul, but it may also have solved your issues.

1 Like
#9

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