Date
21 - 40 of 43
#mmdvm_bridge #mmdvm_bridge
swinger72@...
mbridge2.ini
[General] Callsign=va2tb Id=302252804 Timeout=180 Duplex=0 [Info] RXFrequency=000000000 TXFrequency=000000000 Power=1 Latitude=41.7333 Longitude=-50.3999 Height=0 Location= Description=MMDVM_Bridge URL=https: [Log] # Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal DisplayLevel=1 FileLevel=2 FilePath=/var/log/MMDVM_Bridge2 FileRoot=MMDVM_Bridge [DMR Id Lookup] File=/opt/DMRIds.dat Time=24 [NXDN Id Lookup] File=/var/lib/mmdvm/NXDN.csv Time=24 [Modem] Port=/dev/null RSSIMappingFile=/dev/null Trace=0 Debug=0 [D-Star] Enable=0 Module=B [DMR] Enable=0 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [System Fusion] Enable=1 [P25] Enable=0 NAC=293 [NXDN] Enable=0 RAN=1 Id=12345 [D-Star Network] Enable=0 GatewayAddress=127.0.0.1 GatewayPort=20010 LocalPort=20011 Debug=0 [DMR Network] Enable=0 Address=hblink.dvswitch.org Port=62031 Jitter=360 Local=62032 Password=passw0rd # for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md # for XLX the syntax is: Options=XLX:4009 # Options= Slot1=0 Slot2=1 Debug=0 [System Fusion Network] Enable=1 LocalAddress=0 LocalPort=3200 GatewayAddress=127.0.0.1 GatewayPort=42000 Debug=1 [P25 Network] Enable=0 GatewayAddress=127.0.0.1 GatewayPort=42020 LocalPort=32010 Debug=0 [NXDN Network] Enable=0 #LocalAddress=127.0.0.1 Debug=0 LocalPort=14021 GatewayAddress=127.0.0.1 GatewayPort=14020 Dvswitch ; MMDVM_Bridge export / import configuration file. ; This file should be placed along side of MMDVM_Bridge or you can supply ; an absolute path in the DVSWITCH environment variable, e.g: ; DVSWITCH=/etc/MMDVM_Bridge/DVSwitch.ini ; before executing MMDVM_Bridge ; ; Another method to set the enviorment variable is to use the systemd unit file ; by adding: ; Environment=DVSWITCH=/etc/MMDVM_Bridge/DVSwitch.ini ; to /lib/systemd/system/mmdvm_bridge.service ; Configure the Quantar Repeater Partner ; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge [QUANTAR] address = 0.0.0.0 ; Address to send IMBE TLV frames to (export) txPort = 34103 ; Port to send IMBE TLV frames to (export) rxPort = 34100 ; Port to listen for IMBE TLV frames on (import) quantarPort = 1994 ; HDLC frames To/From the Quantar repeater debug = 0 ; Debug 0 = off, 1 = on (adds lots of additional messages) logLevel = 2 ; Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal logFilePath = /var/log/dvswitch/Quantar_Bridge.log ; Configure the DMR Partner ; Audio format is AMBE 72 bit [DMR] address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) txPort = 31100 ; Port to send AMBE TLV frames to (export) rxPort = 31103 ; Port to listen on (import) slot = 2 ; Export slot exportTG = 0 ; Which TG to export hangTimerInFrames = 0 ; Use 50 for 3 seconds of hang time (3000 / 60) talkerAlias = %callsign %location %description ; Get callsign location and description from MMDVM_Bridge.ini ; Configure the D-Star Partner ; Audio format is AMBE 48 bit (DSAMBE) [DSTAR] address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) txPort = 32100 ; Port to send AMBE TLV frames to (export) rxPort = 32103 ; Port to listen on (import) fallbackID = 1234567 ; In case we can not find a valid DMR id in the database, export this one exportTG = 9 ; Which TG to export slot = 2 ; Export slot RemotePort = 54321 ; Port to send Gateway commands to message = %location %description ; Get location and description from MMDVM_Bridge.ini ; Configure the NXDN Partner ; Audio format is AMBE 72 bit [NXDN] address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) txPort = 33100 ; Port to send AMBE TLV frames to (export) rxPort = 33103 ; Port to listen on (import) fallbackID = 1234567 ; In case we can not find a valid DMR id in the database, export this one nxdnFallbackID = 12345 ; Use this ID when the input DMR ID is not found in the database translate = 1234=4321 ; Translate NXDN TG < -- > DMR TG (bidirectional) slot = 2 ; Export slot RemotePort = 6075 ; Port to send Gateway commands to ; Configure the P25 Partner ; Audio format is IMBE 88 bit [P25] address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) txPort = 34100 ; Port to send AMBE TLV frames to (export) rxPort = 34103 ; Port to listen on (import) slot = 2 ; Export slot RemotePort = 6074 ; Port to send Gateway commands to ; Configure the Yaesu Fusion Partner ; Audio format is AMBE 72 bit ; Audio format is IMBE 88 bit [YSF] address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) txPort = 43500 ; Port to send AMBE TLV frames to (export) rxPort = 42500 ; Port to listen on (import) txWidePort = 43500 ; Port to send IMBE TLV frames to for YSFw (export) fallbackID = 1234567 ; In case we can not find a valid DMR id in the database, export this one exportTG = 1234 ; Which TG to export slot = 2 ; Export slot RemotePort = 6073 ; Port to send Gateway commands to
|
|
Are you using YSFGateway with mbridge2? I see this:
toggle quoted messageShow quoted text
[System Fusion Network] Enable=1 LocalAddress=0 LocalPort=3200 GatewayAddress=127.0.0.1 GatewayPort=42000 Debug=1
On 10/30/2020 2:03 PM,
swinger72@... wrote:
mbridge2.ini
|
|
swinger72@...
No im running in the same server as my ysfreflector
|
|
|
|
swinger72@...
i point each mbridge directly to the ysfreflector ip .mb2 is local in the same server .my question is it is possible that is because i do not pass by ysfgateway? I have been working this way for 1 year now
|
|
You do not need YSFGateway. Are you saying this has been working
over a year with ysf2dmr clients?
toggle quoted messageShow quoted text
On 10/30/20 4:21 PM,
swinger72@... wrote:
i point each mbridge directly to the ysfreflector ip .mb2 is local in the same server .my question is it is possible that is because i do not pass by ysfgateway? I have been working this way for 1 year now
|
|
swinger72@...
Yes but recently mooved the ysfreflector on datacenter. The reason why now we seen this is issue is because about 2 weeks ago i just close my bridge with brandmeister and all of this users now pass by the dmr2ysf to reach my network
|
|
swinger72@...
i just tried again on the old server and its caused the same problem
|
|
k7wby@...
You have two instances of MB created in two separate folders. Did you disable the original mmdvm_bridge service and create the two new ones that are needed for the two separate bridges?
|
|
swinger72@...
Yes . I stop everything disable them and built my .ini
I already try to change rebuilt purge reinstall update bimary try many other port . With the same issue.
|
|
swinger72@...
I create new .service for each mb .mb1 and mb2 differenf path .in and .ini2
|
|
Maybe i can try to change the in each mb path to start ex mmdvmbridge1 and 2
|
|
swinger72@...
in another way i have a nxdn reflector.he is linked to my ysfreflector and when i use my openspot2 nxdn to ysf they work flawlesly and no crash from mb1 or mb2
|
|
Ok, I have some idea of what you're trying to accomplish. Sorry if some of this is redundant but others may want to understand:
Here's my take: Install DVSwitch from the repository to /opt/ which creates /opt/Analog_Bridge /opt/md380-emu /opt/MMDVM_Bridge create two new folders in /opt/ /opt/mb1 opt/mb2 copy the entire contents of MMDVM_Bridge to mb1 and mb2 delete /opt/MMDVM_Bridge disable mmdvm_bridge.service create two new services in /etc/systemd/system based on the original service /etc/systemd/system/multi-user.target.wants/mmdvm_bridge.service change each of the new .service's so they point to the new locations (/opt/mb1 and /opt/mb2). For instance, the following would be the service definition for the first MB instance I called MB1 [Unit]
Description=MMDVM_Bridge MB1 Service
# Description=Place this file in /lib/systemd/system
# Description=N4IRS 04/20/2018
# The device name should point to the
# port the mmdvm is plugged into.
# For USB ports (Arduino Due)
# BindTo=dev-ttyACM0.device
#
# To make the network-online.target available
# systemctl enable systemd-networkd-wait-online.service
After=network-online.target syslog.target netcheck.service
Wants=network-online.target
[Service]
StandardOutput=null
WorkingDirectory=/opt/MMDVM_Bridge (Change to /opt/MB1)
Environment=DVSwitch=/opt/MB1/DVSwitch.ini (Change to /opt/MB1)
RestartSec=3
ExecStart=/opt/MB1/MMDVM_Bridge /opt/MB1/MMDVM_Bridge.ini (Change to /opt/MB1)
Restart=on-abort
[Install]
WantedBy=multi-user.target
Modifiy the second mb service to point to the /opt/mb2/ Now go to /opt/mb2/DVSwitch.ini and modify it to point to a different set of ports than /opt/mb1/DVSwitch.ini. /opt/mb1/DVSwitch.ini can remain as is. If you don't do this you will likely get a "Cannot open port" error when you start the mb2 service and mb2 will fail. Finally: systemctl enable mb1 systemctl start mb1 systemctl status mb1 if it's running then: systemctl enable mb2 systemctl start mb2 systemctl status mb2 If both of your services start successfully then the problem is no longer with MB and I would look at the ports that are defined in DVSwitch and MB. We can go there next if this doesn't solve your issue. K7WBY/Steve
|
|
Didn't see this error before sorry, I really need to be more attentive:
Segmentation fault (core dumped) Caused by trying to write to the same log file from two different instances of mmdvm_bridge. Fix: mkdir /var/lib/mmdvm/mb1 mkdir /var/lib/mmdvm/mb2 mkdir /var/lib/dvswitch/dvs1 mkdir /var/lib/dvswitch/dvs2 Change the log file locations in both of your new MMDVM_Bridge.ini and DVSwitch.ini files to point to the new locations Also make sure that your new DMRIds.dat file locations are correct in your MMDVM_Bridge.ini files or you they won't get updated.
|
|
swinger72@...
Hi Steve. All set this way. Different path for .ini and log. The system work well its not a issue to start and run mb1 and mb2. I runnning it in ysf without any issue and no crash in mb1 or2 if i only use fusion ysf . This issue appear when a user use hotspot with dmr2ysf . A the moment they it the ptt in dmr2ysf now see the mb crash but for other use its ok like nxdn2ysf working good ysf2ysf reflector working good . Its only with dmr2ysf users . I double check my dvs and mb and all seem ok . Only in the dvs log i see for the log the path is for the quantar but i dont no if i only use ysf part if he needed to have the log path. I will try later in case of .... thank s again
|
|
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
|
|
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
|
|
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
|
|
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.
|
|