Date   

Re: Setting the IP address on the Pi

Steve N4IRS
 

Bob,
See the bottom of /etc/dhcpcd.conf

73, Steve N4IRS

On 11/3/20 10:22 PM, Bob Brown wrote:
Since the DVswitch draws a local IP from your network via DHCP, is there a way from the menu system to disable DHCP and hard code a Wired LAN IP ?

No, I am not doing wireless, just hardwire ethernet.

Short of doing this from the command line, can I open a config file and configure this and then reboot?

My system keeps drawing a 169.xxx.xxx.xxx address and an IPV6 address, my router is configured to hand out 10.20.20.xxx addresses, this pi refuses to go there.

I thought there would be a place in the menu system to set this but I cannot find it to save my soul, can someone please enlighten me?

Otherwise, I will do it via the cmd line.

I was following the nice videos from W0RMT, but it lacked what I think is an important part.

Thanks in advance

Bob, W0NQX





Re: Setting the IP address on the Pi

Bob Brown
 

Hi Jeff,

I would do that but the router is from google fiber and I have limited control of it.

I guess I will go to the CMD line method and set it that way.

Thanks for the reply.

Bob


Re: Setting the IP address on the Pi

Jeff Lehman, N8ACL
 

Set it via reserved IP in DHCP in your router by Mac address. That way when the pi boots, DHCP will always assign it that IP address and you don’t have to mess with changing files and the command line. Also if you ever need to move networks ( you get a new router and change your IP scope for example), your PI is not locked on that old network and you can’t get into it.

Jeff Lehman, N8ACL
E-mail: N8ACL@icloud.com
Hamshack Hotline: 4218
Website: https://n8acl.ddns.net

On Nov 3, 2020, at 10:22 PM, Bob Brown <bbrown@byrg.net> wrote:

Since the DVswitch draws a local IP from your network via DHCP, is there a way from the menu system to disable DHCP and hard code a Wired LAN IP ?

No, I am not doing wireless, just hardwire ethernet.

Short of doing this from the command line, can I open a config file and configure this and then reboot?

My system keeps drawing a 169.xxx.xxx.xxx address and an IPV6 address, my router is configured to hand out 10.20.20.xxx addresses, this pi refuses to go there.

I thought there would be a place in the menu system to set this but I cannot find it to save my soul, can someone please enlighten me?

Otherwise, I will do it via the cmd line.

I was following the nice videos from W0RMT, but it lacked what I think is an important part.

Thanks in advance

Bob, W0NQX






Setting the IP address on the Pi

Bob Brown
 

Since the DVswitch draws a local IP from your network via DHCP, is there a way from the menu system to disable DHCP and hard code a Wired LAN IP ?

No, I am not doing wireless, just hardwire ethernet.

Short of doing this from the command line, can I open a config file and configure this and then reboot?

My system keeps drawing a 169.xxx.xxx.xxx address and an IPV6 address, my router is configured to hand out 10.20.20.xxx addresses, this pi refuses to go there.

I thought there would be a place in the menu system to set this but I cannot find it to save my soul, can someone please enlighten me?

Otherwise, I will do it via the cmd line.

I was following the nice videos from W0RMT, but it lacked what I think is an important part.

Thanks in advance

Bob, W0NQX


Re: Where can I find protocol documentation?

Steve N4IRS
 

So read the python.

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of George <gmb2005@...>
Sent: Tuesday, November 3, 2020 4:44:41 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Where can I find protocol documentation?
 
Is that seriously as good as it gets??

Code is not documentation - and in my experience it is usually pretty unreadable anyway, being written in a crap language like C I expect.
I do not understand how people expect systems to be interoperable if the protocols used are not well documented - or is that why I so often hear about "weird problems" and things not quite working right?
Someone tried back in 2015, presumably when making a start. Shame it wasn't maintained unless I am just not finding it.

I am getting too old for this. When I started programming the ASCII text of the documentation would be bigger than the code itself!!

73 George M0GXB


Re: Where can I find protocol documentation?

George M0GXB
 

Is that seriously as good as it gets??

Code is not documentation - and in my experience it is usually pretty unreadable anyway, being written in a crap language like C I expect.
I do not understand how people expect systems to be interoperable if the protocols used are not well documented - or is that why I so often hear about "weird problems" and things not quite working right?
Someone tried back in 2015, presumably when making a start. Shame it wasn't maintained unless I am just not finding it.

I am getting too old for this. When I started programming the ASCII text of the documentation would be bigger than the code itself!!

73 George M0GXB


Re: #mmdvm_bridge #mmdvm_bridge

Mike Zingman - N4IRR
 

Looking at your logs, I see that the station transmitting with dmr2ysf is placing the users DMR ID in the callsign field.  I would bet that their dmr id database is not up to date so it is just sending the numeric ID.  YSF requires a callsign to be sent, not a numeric ID.


Re: DVSwitch Server release date

Steve N4IRS
 

Gary,
DVSwitch Server is all the same programs as you had on your bridge. The idea behind server was to include all the components and scripts. With the menu in Server you configure for use with DVSM, but it's not necessary.
The difference in using DVSwitch Server with DVSM and using DVSwitch Server with ASL is one setting in AB.ini

For DVSM:
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 54321                          ; Transmit USRP frames on this port
rxPort = 54321                          ; Listen for USRP frames on this port


For ASL:
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port

 
The above ports point to the USRP channel driver in ASL rpt.conf:
rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 127.0.0.1 = IP of the target application
                                        ; 34001 = UDP port the target application is listening on
                                        ; 32001 = UDP port ASL is listening on


I'll bet if you look at your AB.ini it's set for DVSM.

As to the ability to change TGs and modes from ASL. You can. It takes a little work in ASL but here are the basics:
/opt/MMDVM_Bridge/dvswitch.sh will allow you to change modes, talk groups and a whole lot more. It's VERY versatile. to get a look at what it can do:
/opt/MMDVM_Bridge/dvswitch.sh will output all or most of the available parameters.

/opt/MMDVM_Bridge/dvswitch.sh mode DMR will change modes to DMR
/opt/MMDVM_Bridge/dvswitch.sh tune 3100 will change TG to 3100

All you need to do is setup ASL. Well, doing that is not quite simple depending on how well you know ASL.
This part should really be continued in the <https://dvswitch.groups.io/g/allstarlink> subgroup.

Hope this helps,
73, Steve N4IRS
 

On 11/3/2020 3:18 PM, Gary wrote:
Installed DVSwitch_Server on new RPi4 and it works great. Fun to watch activity on RX Monitor and on Smartfone.
Have ASL 1.01 running on RPi3B+ for several years.Added DVSwitch bridge on it and it has been working FB.
However, w/o any way to change the TB over the air with DTMF, it is limited usefullness.
Thus, I took the leap and installed DVSwitch_Server on top of the existing stuff on the RPi3. Now DVSwitch does not work.
I shoud have asked B4 attempting the last step, but I got over enthusiastic.
Do you recommend putting ASL & DVSwitch Bridge & DVSwitch_Server on one RPi3B+? If so, what best install steps?
Thanks
Gary W5BI


Re: DVSwitch Server release date

Gary
 

Installed DVSwitch_Server on new RPi4 and it works great. Fun to watch activity on RX Monitor and on Smartfone.
Have ASL 1.01 running on RPi3B+ for several years.Added DVSwitch bridge on it and it has been working FB.
However, w/o any way to change the TB over the air with DTMF, it is limited usefullness.
Thus, I took the leap and installed DVSwitch_Server on top of the existing stuff on the RPi3. Now DVSwitch does not work.
I shoud have asked B4 attempting the last step, but I got over enthusiastic.
Do you recommend putting ASL & DVSwitch Bridge & DVSwitch_Server on one RPi3B+? If so, what best install steps?
Thanks
Gary W5BI


Re: Where can I find protocol documentation?

Steve N4IRS
 

George,
As far as I know, you have found all of the "documentation" on the protocol called HBP. MMDVM uses a slightly modified version of HBP to communicate with DMRGateway and networks like BM, XLX and DMR Plus. This is DMR only. To understand that protocol since it's open source, you can look at the source code for MMDVMHost, DMRGateway, HBlink and XLX.  You can also take a look at <https://github.com/marrold/MMDVM-Dissector>

For NXDN, D-Star, YSF and P25 see the source to MMDVMHost.

Hope this helps.
73, Steve N4IRS

On 11/3/2020 12:25 PM, George wrote:
For starters, I would like to find a full, complete, and correct documentation for whatever the protocol is called (IPSC, HBLINK, ??) that things like MMDVM use to talk to the gateways.

I found an old (2015) document somewhere which is clearly an early alpha version and with errors too, but the actual data streams I am looking at are for something that has evolved a bit since then. So where is this specified?

And is that protocol used for any other links in the growing DV networks?

George M0GXB


Where can I find protocol documentation?

George M0GXB
 

For starters, I would like to find a full, complete, and correct documentation for whatever the protocol is called (IPSC, HBLINK, ??) that things like MMDVM use to talk to the gateways.

I found an old (2015) document somewhere which is clearly an early alpha version and with errors too, but the actual data streams I am looking at are for something that has evolved a bit since then. So where is this specified?

And is that protocol used for any other links in the growing DV networks?

George M0GXB


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Yes i point each mbridge to her dmrid path. But i dont use analogue bridge her . Its only mbridge


Re: #mmdvm_bridge #mmdvm_bridge

k7wby@...
 

MMDMV_Briidge looks for DMRIds.dat and Analog_Bridge looks for subscriber_ids.csv. Since these are both static text files you need a copy for each instance in /var/lib. 
The initial install puts DMRIds.dat in /var/lib/mmdvm/ and susbscriber_ids.csv in var/lib/dvswitch/ You need a copy for each instance of MB and AB.
Something like /var/lib/dvswitch/ab1 and ab2 then /var/lib/mmdvm/mb1 & mb2. Move the .dat and .csv files into those directories for each instance and then change your AB and MB .ini files to point to the new locations. The update process uses the .ini files for the locations so the updates should still work according to plan.

I would chmod 0775 the new directories you created just to make sure they can be accessed. 


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

ok tonight i re update latest bin and now they work without crash but they have a issue with the id. look my mb1 and mb2 log with the id.my id is 3022260 but one of them missing the last digit, 3022260 -mb1 302226 so he w ont recognise the id as a callsign

mbridge 2
lM: 2020-11-03 03:58:11.006 YSF, Opening INI file: DVSwitch.ini
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] txPort -> 43500
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] rxPort -> 42500
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] txWidePort -> 43500
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] exportTG -> 1234
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] slot -> 2
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-11-03 03:58:11.006 YSF, Transmitting on 127.0.0.1:43500, and listening on port 42500.  Result = 1
M: 2020-11-03 03:58:11.006 MMDVM_Bridge-20201031_V1.6.0 is running
I: 2020-11-03 03:58:11.006 Started the DMR Id lookup reload thread
M: 2020-11-03 03:59:38.495 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 03:59:38.496 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 03:59:41.923 YSF, received network end of transmission, 3.5 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 03:59:51.552 YSF, received network data from VE2TBU     to *****H54DM at WIRESX    
I: 2020-11-03 03:59:51.552 YSF, Lookup call VE2TBU returned id 3022260 -> 3022260
M: 2020-11-03 03:59:55.856 YSF, received network end of transmission, 4.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 03:59:57.389 YSF, TX state = ON
I: 2020-11-03 03:59:57.389 YSF, Begin TX: src=3022260 rpt=0 dst=1234 slot=2 cc=0 metadata=VE2TBU
M: 2020-11-03 03:59:57.486 YSF, TX state = OFF
M: 2020-11-03 04:00:00.622 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 04:00:00.622 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 04:00:03.319 YSF, received network end of transmission, 2.8 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 04:01:36.737 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 04:01:36.737 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 04:01:40.462 YSF, received network end of transmission, 3.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 04:01:52.463 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 04:01:52.463 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 04:01:54.085 YSF, received network end of transmission, 1.7 seconds, 0% packet loss, BER: 0.0%
og
now mbridge 1
M: 2020-11-03 03:58:08.975 YSF, Opening INI file: DVSwitch.ini
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] txPort -> 42500
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] rxPort -> 43500
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] txWidePort -> 42500
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] exportTG -> 1234
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] slot -> 2
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-11-03 03:58:08.975 YSF, Transmitting on 127.0.0.1:42500, and listening on port 43500.  Result = 1
M: 2020-11-03 03:58:08.975 MMDVM_Bridge-20201031_V1.6.0 is running
I: 2020-11-03 03:58:08.975 Started the DMR Id lookup reload thread
M: 2020-11-03 03:59:38.496 YSF, TX state = ON
I: 2020-11-03 03:59:38.496 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 03:59:38.496 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 03:59:38.856 YSF, Narrow transmit (72 bit)
M: 2020-11-03 03:59:41.928 YSF, TX state = OFF
M: 2020-11-03 03:59:51.552 YSF, TX state = ON
I: 2020-11-03 03:59:51.552 YSF, Begin TX: src=3022260 rpt=0 dst=1234 slot=2 cc=0 metadata=VE2TBU
I: 2020-11-03 03:59:51.752 YSF, Narrow transmit (72 bit)
M: 2020-11-03 03:59:55.856 YSF, TX state = OFF
M: 2020-11-03 03:59:57.384 YSF, received network data from VE2TBU     to ALL        at F1ZJC     
I: 2020-11-03 03:59:57.384 YSF, Lookup call VE2TBU returned id 3022260 -> 3022260
M: 2020-11-03 03:59:57.481 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 04:00:00.622 YSF, TX state = ON
I: 2020-11-03 04:00:00.622 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 04:00:00.622 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 04:00:00.927 YSF, Narrow transmit (72 bit)
M: 2020-11-03 04:00:03.324 YSF, TX state = OFF
M: 2020-11-03 04:01:36.744 YSF, TX state = ON
I: 2020-11-03 04:01:36.744 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 04:01:36.744 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 04:01:37.041 YSF, Narrow transmit (72 bit)
M: 2020-11-03 04:01:40.467 YSF, TX state = OFF
M: 2020-11-03 04:01:52.463 YSF, TX state = ON
I: 2020-11-03 04:01:52.463 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 04:01:52.463 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 04:01:52.823 YSF, Narrow transmit (72 bit)
M: 2020-11-03 04:01:54.090 YSF, TX state = OFF


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Ok tonight i re downlaod the binary . Change my mmdvmbridge binary for the latest download. Now they work both way without crash but mb1 show the right dmrid associated to the right callsign but mb2 alway  show the id but missing the last digit of the dmr id so  its somewhere in the mbridge software


Re: Pi digital interface for Analog Radio (client)

Steve N4IRS
 

Still have this little issue:
The MMDVM software can look like a DMR repeater transmitter to a subscriber radio. The MMDVM software can look like a simplex signal (DMO) to a subscriber radio. What the MMDVM software can not do, is look like a subscriber radio to a DMR repeater. The same is true for traffic from a DMR repeater to the radio. The MMDVM software can not receive the output of a DMR repeater.

On 11/2/20 6:13 PM, Skyler Fennell wrote:
You could certainly do it with either Fusion or P25 with the remote gateway function enabled. 

I want to try it at some point ...

Radio less ASL node —> analog_bridge —> mmdvm_host P25/YSF REMOTE GATEWAY =1 —> ft-7800 9600 baud data port. 

Might be kinda a clunky mobile requiring a pi and a sound card and an extra speaker and mic   . 

So anyone, if I DO have a radio capable of Key/Unkey rapidly that would support tier II is there any hardware out there relatively easy to use to make a DMR client radio? 



On Mon, Nov 2, 2020 at 4:03 PM Jim Kusznir <jim@...> wrote:
Ok, thank you guys!

I figured there was a reason I didn't see someone making (overpriced) boxes that plugged into the data port of an analog radio to enable DMR...Even at $150, it would be a savings over buying a whole new radio.

--Jim


Re: Pi digital interface for Analog Radio (client)

Skyler Fennell
 

You could certainly do it with either Fusion or P25 with the remote gateway function enabled. 

I want to try it at some point ...

Radio less ASL node —> analog_bridge —> mmdvm_host P25/YSF REMOTE GATEWAY =1 —> ft-7800 9600 baud data port. 

Might be kinda a clunky mobile requiring a pi and a sound card and an extra speaker and mic   . 

So anyone, if I DO have a radio capable of Key/Unkey rapidly that would support tier II is there any hardware out there relatively easy to use to make a DMR client radio? 



On Mon, Nov 2, 2020 at 4:03 PM Jim Kusznir <jim@...> wrote:
Ok, thank you guys!

I figured there was a reason I didn't see someone making (overpriced) boxes that plugged into the data port of an analog radio to enable DMR...Even at $150, it would be a savings over buying a whole new radio.

--Jim


Re: Pi digital interface for Analog Radio (client)

Jim Kusznir
 

Ok, thank you guys!

I figured there was a reason I didn't see someone making (overpriced) boxes that plugged into the data port of an analog radio to enable DMR...Even at $150, it would be a savings over buying a whole new radio.

--Jim


Re: Compiling error on ./DVSwitch-System-Builder.sh

 

Got the problem ,  dvswitch-dashboard or  dvswitch-server would not install  because of a newer version of  libssl blocking lighttpd.

Here is what i did to fix it .

 SCREEN CAPTURE BEGINS

 root@vps275731:/tmp#apt-get install aptitude

root@vps275731:/tmp# aptitude  install lighttpd
The following NEW packages will be installed:
  libfam0{a} lighttpd
The following packages are RECOMMENDED but will NOT be installed:
  spawn-fcgi
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 311 kB of archives. After unpacking 1,041 kB will be used.
The following packages have unmet dependencies:
 libssl1.1 : Breaks: lighttpd (< 1.4.49-2) but 1.4.45-1 is to be installed
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     lighttpd [Not Installed]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Downgrade the following packages:
1)     libssl1.1 [1.1.1g-1+0~20200421.17+debian9~1.gbpf6902f (<NULL>, now) -> 1.1.0l-1~deb9u1 (oldstable)]

Accept this solution? [Y/n/q/?] Y
The following packages will be DOWNGRADED:
  libssl1.1

SCREEN CAPTURE CONTINUES AND ENDS WITH FINISHED INSTALLATION


After  that ,  dvswitch-server is installing perfectly ...

There might be a more elegant way to resolve that  but it worked .


THANKS AGAIN FOR  YOUR GREAT WORK ...

MUCH APPRECIATED


Richard VE2DJE




Le 2020-11-02 à 07:22, Steve N4IRS a écrit :

apt-get install dvswitch-dashboard

On 11/2/20 6:58 AM, Richard (Joseph) VE2DJE wrote:
Thanks. Dvswitch installed and services are all running ok.
Will work on Android / Pyuc to clear out my questions.
No luck on Dvswitch  Server
Will get back to you 
We already have apache2 running.
Where can I get Dvswitch Dashboard to try installing it on the VPS. ??

Richard

Le dim. 1 nov. 2020 6 h 17 p.m., Steve N4IRS <szingman@...> a écrit :
Richard,
I suggest you use DVSwitch Server

If you are starting from scratch:

as root:
wget http://dvswitch.org/buster
chmod +x buster
./buster

apt-get update
apt-get install dvswitch will install analog-bridge, md380-emu, mmdvm-bridge, nxdngateway, nxdnparrot, p25gateway, p25parrot, ysfgateway, ysfparrot, ircddbgateway, quantar-bridge 

apt-get install dvswitch-server will install all of the above plus the menu and the dashboard.

If you want to continue from where you are:
edit /etc/apt/sources.list.d/dvswitch.list
change stretch to buster.
apt-get update
install from above.



On 11/1/20 5:50 PM, Richard (Joseph) VE2DJE wrote:

Running  Debian Stretch on  OVH VPS .   Asterisk is loaded  but was  stopped during compiling  ...


Got this error during compiling of the latest version



c++ -g -O3 -Wall -std=c++0x -pthread -c -o UDPSocket.o UDPSocket.cpp
UDPSocket.cpp: In member function ‘int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&)’:
UDPSocket.cpp:294:50: error: ‘LogMessage’ was not declared in this scope
    LogMessage("Re-opening UDP port on %u", m_port);
                                                                                                ^
Makefile:15: recipe for target 'UDPSocket.o' failed
make: *** [UDPSocket.o] Error 1..

root@vps275731:/srv/DVSwitch-System-Builder#





 I am  out of clue  >>>


Richard VE2DJE




Virus-free. www.avg.com


Re: #mmdvm_bridge #mmdvm_bridge

k7wby@...
 

O.K. That explains the problem better but leaves me without an answer. I have some suspicions and I have a hot spot that I can play and packet analyzer software so if you don't get it resolved let me know and I'll dig in to it.

Steve/K7WBY 

2561 - 2580 of 9925