Date   

hb_bridge_all.py get ACLs

Cort N0MJS <n0mjs@...>
 

Today I added Access Control Lists (ACLs) to hb_bridge_all.py

This was in response to those with no desire to re-write TGID or TS, but who wanted some ability to limit how/what traffic is forwarded. This isn’t quite as simple as a “whitelist” and/or a “blacklist” like MMDVM, because it’s inherently multipoint, with greater than 1 possible target each direction. But it does include most of the simplicity of the whitelist/blacklist approach.

For example, let’s say you want an upstream connection to Brandmeister, but want to keep TGIDs, 1,2,17,3000, and 41109 just on your systems… not a problem. Let’s say you want to block particular subscribers or ranges on a certain system? Not a problem.

ACLs include:

Subscriber ID (SID)
Talkgroup ID (TGID)

There are global SID and TGID ACLs and per-system SID and TGID ACLs

FIRST MATCH EXITS

Evaluation:
GLOBAL first, SYSTEM second

ACLs are evaluated on ingress and egress BOTH.

Each ACL may be either “PERMIT” or “DENY”, and may contain multiple entires that are single IDs, (e.g. 3120101), ranges of IDs, (e.g. 1-3000), or a special identifier “ALL” that will match all valid IDs.


Cort Buffington
785-865-7206


Re: ASL - Analog - HB Bridge help please

Steve N4IRS
 

Michel,
In Analog_Bridge.ini you have this in the AMBE_Audio section:
gatewayDmrId = 2088012        ; ID to use when transmitting from Analog_Bridge
repeaterID = 2088012        ; ID of source repeater

gatewayDmrid is the ID that will display on the DMR radio when someone transmits from analog
repeaterID is the DMR ID of the repeater the signal is coming from.
Thay can not be the same. If you have a real DMR repeater ID, use it. Otherwise, add a 1 to your repeaterID so that it is 12088012

73, Steve N4IRS

On 02/13/2018 06:57 PM, F1TZO - Michel wrote:
Hi Steve and all

I write from France, so please, sorry for my English ;-)

So, I try to make working ASL <-> Analog_Bridge <-> HB_Bridge  to link Echolink with DMR.
I installed ASL in a VM and Analog_Brige + HB_Bridge in an other VM.
I have a Raspi with a DV3000U and AMBEserver running
And I have a MMDVM Hotspot connected on the HB_Bridge in DMR

After looking a lot the messages in the group, I made the configurations and the results are :
- MMDVM Hostspot is connected on HB_Bridge : OK
- ASL + HB_Bridge + Analog_bridge are started
- DMR to ASL : OK sound's good
- ASL to DMR : Nothing, no TX, no log in Analog_bridge
I don't see any error in the logs.

So .... I need help ;-) and when it'll work, I have to find how connect this to BM ....

Here are my config files in attach.

Thanks for your works and your help

Regards,

Michel - F1TZO




ASL - Analog - HB Bridge help please

F1TZO - Michel
 

Hi Steve and all

I write from France, so please, sorry for my English ;-)

So, I try to make working ASL <-> Analog_Bridge <-> HB_Bridge  to link Echolink with DMR.
I installed ASL in a VM and Analog_Brige + HB_Bridge in an other VM.
I have a Raspi with a DV3000U and AMBEserver running
And I have a MMDVM Hotspot connected on the HB_Bridge in DMR

After looking a lot the messages in the group, I made the configurations and the results are :
- MMDVM Hostspot is connected on HB_Bridge : OK
- ASL + HB_Bridge + Analog_bridge are started
- DMR to ASL : OK sound's good
- ASL to DMR : Nothing, no TX, no log in Analog_bridge
I don't see any error in the logs.

So .... I need help ;-) and when it'll work, I have to find how connect this to BM ....

Here are my config files in attach.

Thanks for your works and your help

Regards,

Michel - F1TZO


Re: Analog_Bridge to D-Star audio levels

Steve N4IRS
 

Mike,
A little history for you. Mike, N4IRR and I discovered the work Cort did on DMRLink a few years ago. We quickly realized that it could be leveraged to connect a c-Bridge to AllStarLink. We forked DMRlink and created DMRGateway. So as to not require any changes to AllStarLink, we decided to re-purpose the chan_usrp channel driver. We had a working DMR to AllStarLink gateway. Somewhere around that time, Cort invited us to work directly on DMRLink and later HBlink. When it came time to add the same capability to HBlink we decided to slightly modify the connectivity approach. Each "Network" would get a connectivity Partner. We had DMRlink (IPSC), HBlink (HB) and AllStarLink (analog) A new naming convention was in order. So we renamed DMRGateway to Analog_Bridge and added IPSC_Bridge and HB_Bridge.
As a side note, days after we renamed to Analog_Bridge, G4KLX released DMRGateway for use by MMDVMHost.

One of the things I was asked for a LOT was a replacement for the AllStarLink chan_dstar channel driver. We decided "why recreate the wheel?" We knew DummyRepeater and ircDDBGateway from G4KLX did everything we needed to connect to D-Star. It output and input analog audio. Why not just modify DummyRepeater to use analog audio in a format that AllStarLink could use? So, the modification to DummyRepeater does just that, it uses the USRP formatted PCM. A simple AllStarLink to D-Star bridge just uses DummyRepeater and AllStarLink. Analog_Bridge is not used in that configuration. Along the same lines a bridges to YSF and P25 are working now. The P25Bridge test is in daily use on BM TG 31665 and P25 TG 31665.

All of these things are built on the same premise that Cort defined, "We don't build networks, we build tools to build networks" All of these pieces are mix and match. Pick what you want to connect to and choose that partner. Nothing is built in a vacuum. Without the work of Cort, Jonathan and others, we would have nothing to connect to.

So yes, I think I know how Analog_Bridge is used.

73, Steve N4IRS      

On 2/13/2018 9:21 AM, Mike Swiatkowski via Groups.Io wrote:
Steve,It's used quite a bit more than you think.  You don't have to look that hard on google or Yahoo to find examples.  There is no easy way to go from DMR to D-Star so Analog_bridge is used.  I guess you could use XLX these days and maybe that's another option.


Re: Analog_Bridge to D-Star audio levels

Steven Blackford
 

Hey Mike,
   Just to follow up on using ThumbDV's with the XLXD software.  Like I told you in chat, I've setup a few of these now.  They work great & have been rock solid using the 1.1 version of the AMBED server software.  I've had lots of issues w/ dropouts on the 1.3 version.  I also modified the latency in the 1.1/1.3 versions to try to cut down on the issues.  That' makes all the difference in the world on the 1.1 version.  The default value is 4, drop it down to 1 & I haven't had any issues at all.  If you need more info about that, let me know.  I will say that as far as doing the DMR<->D-Star bridge either setup works.  Using the Analog_Bridge, HB_Bridge, Dummy Repeater is the most flexible way to go.  It allows you to changes things on the fly pretty quickly.  Twice a week normally I swap the "Carolina Link" from it's home on XLXD054B over to REF054C/REF061C for a couple of nets.  With the XLXD reflector I have setup, I can't do that, but I do have a full time interlink from the BM Network on that & it works great after making the changes noted above.   I've had better luck setting the XLXD transcoding system  on an X64 system also.    I know a few people running them on PI3's & have good luck.  The last one I helped setup, we even used a powered USB Hub & had issues w/ it being reliable.  Just my $0.02. :-)  Hope that helps.  73 de K4SQI.

Steve, K4SQI

On Tue, Feb 13, 2018 at 9:21 AM, Mike Swiatkowski via Groups.Io <mjswiatk@...> wrote:
Steve,It's used quite a bit more than you think.  You don't have to look that hard on google or Yahoo to find examples.  There is no easy way to go from DMR to D-Star so Analog_bridge is used.  I guess you could use XLX these days and maybe that's another option.




--
-----
Steve, kb7sqi@...


Re: Analog_Bridge to D-Star audio levels

Steven Blackford
 

Hey Mike,
    Hope things are going well.  What happened w/ the audio levels from when we initially setup your bridge?  I've setup various different bridges & the only time I've had to modify the audio levels was when going from ASL<->DMR.  That did take a while to get the audio level set.   Post your current Analog_Bridge.ini file & we can start then start modifying it to bring the levels to what you need.  You just need to do it in small increments & test it.  

As far as different AMBE devices goes, you can use the PIDV, ThumbDV for the DMR side of things and you can also use them for D-Star along w/ the original Blue DV-Dongle as well.  I use a PIDV and a DV-Dongle for my DStar<->DMR bridge.  PIDV's are great because you don't have the USB issues to deal with on PI's, but they're hard to come by these days.

  
73 de K4SQI.

Steve, K4SQI

On Sun, Feb 11, 2018 at 10:22 AM, Mike Swiatkowski via Groups.Io <mjswiatk@...> wrote:
Steve,
I noticed the source of my problem was setting AUDIO_UNITY on the ASL side in Analog_Bridge.ini.  Unity sounds better but the amplitude is probably 40% of what it needs to be.  Is there any way to bump up that level?  If I set AUDIO_USE_AGC I get the right drive level but the audio quality is a little less smooth.  I also experimented with AUDIO_USE_GAIN and that is about the same as with AGC interms of audio fidelity.

Question 2:  What  other AMBE interfaces can work with Analog_Bridge besides the ThumbDV from NW Digital?  I wonder if there is a better transcoder out there.

Mike, AA9VI




--
-----
Steve, kb7sqi@...


Re: Analog_Bridge to D-Star audio levels

Steve N4IRS
 

DMR to D-Star, yes you need Analog_Bridge
 D-Star to ASL Analog_Bridge is NOT used.

I think I know pretty well how Analog_Bridge, HB_Bridge, IPSC_Bridge are used.

73, Steve N4IRS

On 2/13/2018 9:21 AM, Mike Swiatkowski via Groups.Io wrote:
Steve,It's used quite a bit more than you think.  You don't have to look that hard on google or Yahoo to find examples.  There is no easy way to go from DMR to D-Star so Analog_bridge is used.  I guess you could use XLX these days and maybe that's another option.


Re: Analog_Bridge to D-Star audio levels

Mike, AA9VI
 

Steve,It's used quite a bit more than you think.  You don't have to look that hard on google or Yahoo to find examples.  There is no easy way to go from DMR to D-Star so Analog_bridge is used.  I guess you could use XLX these days and maybe that's another option.


Re: Transcoding between AMBE+ and AMBE+2

Steve, KB9MWR
 


Re: Analog_Bridge to D-Star audio levels

Steve N4IRS
 

Analog_Bridge is not used in that configuration. we can look at adding audio level controls to DummyRepeater


Re: Analog_Bridge to D-Star audio levels

Mike, AA9VI
 

Yes.


Re: Analog_Bridge to D-Star audio levels

Steve N4IRS
 

Mike,
Just to be clear, we are talking about DummyPrepeater to AllStarLink?

DummyRepeater <---> Allstarlink

Steve


On 02/11/2018 10:22 AM, Mike Swiatkowski via Groups.Io wrote:
Steve,
I noticed the source of my problem was setting AUDIO_UNITY on the ASL side in Analog_Bridge.ini.  Unity sounds better but the amplitude is probably 40% of what it needs to be.  Is there any way to bump up that level?  If I set AUDIO_USE_AGC I get the right drive level but the audio quality is a little less smooth.  I also experimented with AUDIO_USE_GAIN and that is about the same as with AGC interms of audio fidelity.

Question 2:  What  other AMBE interfaces can work with Analog_Bridge besides the ThumbDV from NW Digital?  I wonder if there is a better transcoder out there.

Mike, AA9VI


Re: Analog_Bridge to D-Star audio levels

Mike, AA9VI
 

Steve,
I noticed the source of my problem was setting AUDIO_UNITY on the ASL side in Analog_Bridge.ini.  Unity sounds better but the amplitude is probably 40% of what it needs to be.  Is there any way to bump up that level?  If I set AUDIO_USE_AGC I get the right drive level but the audio quality is a little less smooth.  I also experimented with AUDIO_USE_GAIN and that is about the same as with AGC interms of audio fidelity.

Question 2:  What  other AMBE interfaces can work with Analog_Bridge besides the ThumbDV from NW Digital?  I wonder if there is a better transcoder out there.

Mike, AA9VI


Analog_Bridge to D-Star audio levels

Mike, AA9VI
 

I am trying to increase the audio amplitude from Allstar to dummyrepeater using Analog_Bridge.  Besides Analog_Bridge.ini settings where can I do this?

Thanks,
Mike, AA9VI


Re: Transcoding between AMBE+ and AMBE+2

 

That is an option, but most parts are SMD and construction time is significant. 

I think you can buy as few as 10 pieces of the 3003 and pay before shipment. 

This whole project is to help the community, it is not a high volume or profit item.  (Building them in a professional assembly house and there are project costs.)

If there is not enough interest, it will simply not happen. (Orders will be refunded.)

Currently the order count is a few short but close. 

On Feb 7, 2018 14:00, "JJ Cummings" <cummingsj@...> wrote:
Here is a homebrew project that costs substantially less and has 3 channels:


The killer is the AMBE3003 chip, you have to order them in quantities of 90 from DVSI I have been told.  This would be much more economical thing to build or even have built I would think.

JJC 
N0PKT

On Wed, Feb 7, 2018 at 12:23 PM, John D Hays - K7VE <john@...> wrote:
I don't know if this group is aware of the 6 channel AMBE device build that is being planned, based on getting enough orders, see

http://nwdigitalradio.com/xcode-3006/



Re: Transcoding between AMBE+ and AMBE+2

JJ Cummings
 

Here is a homebrew project that costs substantially less and has 3 channels:


The killer is the AMBE3003 chip, you have to order them in quantities of 90 from DVSI I have been told.  This would be much more economical thing to build or even have built I would think.

JJC 
N0PKT

On Wed, Feb 7, 2018 at 12:23 PM, John D Hays - K7VE <john@...> wrote:
I don't know if this group is aware of the 6 channel AMBE device build that is being planned, based on getting enough orders, see

http://nwdigitalradio.com/xcode-3006/



Transcoding between AMBE+ and AMBE+2

 

I don't know if this group is aware of the 6 channel AMBE device build that is being planned, based on getting enough orders, see

http://nwdigitalradio.com/xcode-3006/


Re: hblink.py - CRITICAL UPDATE

Cort N0MJS <n0mjs@...>
 

After the reconnect, I don’t see a:

"Connection to Master Completed”

Implying we never actually get connected. The reason why is of interest, though I also need to look into why hblink.py hangs there and does not reset itself again. My guess is that I’m never checking to see if it actually completed and if not, resting it again. Something that’ll need added to the client maintenance loop.

That’s exactly the kind of info I needed to chase it down!


On Feb 7, 2018, at 5:41 AM, David <david@...> wrote:

Here is from the logs.  Looks like it restarts ok sometimes but not always

DEBUG 2018-02-06 18:50:40,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:50:40,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 19, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:50:45,244 (REPEATER-1) Client maintenance loop started
INFO 2018-02-06 18:50:45,245 (REPEATER-1) Sending login request to master 74.91.114.19:62031
DEBUG 2018-02-06 18:50:50,243 (REPEATER-1) Client maintenance loop started
INFO 2018-02-06 18:50:50,244 (REPEATER-1) Sending login request to master 74.91.114.19:62031
INFO 2018-02-06 18:50:50,267 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 758215133
INFO 2018-02-06 18:50:50,291 (REPEATER-1) Repeater Authentication Accepted
INFO 2018-02-06 18:50:50,292 (REPEATER-1) Repeater Configuration Sent
INFO 2018-02-06 18:50:50,322 (REPEATER-1) Repeater Configuration Accepted
INFO 2018-02-06 18:50:50,322 (REPEATER-1) Connection to Master Completed
DEBUG 2018-02-06 18:50:55,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:50:55,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 0, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:50:55,267 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1
DEBUG 2018-02-06 18:51:00,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:00,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 1, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:00,265 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 2
DEBUG 2018-02-06 18:51:05,244 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:05,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 2, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:05,265 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 3
DEBUG 2018-02-06 18:51:10,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:10,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 3, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:10,263 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 4
DEBUG 2018-02-06 18:51:15,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:15,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 4, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:15,264 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 5
DEBUG 2018-02-06 18:51:20,244 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:20,245 (REPEATER-1) RPTPING Sent to Master. Total Sent: 5, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:20,266 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 6
DEBUG 2018-02-06 18:51:25,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:25,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 6, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:25,266 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 7
DEBUG 2018-02-06 18:51:30,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:30,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 7, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:35,244 (REPEATER-1) Client maintenance loop started
INFO 2018-02-06 18:51:35,244 (REPEATER-1) Sending login request to master 74.91.114.19:62031
INFO 2018-02-06 18:51:35,266 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1635208484
INFO 2018-02-06 18:51:35,290 (REPEATER-1) Repeater Authentication Accepted
INFO 2018-02-06 18:51:35,291 (REPEATER-1) Repeater Configuration Sent
DEBUG 2018-02-06 18:51:40,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:45,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:50,243 (REPEATER-1) Client maintenance loop started


On Mon, Feb 5, 2018 at 8:47 AM, Cort N0MJS <n0mjs@...> wrote:
or if you’re using Git/Github:

"git checkout HB_Bridge”

to switch to that code locally.

On Feb 5, 2018, at 8:15 AM, Steve N4IRS <szingman@...> wrote:

https://github.com/n0mjs710/HBlink/tree/HB_Bridge

On 2/5/2018 8:49 AM, David wrote:
I do not remember where I found HB_Bridge the first time but I can not find the updated version.

On Fri, Feb 2, 2018 at 3:51 PM, Mike Zingman - N4IRR <mike.zingman@...> wrote:
HB_Bridge has taken up Cort's changes as well as updated any other component that has changed to date.



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206










Cort Buffington
785-865-7206


Re: hblink.py - CRITICAL UPDATE

David
 

Here is from the logs.  Looks like it restarts ok sometimes but not always

DEBUG 2018-02-06 18:50:40,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:50:40,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 19, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:50:45,244 (REPEATER-1) Client maintenance loop started
INFO 2018-02-06 18:50:45,245 (REPEATER-1) Sending login request to master 74.91.114.19:62031
DEBUG 2018-02-06 18:50:50,243 (REPEATER-1) Client maintenance loop started
INFO 2018-02-06 18:50:50,244 (REPEATER-1) Sending login request to master 74.91.114.19:62031
INFO 2018-02-06 18:50:50,267 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 758215133
INFO 2018-02-06 18:50:50,291 (REPEATER-1) Repeater Authentication Accepted
INFO 2018-02-06 18:50:50,292 (REPEATER-1) Repeater Configuration Sent
INFO 2018-02-06 18:50:50,322 (REPEATER-1) Repeater Configuration Accepted
INFO 2018-02-06 18:50:50,322 (REPEATER-1) Connection to Master Completed
DEBUG 2018-02-06 18:50:55,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:50:55,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 0, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:50:55,267 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1
DEBUG 2018-02-06 18:51:00,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:00,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 1, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:00,265 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 2
DEBUG 2018-02-06 18:51:05,244 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:05,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 2, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:05,265 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 3
DEBUG 2018-02-06 18:51:10,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:10,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 3, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:10,263 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 4
DEBUG 2018-02-06 18:51:15,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:15,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 4, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:15,264 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 5
DEBUG 2018-02-06 18:51:20,244 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:20,245 (REPEATER-1) RPTPING Sent to Master. Total Sent: 5, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:20,266 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 6
DEBUG 2018-02-06 18:51:25,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:25,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 6, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:25,266 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 7
DEBUG 2018-02-06 18:51:30,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:30,244 (REPEATER-1) RPTPING Sent to Master. Total Sent: 7, Total Missed: 0, Currently Outstanding: 0
DEBUG 2018-02-06 18:51:35,244 (REPEATER-1) Client maintenance loop started
INFO 2018-02-06 18:51:35,244 (REPEATER-1) Sending login request to master 74.91.114.19:62031
INFO 2018-02-06 18:51:35,266 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1635208484
INFO 2018-02-06 18:51:35,290 (REPEATER-1) Repeater Authentication Accepted
INFO 2018-02-06 18:51:35,291 (REPEATER-1) Repeater Configuration Sent
DEBUG 2018-02-06 18:51:40,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:45,243 (REPEATER-1) Client maintenance loop started
DEBUG 2018-02-06 18:51:50,243 (REPEATER-1) Client maintenance loop started


On Mon, Feb 5, 2018 at 8:47 AM, Cort N0MJS <n0mjs@...> wrote:
or if you’re using Git/Github:

"git checkout HB_Bridge”

to switch to that code locally.

On Feb 5, 2018, at 8:15 AM, Steve N4IRS <szingman@...> wrote:

https://github.com/n0mjs710/HBlink/tree/HB_Bridge

On 2/5/2018 8:49 AM, David wrote:
I do not remember where I found HB_Bridge the first time but I can not find the updated version.

On Fri, Feb 2, 2018 at 3:51 PM, Mike Zingman - N4IRR <mike.zingman@...> wrote:
HB_Bridge has taken up Cort's changes as well as updated any other component that has changed to date.



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206







Re: DMRmonitor broken?

David Andrzejewski KD8TWG
 

They’re definitely talking.


-- 

David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72


On Feb 7, 2018, at 04:30, Peter M0NWI <peter-martin@...> wrote:

David,


It's not something as simple as a networking issue is it?  The sender within DMRLink and receiver in DMRMonitor need to be able to connect over open sockets, just an idea?


I'm running a version from a few months ago, and it works OK for me.


73,

Peter



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of David Andrzejewski KD8TWG via Groups.Io <david@...>
Sent: 07 February 2018 05:08
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMRmonitor broken?
 
I know. But I really like it, so I’ll keep poking around. I’m not sure if the problem is in the DMRLink reporting server or dmrmonitor.

Thanks!

-- 

David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72


On Feb 7, 2018, at 00:04, Cort N0MJS <n0mjs@...> wrote:

DMRmonitor is not a supported application.

I don’t consider it part of DVSwitch. It’s just a repo of mine that still just a thought in progress


On Feb 6, 2018, at 8:54 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

I recently did a git pull on the dmrlink repo, and now DMRmonitor seems to be broken.  It's no longer showing calls, but the log down below is being updated.  I'm treading lightly here because I'm still learning the code, but from what I can tell, it's not receiving RCM messages from the reporting server.  I am probably wrong on that part, but it's my best educated guess.

Has something changed with regard to the reporting server portion and maybe DMRmonitor wasn't updated to support it?  I'm a professional Python developer and I'm happy to do the work if someone wants to point me in the right direction.

Also, is there a test harness for this, e.g. something that can construct and send packets, so I don't have to continually key up my repeater to test? ;)

Thanks!

9061 - 9080 of 9891