Date
1 - 4 of 4
DMR Timeout/Beaconing #brandmeister #mmdvm_bridge
|
mi0pyn@...
Hi all,
I have a question about the DMR Network side of MMDVM_Bridge. On a test system I have running, connecting to the BM UK Master on the DMR side, I have an issue where the Master connection is dropped every 120 seconds exactly: M: 2019-04-25 17:51:14.327 DMR, Logged into the master successfullyBefore I start bugging the Master sysop, is there some heartbeat or beaconing that can/needs to be put in place to keep the connection alive? The time is exactly what I'd expect to see if there was a TCP timeout somewhere, but tracing that is likely to be very time consuming so I was wondering whether there was some way of enabling a heartbeat every 60 seconds or so. 73 Stefan MI0PYN |
|
|
|
Stefan, There is already a keepalive function built into MMDVM_Bridge, that's how it knows whether or not the connection has been lost or not. Looking at your logs, I see duplication of lines which suggests that you may be running MB in two instances. If that's the case, make sure that the two instances are using separate sets of ports assigned to the program. If you're intending to run one instance of MB, then check to make sure that you don't have any other instances of it running before you start it. Steve KC1AWV On Thu, Apr 25, 2019, 2:04 PM <mi0pyn@...> wrote: Hi all, |
|
|
|
mi0pyn@...
Thanks for the response Steve.
It turns outthere were in fact 2 instances running, I didn't realise that the daemonised service was enabled by default and I was testing with an instance running inthe foreground. Thanks for the help. |
|
|
|
Glad to be of service to you! On Sat, Apr 27, 2019, 6:25 PM <mi0pyn@...> wrote: Thanks for the response Steve. |
|
|