DMR NET goes offline when using DMR Gateway for BM and TGIF networks

[w8vpc]

Another issue popped up.

My repeater was configured to have TGIF on slot 1 and Brandmeister on slot 2. DMR Master was set to DMR Gateway.

everything was working well until I enabled FM Mode.

Now DMR NET goes offline after a few seconds.

Both networks have security password protection enabled.

If i configure pstar for TGIF only, DMR NET stays enabled.

Here is what my network settings are in expert mode, DMR GW:

[DMR Network 1]
Enabled=1
Id=310443
Address=3104.master.brandmeister.network
Port=62031
TGRewrite0=2,9,2,9,1
PCRewrite0=2,94000,2,4000,1001
TypeRewrite0=2,9990,2,9990
SrcRewrite0=2,4000,2,9,1001
PassAllPC0=1
PassAllPC1=2
PassAllTG1=2
Password="***********"
Debug=0
Name=BM_3104_United_States
Location=1

[DMR Network 2]
Enabled=0
Address=43.245.72.66
Port=55555
TGRewrite0=2,8,2,9,1
PCRewrite0=2,84000,2,4000,1001
Password="PASSWORD"
Debug=0
Id=31044367
Name=DMR+_IPSC2-Australia
Location=0

[DMR Network 3]
Enabled=0
Id=310443
Name=TGIF_SLOT1
TGRewrite0=1,1,2,1,9999998
SrcRewrite0=2,1,1,1,9999998
Address=tgif.network
Password="#############
Port=62031
Location=0
Debug=0

[DMR Network 4]
Enabled=1
Id=310443
Name=TGIF_SLOT1
TGRewrite0=1,1,2,1,9999998
SrcRewrite0=2,1,1,1,9999998
Address=tgif.network
Password="%%%%%%%%%%
Port=62031
Location=0
Debug=0

Would there be something in the settings?

tnx
Mike W8VPC

[VE3RD]

Retrace your logic with the following process in mind.

1) The DMRGateway processes rules one by one in progression from Net 1 to Net 5 in two passes. The first pass processes all regular rules. If it gets a match it will process it and bails out. ie: If it gets a match in Net 1 it will not process any rules in Net 4
2) The first pass will ignore all PassAll Lines
3) The second pass will pickup the first matching passall, process it and bail out
4) To get a match the TS must match and the TG fall within the range specified
-------------

When trouble shooting the DMRGateway, I usually comment out all the PassAll and PC rules on all networks. Get that working, then add the PC calls, get that working
Then add the PassAlls(I never use the PassAlls.,, With 4 active networks I use specific rules for what I want to do)

With log file level set to 2, restart the DMRGateway and run the following
tail -f -n100 /var/log/pi-star/DMRGateway-2022-06*
This will display the startup parameters and the range handled by each command
ie:
M: 2022-06-07 13:33:26.103 TGIF_Network, Opening DMR Network
I: 2022-06-07 13:33:26.103 Rewrite RF: 2:TG14000001-TG14999999 -> 2:TG1-TG999999
I: 2022-06-07 13:33:26.103 Rewrite Net: 2:TG1-TG999999 -> 2:TG14000001-TG14999999
I: 2022-06-07 13:33:26.103 Rewrite RF: 2:14000001-14999999 -> 2:1-999999
I: 2022-06-07 13:33:26.103 Rewrite Net: 2:1-9999999 -> 2:TG0

and finally show your connection to the servers.
ie:
M: 2022-06-07 13:33:36.258 TGIF_Network, Logged into the master successfully
M: 2022-06-07 13:33:36.288 MNet_Network, Logged into the master successfully
M: 2022-06-07 13:33:36.339 DMR+_IPSC2-CAN-TRBO, Logged into the master successfully


Good Luck

PS.
What is the following rule intended to do in Net4
SrcRewrite0=2,1,1,1,9999998

Phil VE3RD

[M1DNS]

Dont use net3
pistar uses it for default dmr2ysf mode.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

[VE3RD]

Quite Right!! Do Not use Net 3 unless you are tying to use one of the two dmr2xxx crossovers

ie: DMR2YSF, or DMR2NXDN. These must be initially configured in the pi-star configuration page.

If you try to use Net3 for any other mode, the configuration script that runs when you hit [Apply Changes] will wipe it out.

Phil VE3RD