By performing a dump on the output interface of my Raspberry I see the traffic being forwarded to the Handlers, the ones do not have a valid Radius request response in my understanding.
20:56:03.683957 IP 192.168.88.243.55983 > 13.76.168.68.1700: RADIUS, Access-Request (1), id: 0x79 length: 237
20:56:03.684575 IP 192.168.88.243.55983 > 52.62.83.250.1700: RADIUS, Access-Request (1), id: 0x79 length: 237
20:56:04.053008 IP 13.76.168.68.1700 > 192.168.88.243.55983: [|radius]
20:56:04.125858 IP 52.62.83.250.1700 > 192.168.88.243.55983: [|radius]
20:56:10.090125 IP 192.168.88.243.55983 > 13.76.168.68.1700: RADIUS, Access-Request (1), id: 0x3b length: 236
20:56:10.090841 IP 192.168.88.243.55983 > 52.62.83.250.1700: RADIUS, Access-Request (1), id: 0x3b length: 236
20:56:10.463806 IP 13.76.168.68.1700 > 192.168.88.243.55983: [|radius]
20:56:10.535532 IP 52.62.83.250.1700 > 192.168.88.243.55983: [|radius]
I found a solution! I am working with Raspi and the single_chan_pkt_fwd application to send to the TTN handlers, well, since Rasp has two network interfaces (eth0 and wlan0) I deleted my gateway record in TTN with the eth0 network card MAC and made a new one Register with the MAC of the wlan0 card, now the Gateway is online!
That’s not really a question/related for this topic… ’ connecting your single channel gateway with 800l chip ’
I suggest to open a separate topic for this subject.
I had successfully setup a RasperryPi+RFM95W single channel gateway with the code from https://github.com/hallard/single_chan_pkt_fwd but i am stuck on a problem with The Things Network. Btw my end node (for testing purpose) is an im880b and i am using the ABP activation. This node is sending messages at 3 different frequencies 868,1MHz, 868,3MHz, 868,5MHz. But i take into account only the one at 868,1 because my gateway is set at 868,1 with SF7BW125.
The problem is that i dont see any messages in the application console on TTN ! I checked on the TTN gateway console and I noticed that my DevAddr are almost all the time wrong. It’s supposed to be 26 01 19 08 :
I am really lost on where the problem can come from. I tried my ABP activation with a multi channel gateway (sx1308 picocell gateway from semtech) and everything is working fine (the DevAddr is never wrong) so i suppose the problem doesnt come from my end node and comes from the gateway. Maybe there is a frequency to set for the udp transmission in the single_chan_pkt_fwd code ? If someone can helps me it would be nice because i really dont know what to do now.
Around 7 meters, do you think it’s not enough ? Do you think the problem only come from the distance and there is no mistake about DevAddr or a UDP frequency to set in the code ?
Thanks I will try to test with a longest distance this afternoon !
UDP does not have a frequency. It might also happen that you have other LoRaWAN nodes around, or LoRa, or even non-LoRa transmission around you. However, looking at numbers, this seems not the case (random counters, as one example). 7 meters is not bad.
I suddenly remember to have had some similar problem with the same gateway software; did you try to restart it?
By the way, I went with a different version of the same software that also should allow for downlinks (the Hallard one does not).
Just disable, in your LoRa device, frequencies not received by gateway
LMIC_setupChannel(0, 868100000, DR_RANGE_MAP(DR_SF12, DR_SF7), BAND_CENTI); // g-band
for (int i = 1; i <= 8; i++) LMIC_disableChannel(i); // Only channel 0 is enabled
I am sure the messages come from my node because i see it in real time appearing in my terminal and if you look carefully i noticed that every DevAddr has the form XX XX 26 01 or XX XX 19 08 ! And the real DevAddr is 26 01 19 08. What can produce this kind of mistake ?
Yes but this other version is using 2 RFM95W ? i would like to use only one
Regarding the errors, try restarting the gateway, and also to stay far if possible (but 7 meters should be ok). Regarding the other version, read carefully the linked post.
That’s a very suggestive description.
A single channel gateway is of course not a LoRaWAN compliant gateway.
Therefore the ‘whether worthwhile’ is quite misleading.
Initially a LoRaWAN gateway was relatively expensive, but these days a TTIG can be bought for less than € 100 and a RAK concentrator board based DIY gateway can be build starting for around € 125 (and up). With these prices and an assortment of available gateways there are currently no good reasons for having Single Channel ‘gateways’ anymore.
Single Channel ‘gateways’ actually negatively impact proper operation of regular LoRaWAN gateways.
So there is no case of ‘whether worthwhile’ here.
Indeed, and as the article specifically does not detail advantages\dissadvantages, readers are very likely to assume that as the range is similar (exactly as expected) then the extra expense of a compliant gateway is not worthwhile.
Mmm… if you add the legend for interpreting colors in the charts, it will become clear that the SCG is inferior, and likely you could reach a better range with the Lorix, at least because of the better antenna - by the way, it is not clear how far you moved from the gateways and where they stopped to receive.
However, I must say I reached better ranges with both SCGs and Lorix
Hi,
I designed my own node/forwarder hardware, see: ESP12_RFM95
As end node it works perfect. Next step is to use it as single channel packet forwarder conform de software of Maarten Westenberg (6.2.0). After a lot reading, configurating and testing I came to the conclusion that the forwarder runs (not tested with end nodes yet) but the www-server gives me a lot ascii text in the browser (see next image)