Re: looking at my options
Mike,
toggle quoted messageShow quoted text
I guess you are sawing the issue is GW2? without GW1 running GW2 can not connect?
On 2/28/2019 11:33 AM, Mike AE4ML
wrote:
REF 1 -- GW 1
|
|
Re: LAN address as FQDN in P25Hosts.txt?
OK, just for the heck of it so I can wrap my head around the
problem. Add a entry in the /etc/hosts file for 192.168.3.130 Put
the fqdn in P25Hosts.ini and retest.
toggle quoted messageShow quoted text
Are you getting this" (97.125.17.237:42010) from the reflector log or from something else? I know of no reason that 192.168.3.130 should not work. Steve
On 2/28/2019 10:17 AM,
harden.ray@... wrote:
P25Reflector<->P25Gateway<->AnalogBridgeP25<->AnalogBridgeDMR<->MMSVMHost <-> Brandmeister
|
|
Re: looking at my options
REF 1 -- GW 1
REF2 -- GW 2 RPTR 1 -- REF 1 RPTR 2 -- REF 2 shutdown GW 1 REF -1 drops 127.0.0.1 connection RPTR 1 changed to REF 2 and will not connect started GW 1 REF 1 adds 127.0.0.1 shutdown GW 2 REF 2 drops 127.0.0.1 RPTR 1 changed to REF 1 and connects RPTR 2 changed to REF 1 and connects Problem GW 2
|
|
Re: LAN address as FQDN in P25Hosts.txt?
JJ Cummings
hosts file - an entry for whatever hostname to IP mapping that you want..
On Thu, Feb 28, 2019 at 9:03 AM <harden.ray@...> wrote: P25Reflector<->P25Gateway<->AnalogBridgeP25<->AnalogBridgeDMR<->MMSVMHost <-> Brandmeister
|
|
Re: looking at my options
I think the issue is at the Gateway not the Reflector.
toggle quoted messageShow quoted text
Shutdown one gateway and test connect to each Reflector Then shutdown first Gateway and test connect to each Reflector If that works, we can trouble shoot 2 Gateways on the same machine.
On 2/28/2019 10:48 AM, Mike AE4ML
wrote:
Steve,
|
|
LAN address as FQDN in P25Hosts.txt?
Ray Harden
P25Reflector<->P25Gateway<->AnalogBridgeP25<->AnalogBridgeDMR<->MMSVMHost <-> Brandmeister
I am close to finishing testing of "This Beast", software is working. The P25 <=> DMR equipment is physically located in my lab in the same local area net- MMDVM-P25 Moto MSF5000 -- RPi -- TYT 2017-DMR Substituting in P25Hosts.txt the LAN address 192.168.3.130 for the FDQN results in an erroneous IP address at the time to PTT on the P25 radio === (97.125.17.237:42010) instead of the intended 192.168.3.130 as coded in P25Hosts.txt (attached). (see attached P25Reflector.log) Is it possible to use a LAN address as the FQDN in P25Hosts.txt? For example: 31900 (tab) 192.168.3.130 (tab) 41000 instead of: 31900 (tab) dvsw.org (tab) 41000 The DVSWITCH software is running at address 192.168.3.4 so it seems the LAN should support what I am tying to do. Eventually I will provide the P25Hosts 31900 entry with a proper FQDN. Thanks to all support this effort.
|
|
Re: looking at my options
Steve,
They are definitely up root@ip-172-31-19-69:/opt/310749/P25Reflector# netstat -unap | grep -e "P25Gateway" -e "P25Reflector" udp 0 0 0.0.0.0:42010 0.0.0.0:* 6280/P25Gateway udp 0 0 0.0.0.0:42020 0.0.0.0:* 6280/P25Gateway udp 0 0 0.0.0.0:41000 0.0.0.0:* 1564/P25Reflector udp 0 0 0.0.0.0:41010 0.0.0.0:* 23972/P25Reflector udp 0 0 0.0.0.0:42110 0.0.0.0:* 23911/P25Gateway udp 0 0 0.0.0.0:42120 0.0.0.0:* 23911/P25Gateway This is what I see on the one repeater that isn't connecting I: 2019-02-28 14:22:14.286 Opening P25 network connection I: 2019-02-28 14:22:14.286 Opening P25 network connection I: 2019-02-28 14:22:15.241 Loaded 13 P25 reflectors I: 2019-02-28 14:22:15.688 Loaded 126125 Ids to the callsign lookup table M: 2019-02-28 14:22:15.689 Starting P25Gateway-20180409 I: 2019-02-28 14:22:15.689 Started the DMR Id lookup reload thread M: 2019-02-28 14:22:15.689 Linked at startup to reflector 10283 W: 2019-02-28 14:24:15.711 No response from 10283, unlinking I: 2019-02-28 15:22:20.431 Loaded 13 P25 reflectors ! /var/log/syslog Feb 28 09:22:14 147030_Madison systemd[1]: Stopping P25Gateway Service... Feb 28 09:22:14 147030_Madison systemd[1]: Stopped P25Gateway Service. Feb 28 09:22:14 147030_Madison systemd[1]: Started P25Gateway Service. if I switch this repeater over to the first reflector it links right up I have looked at the setup , open udp ports. I've looked at the logs including syslog. I'm stumped at the moment. 10283 Reflector 310749 P25_Ref <-> P25Gtw <-> MMDVM_Br <-> An_Br_P25 <-> An_Br_DMR <-> MMDVM_Br <-> BrandMeister P25 DMR 41010 --> 41010 32110 --> 32110 34203 --> 34203 34101 --> 34101 31200 --> 31200 62132 --> 62132 42110 <-- 42110 42120 <-- 42120 34200 <-- 34200 32101 <-- 32101 31203 <-- 31203 62131 <-- 62131 DMR P25 31200 34203 31203 34200
|
|
Re: looking at my options
Mike I run 3 P25 reflectors on dvswitch.org:
toggle quoted messageShow quoted text
[General] Daemon=0 [Id Lookup] Name=/var/lib/mmdvm/DMRIds.dat Time=24 [Log] # Logging levels, 0=No logging DisplayLevel=1 FileLevel=1 FilePath=/var/log/P25Reflector FileRoot=P25_DVSwitch_Reflector [Network] Port=43166 Debug=0 ############################################# [General] Daemon=0 [Id Lookup] Name=/var/lib/mmdvm/DMRIds.dat Time=24 [Log] # Logging levels, 0=No logging DisplayLevel=1 FileLevel=1 FilePath=/var/log/P25Reflector FileRoot=P25_NA_Reflector [Network] Port=41000 Debug=0 ################################################# [General] Daemon=0 [Id Lookup] Name=/var/lib/mmdvm/DMRIds.dat Time=24 [Log] # Logging levels, 0=No logging DisplayLevel=1 FileLevel=1 FilePath=/var/log/P25Reflector FileRoot=P25_TAC1_Reflector [Network] Port=41010 Debug=0
On 2/28/2019 9:59 AM, Mike AE4ML wrote:
Steve,
|
|
Re: looking at my options
Steve,
I started building on the centralized reflector(s) The first reflector was no problem. Its up and working. The second reflector nothing can connect to it. I see in the logs of the repeater that it is connecting to reflector 2 (102x3) but then it times out. I have noticed that once a device fails connection to a reflector that there are no further retries. I have to do a restart on P25gateway to reattempt. I can't find anything in the Docs files as to the port 42010. I found this first layout in documentation. 102x2 Reflector 310xx7 P25_Ref <-> P25Gtw <-> MMDVM_Br <-> An_Br_P25 <-> An_Br_DMR <-> MMDVM_Br <-> BrandMeister P25 41000 --> 41000 32010 --> 32010 34103 --> 34103 34001 --> 34001 31100 --> 31100 62032 --> 62032 42010 <-- 42010 42020 <-- 42020 34100 <-- 34100 32001 <-- 32001 31103 <-- 31103 62031 <-- 62031 DMR 31100 31103 102x3 Reflector 310xx9 P25_Ref <-> P25Gtw <-> MMDVM_Br <-> An_Br_P25 <-> An_Br_DMR <-> MMDVM_Br <-> BrandMeister P25 DMR 41010 --> 41010 32110 --> 32110 34203 --> 34203 34101 --> 34101 31200 --> 31200 62132 --> 62132 XXXXX <-- XXXXX 42120 <-- 42120 34200 <-- 34200 32101 <-- 32101 31203 <-- 31203 62131 <-- 62131 DMR P25 31200 34203 31203 34200
|
|
Re: BrandMeister to XLX
Not a problem, Lito. Good idea on the firewall ports, but by default Debian 9 comes with the firewall wide open. I think this is the same story for Raspbian. Since there's many firewalls (iptables, ufw, firewalld, etc) it would be difficult to write out the config in the doc but I can add in a "gotcha" line to remind people.
On Wed, Feb 27, 2019 at 3:58 PM Lito - WI6Y <Tolitski@...> wrote: Ok.. It looks like I got it running. At first I was wondering if I needed to set the firewall ports for these two ports as soon as I added these to the rules.v4 file, data started flowing. --
Steve Miller KC1AWV
|
|
Re: BrandMeister to XLX
Lito - WI6Y
Ok.. It looks like I got it running. At first I was wondering if I needed to set the firewall ports for these two ports as soon as I added these to the rules.v4 file, data started flowing.
Now, I need to define the same for the XLX port in DMRGateway. Steve (AWV), The document is wonderful. I think you should make note of the firewall ports in the file. I am using iptables. Thanks for the help guys!, 73, Lito
|
|
Re: BrandMeister to XLX
Lito et al.:
Here's a ruff draft of the BM to XLX via MMDVM_Bridge (DVSwitch distribution) on Debian 9. Assumptions made that you're using a Debian 9 box, and installed the DVSwitch apps via the DVSwitch-System-Builder scripts. https://docs.google.com/document/d/1n17cx_9elLJoMmcQWM0_XOm2dicKdIC6ar_0S16904A/edit?usp=sharing
|
|
Re: BrandMeister to XLX
No, I misread the message. it looks right.
toggle quoted messageShow quoted text
On 2/27/2019 2:39 PM, Lito - WI6Y
wrote:
When I run the MMBridgeBM I get this:
|
|
Re: BrandMeister to XLX
Lito - WI6Y
Hi Steve (IRS),
I was under the impression that:
bridge1 tx 35100<-->
bridge2 rx
bridge1 rx
35103<--> bridge2 tx
Is this what I am doing
wrong?
Thank you
Lito
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Wednesday, February 27, 2019 11:35 AM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] BrandMeister to XLX You can NOT use the same port pairs for both instances of MMDVM_Bridge.
On 2/27/2019 2:24 PM, Lito - WI6Y wrote:
Thank you Steve,
|
|
Re: BrandMeister to XLX
You can NOT use the same port pairs for both instances of
MMDVM_Bridge.
toggle quoted messageShow quoted text
On 2/27/2019 2:24 PM, Lito - WI6Y
wrote:
Thank you Steve,
|
|
Re: BrandMeister to XLX
Lito - WI6Y
Thank you Steve,
I found a configuration error and turned off the YSF in the BM side. When I do netstat this is what I get root@localhost:/etc# netstat -lntu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 xx.xx.xx.xx:10001 0.0.0.0:*
udp 0 0 xx.xx.xx.x:10002 0.0.0.0:*
udp 0 0 0.0.0.0:35100 0.0.0.0:*
udp 0 0 0.0.0.0:35103 0.0.0.0:*
udp 0 0 xx.xx.xx.xx:30001 0.0.0.0:*
udp 0 0 xx.xx.xx.xx:30051 0.0.0.0:*
udp 0 0 0.0.0.0:42860 0.0.0.0:*
udp 0 0 xx.xx.xx.xx:10100 0.0.0.0:*
udp 0 0 0.0.0.0:42000 0.0.0.0:*
udp 0 0 0.0.0.0:42002 0.0.0.0:*
udp 0 0 127.0.0.1:42013 0.0.0.0:*
udp 0 0 127.0.0.1:42015 0.0.0.0:*
udp 0 0 xx.xx.xx.xx:20001 0.0.0.0:*
udp 0 0 xx.xx.xx.xx:62030 0.0.0.0:*
udp 0 0 0.0.0.0:62032 0.0.0.0:*
udp 0 0 0.0.0.0:62033 0.0.0.0:*
udp 0 0 0.0.0.0:62035 0.0.0.0:*
The highlighted ports are not present when the program is not running. When I run the MMBridgeBM I get this: M: 2019-02-27 19:14:56.123 DMR, Opening INI file: DVSwitch.ini
M: 2019-02-27 19:14:56.123 DMR, Setting [DMR] TXPort -> 35100
M: 2019-02-27 19:14:56.123 DMR, Setting [DMR] RXPort -> 35103
M: 2019-02-27 19:14:56.123 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-02-27 19:14:56.123 DMR, Setting [DMR] Slot -> 2
M: 2019-02-27 19:14:56.123 DMR, Transmitting on 127.0.0.1:35100 and listening on port 35103. Result = 1
M: 2019-02-27 19:14:56.123 MMDVM_Bridge-20180423 is running
and on the XLX side M: 2019-02-27 19:17:02.028 DMR, Opening INI file: DVSwitch.ini
M: 2019-02-27 19:17:02.028 DMR, Setting [DMR] RXPort -> 35100
M: 2019-02-27 19:17:02.028 DMR, Setting [DMR] TXPort -> 35103
M: 2019-02-27 19:17:02.028 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-02-27 19:17:02.028 DMR, Setting [DMR] Slot -> 2
M: 2019-02-27 19:17:02.028 DMR, Transmitting on 127.0.0.1:35103 and listening on port 35100. Result = 1
I think the config is right but data is not flowing.. I wonder if there are other diagnostic messages that I am not seeing. 73, Lito
|
|
Re: BrandMeister to XLX
Lito, I just realized that what you say is the BM side looks like it's actually running the XLX side. Check the logs: I: 2019-02-27 17:26:30.656 Description: "MMBr2XLX" So... it looks like what was loaded from /opt/MMBr2BM5153 actually loaded settings for XLX?
On Wed, Feb 27, 2019 at 1:33 PM Steve KC1AWV <smiller@...> wrote:
--
Steve Miller KC1AWV
|
|
Re: BrandMeister to XLX
Lito, I don't see anything from MMDVM_Bridge on the XLX side. The MMDVM_Bridge on the BM side is using ports that are transposed from the posted DVSwitch.ini, check the log: M: 2019-02-27 17:26:30.790 DMR, Opening INI file: DVSwitch.ini M: 2019-02-27 17:26:30.790 DMR, Setting [DMR] RXPort -> 35100 M: 2019-02-27 17:26:30.790 DMR, Setting [DMR] TXPort -> 35103 M: 2019-02-27 17:26:30.791 DMR, Setting [DMR] Address -> 127.0.0.1 Posted DVSwitch.ini (For BM Side): [DMR] TXPort = 35100 ; Port to send AMBE TLV frames to (export) RXPort = 35103 ; Port to listen on (import) Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) Also, you're dropping off of Master 3103: E: 2019-02-27 17:28:02.549 DMR, Master is closing down M: 2019-02-27 17:28:02.549 DMR, Closing DMR Network M: 2019-02-27 17:28:02.549 DMR, Opening DMR Network E: 2019-02-27 17:29:12.564 DMR, Connection to the master has timed out, retrying connection Check for port conflicts, or processes running in the background that may be already using the ports. Make sure that you're running the two MMDVM_Bridge instances from separate working directories, else both instances will read the same copy of DVSwitch.ini and conflict ports for similar protocols (DMR to DMR in this case). If using separate service files, check the service files for: WorkingDirectory=/opt/MMDVM_Bridge and change the working directory to match the folder that you're running MMDVM_Bridge from.
On Wed, Feb 27, 2019 at 12:48 PM Lito - WI6Y <Tolitski@...> wrote: Good morning Steve (AWV) --
Steve Miller KC1AWV
|
|
Re: BrandMeister to XLX
Lito - WI6Y
Hi Nick,
Have you tried this?
[XLX Network]
Enabled=1 File=XLXHosts.txt Port=62030 Password=passw0rd ReloadTime=60 # Local=3351 Slot=2 TG=6 Base=64000 Startup=933 Relink=10 Debug=0 #Allow user linking control using Private Calls UserControl=1 #Override default module for startup reflector Module=E
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Nicolas Larvor via Groups.Io <f4fkd@...>
Sent: Tuesday, February 26, 2019 11:32 AM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] BrandMeister to XLX Hi all,
Here is my DMRGateway.ini to connect to XLX
Mine is connected to XLX933-E
I've tried 2 MMDVM_Bridge instances to connected a XLX to IPSC2 but it don't work.
IPSC2fr3 <--> MMDVM_Bridge 1 <--> MMDVM_Bridge 2 <--> DMRGateway <--> XLX933-E
[General]
Timeout=10 # RFTimeout=10 # NetTimeout=7 RptAddress=127.0.0.1 RptPort=62032 LocalAddress=127.0.0.1 LocalPort=62031 RuleTrace=0 Daemon=0 Debug=0 [Log] # Logging levels, 0=No logging DisplayLevel=1 FileLevel=1 FilePath=. FileRoot=DMRGateway [Voice] Enabled=1 Language=en_GB Directory=./Audio [Info] Enabled=0 RXFrequency=435000000 TXFrequency=435000000 Power=1 Latitude=0.0 Longitude=0.0 Height=0 Location=Nowhere Description=Multi-Mode Repeater URL=www.google.co.uk [XLX Network] Enabled=1 File=XLXHosts.txt Port=62030 Password=passw0rd ReloadTime=60 # Local=3351 Slot=2 TG=2082 Base=64000 Startup=933 Relink=10 Debug=0 #Allow user linking control using Private Calls UserControl=1 #Override default module for startup reflector Module=E # BrandMeister [DMR Network 1] Enabled=0 Name=BM Address=44.131.4.1 Port=62031 # Local=3352 # Local cluster TGRewrite=1,9,1,9,1 # Reflector TG on to slot 2 TG9 TGRewrite=2,9,2,9,1 # Reflector control command slot 2 94000->4000 to 95000->5000 PCRewrite=2,94000,2,4000,1001 # Echo on RF slot 1 TG9990 to network slot 1 9990 TypeRewrite=1,9990,1,9990 SrcRewrite=1,9990,1,9990,1 # Reflector status returns SrcRewrite=2,4000,2,9,1001 # Pass all of the other private traffic on slot 1 and slot 2 PassAllPC=1 PassAllPC=2 Password=PASSWORD Location=1 Debug=0 # DMR+ [DMR Network 2] Enabled=0 Name=DMR+ Address=44.131.4.1 Port=55555 # Local=3352 # Reflector TG on to slot 2 TG8 TGRewrite=2,8,2,9,1 # Echo on slot 2 TG9990 TGRewrite=2,9990,2,9990,1 # Reflector control command slot 2 84000->4000 to 85000->5000 PCRewrite=2,84000,2,4000,1001 # Pass all of the other talk group traffic on slot 1 and slot 2 PassAllTG=1 PassAllTG=2 Password=PASSWORD Location=0 Debug=0 # TGIF Network [DMR Network 3] Enabled=0 Name=TGIF_Network TGRewrite0=1,1,2,1,9999998 SrcRewrite0=2,1,1,1,9999998 Address=tgif.network Password=passw0rd Port=62031 Location=0 Debug=0 # Local HBLink network [DMR Network 3] Enabled=0 Name=HBLink Address=44.131.4.2 Port=55555 # Local=3352 # Local area TG on to slot 2 TG11 TGRewrite=2,11,2,11,1 Password=PASSWORD Location=0 Debug=0 73 QRO, Nicolas - F8FKD
Le mardi 26 février 2019 à 20:25:20 UTC+1, Steve KC1AWV <smiller@...> a écrit :
Yes Lito, you have the right idea.
If you run the two programs for the XLX side in the foreground, can you copy and paste the output to me? Maybe I can diagnose what's going on before I complete the documentation. Day job is taking precedence over it right now.
|
|
Re: BrandMeister to XLX
Nicolas Larvor <f4fkd@...>
Hi all, Here is my DMRGateway.ini to connect to XLX Mine is connected to XLX933-E I've tried 2 MMDVM_Bridge instances to connected a XLX to IPSC2 but it don't work. IPSC2fr3 <--> MMDVM_Bridge 1 <--> MMDVM_Bridge 2 <--> DMRGateway <--> XLX933-E [General] Timeout=10 # RFTimeout=10 # NetTimeout=7 RptAddress=127.0.0.1 RptPort=62032 LocalAddress=127.0.0.1 LocalPort=62031 RuleTrace=0 Daemon=0 Debug=0 [Log] # Logging levels, 0=No logging DisplayLevel=1 FileLevel=1 FilePath=. FileRoot=DMRGateway [Voice] Enabled=1 Language=en_GB Directory=./Audio [Info] Enabled=0 RXFrequency=435000000 TXFrequency=435000000 Power=1 Latitude=0.0 Longitude=0.0 Height=0 Location=Nowhere Description=Multi-Mode Repeater URL=www.google.co.uk [XLX Network] Enabled=1 File=XLXHosts.txt Port=62030 Password=passw0rd ReloadTime=60 # Local=3351 Slot=2 TG=2082 Base=64000 Startup=933 Relink=10 Debug=0 #Allow user linking control using Private Calls UserControl=1 #Override default module for startup reflector Module=E # BrandMeister [DMR Network 1] Enabled=0 Name=BM Address=44.131.4.1 Port=62031 # Local=3352 # Local cluster TGRewrite=1,9,1,9,1 # Reflector TG on to slot 2 TG9 TGRewrite=2,9,2,9,1 # Reflector control command slot 2 94000->4000 to 95000->5000 PCRewrite=2,94000,2,4000,1001 # Echo on RF slot 1 TG9990 to network slot 1 9990 TypeRewrite=1,9990,1,9990 SrcRewrite=1,9990,1,9990,1 # Reflector status returns SrcRewrite=2,4000,2,9,1001 # Pass all of the other private traffic on slot 1 and slot 2 PassAllPC=1 PassAllPC=2 Password=PASSWORD Location=1 Debug=0 # DMR+ [DMR Network 2] Enabled=0 Name=DMR+ Address=44.131.4.1 Port=55555 # Local=3352 # Reflector TG on to slot 2 TG8 TGRewrite=2,8,2,9,1 # Echo on slot 2 TG9990 TGRewrite=2,9990,2,9990,1 # Reflector control command slot 2 84000->4000 to 85000->5000 PCRewrite=2,84000,2,4000,1001 # Pass all of the other talk group traffic on slot 1 and slot 2 PassAllTG=1 PassAllTG=2 Password=PASSWORD Location=0 Debug=0 # TGIF Network [DMR Network 3] Enabled=0 Name=TGIF_Network TGRewrite0=1,1,2,1,9999998 SrcRewrite0=2,1,1,1,9999998 Address=tgif.network Password=passw0rd Port=62031 Location=0 Debug=0 # Local HBLink network [DMR Network 3] Enabled=0 Name=HBLink Address=44.131.4.2 Port=55555 # Local=3352 # Local area TG on to slot 2 TG11 TGRewrite=2,11,2,11,1 Password=PASSWORD Location=0 Debug=0 73 QRO, Nicolas - F8FKD
Le mardi 26 février 2019 à 20:25:20 UTC+1, Steve KC1AWV <smiller@...> a écrit :
Yes Lito, you have the right idea. If you run the two programs for the XLX side in the foreground, can you copy and paste the output to me? Maybe I can diagnose what's going on before I complete the documentation. Day job is taking precedence over it right now.
|
|