|
It depends entirely on how many repeaters and how many uplinks… how many TGIDs will have slot and TGID transcoded, etc.
Give me an idea of what you’re trying to achieve…. A few repeaters with no uplink would run on one core of a raspberry pi without breaking a sweat…. 50 repeaters with 15 transcoded TGIDs would be a very different story. On Jan 23, 2019, at 1:33 PM, Roselito de los Reyes < Tolitski@...> wrote:
In your experience what would be the minimum specs for HBlink to be happy?
Yes, HBlink will act as a server for MMDVM based repeaters and hotspots. On 1/23/2019 2:27 PM, Roselito de los Reyes wrote:
I tried applying for a master server for our group. It seems like the procedure is like Evel Knievel doing jumping jacks while doing his motorcycle jumps. Is there a way I can use the DVSwitch applications to run my own server where all the repeaters dedicated to a specific talkgroup/reflector can connect to?
73,
Lito WI6Y
Cort Buffington 785-865-7206
|
|
|
Steve N4IRS
toggle quoted messageShow quoted text
On 1/23/2019 2:34 PM, Cort N0MJS via
Groups.Io wrote:
For anyone starting fresh with an install of just hblink.py or the
traditional conference-style bridging, I would STRONGLY recommend
using hblink3 and avoiding the python2 version.
All future development will be with hblink3, and
there are several things in the works – from 2x faster packet
processing to a real web dashboard (hbmonitor is pretty crappy).
On Jan 23, 2019, at 1:28 PM, Steve N4IRS < szingman@...>
wrote:
Yes,
HBlink will act as a server for MMDVM based repeaters
and hotspots.
On 1/23/2019 2:27 PM,
Roselito de los Reyes wrote:
I tried
applying for a master server for our group. It seems
like the procedure is like Evel Knievel doing
jumping jacks while doing his motorcycle jumps. Is
there a way I can use the DVSwitch applications to
run my own server where all the repeaters dedicated
to a specific talkgroup/reflector can connect to?
73,
Lito WI6Y
Cort Buffington
785-865-7206
|
|
|
For anyone starting fresh with an install of just hblink.py or the traditional conference-style bridging, I would STRONGLY recommend using hblink3 and avoiding the python2 version.
All future development will be with hblink3, and there are several things in the works – from 2x faster packet processing to a real web dashboard (hbmonitor is pretty crappy). On Jan 23, 2019, at 1:28 PM, Steve N4IRS < szingman@...> wrote:
Yes,
HBlink will act as a server for MMDVM based repeaters and hotspots.
On 1/23/2019 2:27 PM, Roselito de los
Reyes wrote:
I tried applying for a master server for our group. It seems
like the procedure is like Evel Knievel doing jumping jacks
while doing his motorcycle jumps. Is there a way I can use the
DVSwitch applications to run my own server where all the
repeaters dedicated to a specific talkgroup/reflector can
connect to?
73,
Lito WI6Y
Cort Buffington 785-865-7206
|
|
|
In your experience what would be the minimum specs for HBlink to be happy?
toggle quoted messageShow quoted text
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Wednesday, January 23, 2019 11:28 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Master Server.
Yes,
HBlink will act as a server for MMDVM based repeaters and hotspots.
On 1/23/2019 2:27 PM, Roselito de los Reyes wrote:
I tried applying for a master server for our group. It seems like the procedure is like Evel Knievel doing jumping jacks while doing his motorcycle jumps. Is there a way I can use the DVSwitch applications to run my own server where all the repeaters dedicated
to a specific talkgroup/reflector can connect to?
73,
Lito WI6Y
|
|
|
Steve N4IRS
These are the items in MMDVM_Bridge.in that deal with logging into a
Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0
[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0
toggle quoted messageShow quoted text
On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct
On Wed, Jan 23, 2019 at 1:22
PM Steve N4IRS < szingman@...> wrote:
Check your password. Should be
passw0rd Notice the 0
On
1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line
that comes up says Login to master has failed, retrying
login ...
On Wed,
Jan 23, 2019 at 1:11 PM Steve N4IRS < szingman@...>
wrote:
Run the program(s) in the
foreground to look for errors.
Running the program in the foreground simply means
starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host
MMDVM.ini This runs the program from the prompt.
Notice the ./ in front of the program name. This
means run the program in this directory.
On
1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't
know how to run it in the foreground
On
Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS < szingman@...>
wrote:
Hoseline has been up
and down. First check your self care page
and make sure MMDVM_Bridge is logged in to
BM. Running MMDVM_Bridge in the foreground
will also tell you if it is connected to BM.
On
1/23/2019 2:04 PM, K4VL wrote:
I did see that I am
connected to Brandmeister it has me
wondering if my radio is not programmed
correctly. I did also try to click on
hoseline and got a 503 service
unavailable page.
On
Wed, Jan 23, 2019 at 12:50 PM Steve
N4IRS < szingman@...>
wrote:
Not a lot of
information to go on but in general:
Run each program in the foreground
so you can see what is happening.
Start at one end and work to the
other end.
Steve
On
1/23/2019 1:42 PM, K4VL wrote:
I was
wondering how to test my bridge? I
don't seem to be getting to it
through my hotspot. I went to the
CLI and keyed my radio and nothing
showed up. My server is setup as
311628005 and my talkgroup is
310286.
Thanks
|
|
|
Steve N4IRS
Yes,
HBlink will act as a server for MMDVM based repeaters and hotspots.
toggle quoted messageShow quoted text
On 1/23/2019 2:27 PM, Roselito de los
Reyes wrote:
I tried applying for a master server for our group. It seems
like the procedure is like Evel Knievel doing jumping jacks
while doing his motorcycle jumps. Is there a way I can use the
DVSwitch applications to run my own server where all the
repeaters dedicated to a specific talkgroup/reflector can
connect to?
73,
Lito WI6Y
|
|
|
I tried applying for a master server for our group. It seems like the procedure is like Evel Knievel doing jumping jacks while doing his motorcycle jumps. Is there a way I can use the DVSwitch applications to run my own server where all the repeaters dedicated
to a specific talkgroup/reflector can connect to?
73,
Lito WI6Y
|
|
|
The password under DMR Network is correct
On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS < szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0
On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes
up says Login to master has failed, retrying login ...
On Wed, Jan 23, 2019 at 1:11
PM Steve N4IRS < szingman@...> wrote:
Run the program(s) in the foreground
to look for errors.
Running the program in the foreground simply means starting
the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host
MMDVM.ini This runs the program from the prompt. Notice the
./ in front of the program name. This means run the program
in this directory.
On
1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how
to run it in the foreground
On Wed,
Jan 23, 2019 at 1:06 PM Steve N4IRS < szingman@...>
wrote:
Hoseline has been up and down.
First check your self care page and make sure
MMDVM_Bridge is logged in to BM. Running
MMDVM_Bridge in the foreground will also tell you if
it is connected to BM.
On
1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to
Brandmeister it has me wondering if my radio is
not programmed correctly. I did also try to
click on hoseline and got a 503 service
unavailable page.
On
Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS < szingman@...>
wrote:
Not a lot of
information to go on but in general:
Run each program in the foreground so you
can see what is happening. Start at one end
and work to the other end.
Steve
On
1/23/2019 1:42 PM, K4VL wrote:
I was wondering how
to test my bridge? I don't seem to be
getting to it through my hotspot. I went
to the CLI and keyed my radio and nothing
showed up. My server is setup as 311628005
and my talkgroup is 310286.
Thanks
|
|
|
Steve N4IRS
Check your password. Should be passw0rd Notice the 0
toggle quoted messageShow quoted text
On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes
up says Login to master has failed, retrying login ...
On Wed, Jan 23, 2019 at 1:11
PM Steve N4IRS < szingman@...> wrote:
Run the program(s) in the foreground
to look for errors.
Running the program in the foreground simply means starting
the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host
MMDVM.ini This runs the program from the prompt. Notice the
./ in front of the program name. This means run the program
in this directory.
On
1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how
to run it in the foreground
On Wed,
Jan 23, 2019 at 1:06 PM Steve N4IRS < szingman@...>
wrote:
Hoseline has been up and down.
First check your self care page and make sure
MMDVM_Bridge is logged in to BM. Running
MMDVM_Bridge in the foreground will also tell you if
it is connected to BM.
On
1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to
Brandmeister it has me wondering if my radio is
not programmed correctly. I did also try to
click on hoseline and got a 503 service
unavailable page.
On
Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS < szingman@...>
wrote:
Not a lot of
information to go on but in general:
Run each program in the foreground so you
can see what is happening. Start at one end
and work to the other end.
Steve
On
1/23/2019 1:42 PM, K4VL wrote:
I was wondering how
to test my bridge? I don't seem to be
getting to it through my hotspot. I went
to the CLI and keyed my radio and nothing
showed up. My server is setup as 311628005
and my talkgroup is 310286.
Thanks
|
|
|
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...
On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS < szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the
program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This
runs the program from the prompt. Notice the ./ in front of the
program name. This means run the program in this directory.
On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it
in the foreground
On Wed, Jan 23, 2019 at 1:06
PM Steve N4IRS < szingman@...> wrote:
Hoseline has been up and down. First
check your self care page and make sure MMDVM_Bridge is
logged in to BM. Running MMDVM_Bridge in the foreground will
also tell you if it is connected to BM.
On
1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to
Brandmeister it has me wondering if my radio is not
programmed correctly. I did also try to click on
hoseline and got a 503 service unavailable page.
On Wed,
Jan 23, 2019 at 12:50 PM Steve N4IRS < szingman@...>
wrote:
Not a lot of information to go
on but in general:
Run each program in the foreground so you can see
what is happening. Start at one end and work to the
other end.
Steve
On
1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test
my bridge? I don't seem to be getting to it
through my hotspot. I went to the CLI and keyed my
radio and nothing showed up. My server is setup as
311628005 and my talkgroup is 310286.
Thanks
|
|
|
Steve N4IRS
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the
program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This
runs the program from the prompt. Notice the ./ in front of the
program name. This means run the program in this directory.
toggle quoted messageShow quoted text
On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it
in the foreground
On Wed, Jan 23, 2019 at 1:06
PM Steve N4IRS < szingman@...> wrote:
Hoseline has been up and down. First
check your self care page and make sure MMDVM_Bridge is
logged in to BM. Running MMDVM_Bridge in the foreground will
also tell you if it is connected to BM.
On
1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to
Brandmeister it has me wondering if my radio is not
programmed correctly. I did also try to click on
hoseline and got a 503 service unavailable page.
On Wed,
Jan 23, 2019 at 12:50 PM Steve N4IRS < szingman@...>
wrote:
Not a lot of information to go
on but in general:
Run each program in the foreground so you can see
what is happening. Start at one end and work to the
other end.
Steve
On
1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test
my bridge? I don't seem to be getting to it
through my hotspot. I went to the CLI and keyed my
radio and nothing showed up. My server is setup as
311628005 and my talkgroup is 310286.
Thanks
|
|
|
Steve N4IRS
HELP !!!!!!!!!!!!!!!!!!!!
No one expects you to be a "Linux Expert" but understand this, you have chosen to build a bridge. You have to use the tools available. All of the DVSwitch programs run on Linux. You should put in the effort to at least be aware of how to do things in Linux. If you are posting on the discussion board then you have access to the internet. I doubt you can not find every Linux command and how to use it somewhere on the net.
Learn how to copy and paste from a window to e-mail or other program. For people to help you, they need to see the error. PLEASE don't post a screenshot or take a picture of the screen. Many people use PuTTY to login to a remote host via SSH. it is very easy to copy text from PuTTY. Simply put the mouse at the start of the text you want to copy and while holding down the right mouse button, drag the cursor across the text you want to copy. Now go to the e-mail you want to paste into. You can usually just go to the edit menu at the top of the screen and select paste. There is no way I can tell you how to paste into every program you could be running. I strongly suggest you practice this so when you need it, you know how to do it.
Start with a flow diagram of what you are trying to do. For example, if you are trying to build a bridge between AllStarLink and BrandMeister DMR, your diagram will look like this: BM <-> MMDVM_Bridge <-> Analog_Bridge <-> AllStarLink. The <-> indicates traffic or data will flow in both directions. Traffic flows from BM to MMDVM_Bridge which flows to Analog_Bridge and on to AllStarLink. Traffic also flows in the opposite direction from AllStarLink to BM. If you are unsure of the programs you will need to accomplish the task, ask in the discussion area. Post what you think the flow diagram should look like. Don't just ask someone else to create one for you.
While setting up and running the programs you should have root privileges.
You can do this in multiple ways: sudo ./myprogram or login to the machine as root (if possible) or sudo -s This will give you root privileges as long as you are logged in. This is easier then remembering to start each program with sudo.
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.
Run each program in a separate session (window). Most, if not all of the DVSwitch programs are built for only one purpose. Almost any bridge you build will require multiple programs. These programs talk to each other. You can watch the data "flow" from one program to the other if you are running all of the programs in windows so you can see the output. This is your first chance to catch errors. Don't understand the error? Read from the bottom up. Look for key words like, error, can't, fail etc. In the line containing errors look for things like a directory name or file name. When asking for help you should copy and paste the error into the e-mail. PLEASE don't just post a message that "it does not work" or my personal favorite "Broke! no good!" (Yes, I get that at work all the time.)
Build from the outside in. That way you can see the traffic flow. If you don't see the traffic, stop and fix the issue before going on to the next step. If the program on the outside of the flow diagram does not see the traffic from the external network, the next program in the flow diagram won't either. It's a heck of a lot easier to fix one program at a time then it is to troubleshoot 4 programs all at once. (It does not work!)
Change as little as possible in a configuration file. We have tried to set the parameters to usable values. There are comments in the configuration files. Read them! If you don't understand the comment, ask. Your question may spark an idea about how we can word the comment better. Some parameters are set to what should be obvious "place holder" values. A call sign like W1AW a DMR ID like 1234567 or 0. These things you will need to change. Keep a backup of the default configuration files so you can start over if need be. Some program have more then one configuration file. MMDVM_Bridge is this way. For MMDVM_Bridge, the file MMDVM_Bridge.ini enables and disables the mode (D-Star, DMR, P25 etc) it also controls the connection to the external network (BM, P25Reflector etc) This is CLOSELY modeled after MMDVM. DVSwitch.ini is used to define how MMDVM_Bridge communicates with other programs that make up the bridge (Analog_Bridge, Quantar_Bridge etc)
The DVSwitch programs use UDP ports to communicate or transfer traffic. You can not use the same port number twice. Below is a example of a port map you can use to visualize the port numbers in use and what they talk to and listen to. In the map below we are bridging from DMR to P25. Before you skip over this and say "that is not what I want to build" look at the map. It is a good example of how things go together. From left to right we start with BM. MMDVM_Bridge is used to communicate with BM. That communication is defined in MMDVM_Bridge.ini in the [DMR Network] stanza. A stanza is a group of variables and their values. The map does not show every entry in MMDVM_Bridge.ini just those variables needed to communicate. Below the MMDVM_Bridge.ini is the DVSwitch.ini file stanzas used. In this case, [DMR] This stanza defines how MMDVM_Bridge communicates with Analog_Bridge. The address 127.0.0.1 is the IP address of the host running Analog_Bridge. In this case 127.0.0.1 (localhost) When MMDVM_Bridge wants to send traffic to Analog_Bridge it transmits the traffic on UDP port number 31100. MMDVM_Bridge listens for traffic from Analog_Bridge on UDP port 31103. The arrows (<- and ->) indicates the direction of the traffic flow. These port number are now in use. You can NOT use them anywhere else in the bridge. For the bridge we are building below we need a second instance of Analog_Bridge running. That is why there are 2 in the flow diagram and the port map. The first Analog_Bridge needs to communicate with the second Analog_Bridge. This is done in the [USRP] stanza. Analog_Bridge DMR sends traffic on UDP port 32001 to Analog_Bridge P25. Analog_Bridge P25 sends traffic to Analog_Bridge DMR on UDP port 34001. and so on. That is a whole lot of words to describe what can be visualized in the port map below.
BrandMeister <-> MMDVM_Bridge <-> Analog_Bridge <-> Analog_Bridge <-> MMDVM_Bridge <-> P25Gateway
MMDVM_Bridge.ini Analog_Bridge.ini DMR Analog_Bridge.ini P25 MMDVM_Bridge.ini P25Gateway.ini
[DMR Network] [USRP] [USRP] [P25 Network] [General]
BM <---> Address=1.2.3.4 address = 127.0.0.1 <-> address = 127.0.0.1 GatewayAddress=127.0.0.1 <-> RptAddress=127.0.0.1
Port=62031 txPort = 32001 -------> rxPort = 32001 GatewayPort=42020 ---------> LocalPort=42020
Local=62032 rxPort = 34001 <------- txPort = 34001 LocalPort=32010 <----------- RptPort=32010
DVSwitch.ini DVSwitch.ini
[DMR] [AMBE_AUDIO] [AMBE_AUDIO] [P25]
Address = 127.0.0.1 <-> address = 127.0.0.1 address = 127.0.0.1 <-> Address = 127.0.0.1
TXPort = 31100 -------> rxPort = 31100 rxPort = 34100 <------- TXPort = 34100
RXPort = 31103 <------- txPort = 31103 txPort = 34103 -------> RXPort = 34103
ambeMode = DMR ambeMode = P25
One of the other great lines we have seen from people building bridges. "I have been banging my head against this for over a month and I don't know what's wrong" It should not take you more then an evening to bring up a bridge. If you have been trying for a month, you are now frustrated cross eyed and confused. Do not wait a month to ask for help. Again, "Broke! no good!" does not tell us much. What are you trying to do? Please show us your flow diagram at least. Where does the traffic stop? Posting the complete ini file or the log for 10 days does no one any good. Listen to what we ask for. Like in the flow diagram above and the port map, if you tell me MMDVM_Bridge does not see any traffic from BrandMeister, I'll want to see the [DMR] Stanza and the [DMR Network] stanza in MMDVM_Bridge.ini We will also want to see the section of the log where MMDVM_Bridge logs into BM. Showing us your DVSwitch.ini file does no good. The less extraneous information I have to pick through The quicker I can help you solve your problem.
Something that is pretty common: "I key my portable (HT) and nothing happens" The causes me to ask what mode is the HT? does BrandMeister or AllStarLink or the NXDN reflector see the traffic? Where does the traffic stop? We are not in the shack with you. We have to understand what is the environment you are working in. It does not help me if you tell me Jimmy's brother Tom key his new radio and I don't hear him on the bridge.
This document may come across to some as a gripe session. Well, to some extent it is. I have been doing remote support for 40 years. (Yes, I'm that old) I've supported everywhere from guys running a paper machine in a paper mill to PHDs in Computer Science. I don't care. It's been my job to help them solve their problem. In some cases if I did not solve it over the phone or via e-mail I had to drive 60 mile on Christmas eve in Michigan to fix it myself. (that really happened) All I'm saying here is please help us help you.
|
|
|
forgive my ignorance but I don't know how to run it in the foreground
On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS < szingman@...> wrote:
Hoseline has been up and down. First check your self care page and
make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in
the foreground will also tell you if it is connected to BM.
On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it
has me wondering if my radio is not programmed correctly. I did
also try to click on hoseline and got a 503 service unavailable
page.
On Wed, Jan 23, 2019 at 12:50
PM Steve N4IRS < szingman@...> wrote:
Not a lot of information to go on but
in general:
Run each program in the foreground so you can see what is
happening. Start at one end and work to the other end.
Steve
On
1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my
bridge? I don't seem to be getting to it through my
hotspot. I went to the CLI and keyed my radio and nothing
showed up. My server is setup as 311628005 and my
talkgroup is 310286.
Thanks
|
|
|
Steve N4IRS
Hoseline has been up and down. First check your self care page and
make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in
the foreground will also tell you if it is connected to BM.
toggle quoted messageShow quoted text
On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it
has me wondering if my radio is not programmed correctly. I did
also try to click on hoseline and got a 503 service unavailable
page.
On Wed, Jan 23, 2019 at 12:50
PM Steve N4IRS < szingman@...> wrote:
Not a lot of information to go on but
in general:
Run each program in the foreground so you can see what is
happening. Start at one end and work to the other end.
Steve
On
1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my
bridge? I don't seem to be getting to it through my
hotspot. I went to the CLI and keyed my radio and nothing
showed up. My server is setup as 311628005 and my
talkgroup is 310286.
Thanks
|
|
|
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.
On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS < szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening.
Start at one end and work to the other end.
Steve
On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting
to it through my hotspot. I went to the CLI and keyed my radio and
nothing showed up. My server is setup as 311628005 and my
talkgroup is 310286.
Thanks
|
|
|
Steve N4IRS
ls -lah
toggle quoted messageShow quoted text
On 1/23/2019 1:51 PM, Skyler Fennell
wrote:
I found it in the log2ram config file and
increased to 100MB.
Somethings writing a lot there — im trying to find
what it is— I’m already at 7 additional MB used after the first
12 hours or so.
On Wed, Jan 23, 2019 at 9:20 AM JJ Cummings
< cummingsj@...> wrote:
On Wed, Jan 23, 2019 at 3:40 AM Steve N4IRS
< szingman@...>
wrote:
I don't remember DIAL
setting up a RAM drive for Intel / AMD.
On
1/23/19 12:40 AM, Skyler Fennell wrote:
I'm using an older distro of DIAL
AllStar manual install from a Debian 8 virtual
machine, ( I need older app_rpt.c patched for IRLP
)
On
Tue, Jan 22, 2019 at 4:01 PM JJ Cummings < cummingsj@...>
wrote:
What distro/image are you using?
This does not exist in my
fstab. This is all I have:
# /etc/fstab: static
file system information.
#
# Use 'blkid' to
print the universally unique
identifier for a
# device; this may be
used with UUID= as a more robust
way to name devices
# that works even if
disks are added and removed. See
fstab(5).
#
# <file system>
<mount point>
<type>
<options>
<dump>
<pass>
# / was on /dev/vda1
during installation
UUID=87ebb3ad-15df-4e86-80a1-ccfd1cbe13c8
/
ext4
errors=remount-ro 0
1
/dev/sr0
/media/cdrom0
udf,iso9660 user,noauto
0
0
On
Tue, Jan 22, 2019 at 10:43 AM JJ
Cummings < cummingsj@...>
wrote:
If you look in
/etc/fstab you should see an entry
like the following (similar) set the
size= option to what I have it or
what you think... Don't get too
crazy because this uses memory and
not disk..
tmpfs /var/log tmpfs
defaults,noatime,nosuid,mode=0755,size=100m
JJC
Ok thank you.
Yeah I will get a rotating log
system and get the old garbage
out of there.
What commands do I use to
increase the file size?
Thanks,
Skyler
On Tue, Jan 22,
2019 at 8:57 AM JJ Cummings
< cummingsj@...>
wrote:
Skyler - time
to get logrotate running on
that system to age out old
things from the tmpfs where
/var/log is mounted. I'd
also look at increasing that
to 100M maybe as long as you
have enough memory for it.
On Tue, Jan
22, 2019 at 8:38 AM Steve
N4IRS < szingman@...>
wrote:
Your log directory is
full:
log2ram 40M
40M 0 100% /var/log
Can I assume it's a ASL
1.01 system?
On
1/22/2019 10:37 AM,
Skyler Fennell wrote:
mount
sysfs on /sys type
sysfs
(rw,nosuid,nodev,noexec,relatime)
proc on /proc type
proc
(rw,nosuid,nodev,noexec,relatime)
udev on /dev type
devtmpfs
(rw,relatime,size=10240k,nr_inodes=125703,mode=755)
devpts on /dev/pts
type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type
tmpfs
(rw,nosuid,relatime,size=204852k,mode=755)
/dev/vda1 on / type
ext4
(rw,relatime,errors=remount-ro,data=ordered)
securityfs on
/sys/kernel/security
type securityfs
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm
type tmpfs
(rw,nosuid,nodev)
tmpfs on /run/lock
type tmpfs
(rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on
/sys/fs/cgroup
type tmpfs
(ro,nosuid,nodev,noexec,mode=755)
cgroup on
/sys/fs/cgroup/systemd
type cgroup
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on
/sys/fs/pstore
type pstore
(rw,nosuid,nodev,noexec,relatime)
cgroup on
/sys/fs/cgroup/cpuset
type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on
/sys/fs/cgroup/cpu,cpuacct
type cgroup
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on
/sys/fs/cgroup/devices
type cgroup
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on
/sys/fs/cgroup/freezer
type cgroup
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on
/sys/fs/cgroup/net_cls,net_prio
type cgroup
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on
/sys/fs/cgroup/blkio
type cgroup
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on
/sys/fs/cgroup/perf_event
type cgroup
(rw,nosuid,nodev,noexec,relatime,perf_event)
tmpfs on
/etc/machine-id
type tmpfs
(ro,relatime,size=204852k,mode=755)
systemd-1 on
/proc/sys/fs/binfmt_misc
type autofs
(rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on
/sys/kernel/debug
type debugfs
(rw,relatime)
hugetlbfs on
/dev/hugepages
type hugetlbfs
(rw,relatime)
mqueue on /dev/mqueue
type mqueue
(rw,relatime)
fusectl on
/sys/fs/fuse/connections
type fusectl
(rw,relatime)
/dev/vda1 on
/var/log.hdd
type ext4
(rw,relatime,errors=remount-ro,data=ordered)
log2ram on /var/log
type tmpfs
(rw,nosuid,nodev,noexec,relatime,size=40960k,mode=755)
binfmt_misc on
/proc/sys/fs/binfmt_misc
type binfmt_misc
(rw,relatime)
tmpfs on /run/user/0
type tmpfs
(rw,nosuid,nodev,relatime,size=102428k,mode=700)
On
Tue, Jan 22, 2019
at 8:36 AM Steve
N4IRS < szingman@...> wrote:
Also show result
of mount
On
1/22/2019
10:34 AM,
Skyler Fennell
wrote:
Interesting
.... So when I
try to write a
file to this
directory and
add content to
it, I get an
error "No
Space Left on
Device"
However,
my root
directory has
17GB
remaining! How
could this be?
On
Tue, Jan 22,
2019 at 8:32
AM Skyler
Fennell via
Groups.Io
<electricity440= gmail.com@groups.io>
wrote:
Heres
something else
that is
interesting, I
am also
running an
instance of
MMDVM_bridge
for something
else ( not
related to the
P25 ), and
it's log files
have been
blank for a
couple of
months.
I have
similar log
settings for
this
MMDVM_Bridge.ini
[Log]
# Logging levels,
0=No logging,
1=Debug,
2=Message,
3=Info,
4=Warning,
5=Error,
6=Fatal
DisplayLevel=1
FileLevel=1
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
On
Tue, Jan 22,
2019 at 8:26
AM Skyler
Fennell via
Groups.Io
<electricity440= gmail.com@groups.io>
wrote:
Nope,
it's still
blank
root@stn3764:/var/log/mmdvm#
cat
P25Reflector-2019-01-22.log
root@stn3764:/var/log/mmdvm#
On
Tue, Jan 22,
2019 at 8:24
AM Steve N4IRS
< szingman@...>
wrote:
OK, good.
Check your log
file now.
Anything in
it?
On
1/22/2019
10:23 AM,
Skyler Fennell
wrote:
I: 2019-01-22
15:22:45.302
Opening P25
network
connection
I: 2019-01-22
15:22:45.386
Loaded 109242
Ids to the
callsign
lookup table
M: 2019-01-22
15:22:45.386
Starting
P25Reflector-20161101
I: 2019-01-22
15:22:45.386
Started the
DMR Id lookup
reload thread
M: 2019-01-22
15:22:47.724
Adding KG0SKY
(71.196.210.222:35143)
M: 2019-01-22
15:22:48.190
Adding WN0EHE
(71.228.144.180:42010)
On
Tue, Jan 22,
2019 at 8:18
AM Steve N4IRS
< szingman@...>
wrote:
when you run
P25Reflector
in the
foreground
what do you
get?
./P25Reflector
P25Reflector.ini
Steve
On
1/22/2019
10:15 AM,
Skyler Fennell
wrote:
First,
I would like
to put a great
thanks to
Steve and
everyone on
this group for
there efforts
helping
everyone out.
I
recently
installed
P25Reflector
and I wen't to
check my log
directory, and
I have blank
files
generated
every day with
the proper
date but with
no data in
them.
Below is
my config for
the
P25Reflector.ini
[General]
Daemon=0
[Id Lookup]
Name=DMRIds.dat
Time=24
[Log]
# Logging levels,
0=No logging
DisplayLevel=1
FileLevel=1
[Log]
FilePath=/var/log/mmdvm
FileRoot=P25Reflector
[Network]
Port=41000
Debug=1
|
|
|
I found it in the log2ram config file and increased to 100MB.
Somethings writing a lot there — im trying to find what it is— I’m already at 7 additional MB used after the first 12 hours or so.
On Wed, Jan 23, 2019 at 9:20 AM JJ Cummings < cummingsj@...> wrote:
On Wed, Jan 23, 2019 at 3:40 AM Steve N4IRS < szingman@...> wrote:
I don't remember DIAL setting up a RAM drive for Intel / AMD.
On 1/23/19 12:40 AM, Skyler Fennell
wrote:
I'm using an older distro of DIAL AllStar manual
install from a Debian 8 virtual machine, ( I need older
app_rpt.c patched for IRLP )
On
Tue, Jan 22, 2019 at 4:01 PM JJ Cummings < cummingsj@...> wrote:
What distro/image are you using?
This does not exist in my fstab. This is
all I have:
# /etc/fstab: static
file system information.
#
# Use 'blkid' to
print the universally unique identifier for a
# device; this may be
used with UUID= as a more robust way to name
devices
# that works even if
disks are added and removed. See fstab(5).
#
# <file system>
<mount point>
<type>
<options>
<dump>
<pass>
# / was on /dev/vda1
during installation
UUID=87ebb3ad-15df-4e86-80a1-ccfd1cbe13c8
/
ext4
errors=remount-ro 0
1
/dev/sr0
/media/cdrom0
udf,iso9660 user,noauto
0
0
On
Tue, Jan 22, 2019 at 10:43 AM JJ Cummings < cummingsj@...>
wrote:
If you look in /etc/fstab you should
see an entry like the following (similar) set the
size= option to what I have it or what you
think... Don't get too crazy because this uses
memory and not disk..
tmpfs /var/log tmpfs
defaults,noatime,nosuid,mode=0755,size=100m
JJC
Ok thank you. Yeah I will get
a rotating log system and get the old
garbage out of there.
What commands do I use to increase the file
size?
Thanks,
Skyler
On Tue, Jan 22, 2019 at 8:57 AM
JJ Cummings < cummingsj@...>
wrote:
Skyler - time to get
logrotate running on that system to age
out old things from the tmpfs where
/var/log is mounted. I'd also look at
increasing that to 100M maybe as long as
you have enough memory for it.
On Tue, Jan 22, 2019 at
8:38 AM Steve N4IRS < szingman@...>
wrote:
Your log
directory is full:
log2ram 40M 40M 0 100%
/var/log
Can I assume it's a ASL 1.01 system?
On
1/22/2019 10:37 AM, Skyler Fennell
wrote:
mount
sysfs on /sys type
sysfs
(rw,nosuid,nodev,noexec,relatime)
proc on /proc type
proc
(rw,nosuid,nodev,noexec,relatime)
udev on /dev type
devtmpfs
(rw,relatime,size=10240k,nr_inodes=125703,mode=755)
devpts on /dev/pts
type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type
tmpfs
(rw,nosuid,relatime,size=204852k,mode=755)
/dev/vda1 on / type
ext4
(rw,relatime,errors=remount-ro,data=ordered)
securityfs on
/sys/kernel/security type
securityfs
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm
type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock
type tmpfs
(rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on
/sys/fs/cgroup type tmpfs
(ro,nosuid,nodev,noexec,mode=755)
cgroup on
/sys/fs/cgroup/systemd type
cgroup
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on
/sys/fs/pstore type pstore
(rw,nosuid,nodev,noexec,relatime)
cgroup on
/sys/fs/cgroup/cpuset type
cgroup
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on
/sys/fs/cgroup/cpu,cpuacct
type cgroup
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on
/sys/fs/cgroup/devices type
cgroup
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on
/sys/fs/cgroup/freezer type
cgroup
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on
/sys/fs/cgroup/net_cls,net_prio
type cgroup
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on
/sys/fs/cgroup/blkio type
cgroup
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on
/sys/fs/cgroup/perf_event type
cgroup
(rw,nosuid,nodev,noexec,relatime,perf_event)
tmpfs on
/etc/machine-id type tmpfs
(ro,relatime,size=204852k,mode=755)
systemd-1 on
/proc/sys/fs/binfmt_misc type
autofs
(rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on
/sys/kernel/debug type debugfs
(rw,relatime)
hugetlbfs on
/dev/hugepages type hugetlbfs
(rw,relatime)
mqueue on /dev/mqueue
type mqueue (rw,relatime)
fusectl on
/sys/fs/fuse/connections type
fusectl (rw,relatime)
/dev/vda1 on
/var/log.hdd type ext4
(rw,relatime,errors=remount-ro,data=ordered)
log2ram on /var/log
type tmpfs
(rw,nosuid,nodev,noexec,relatime,size=40960k,mode=755)
binfmt_misc on
/proc/sys/fs/binfmt_misc type
binfmt_misc (rw,relatime)
tmpfs on /run/user/0
type tmpfs
(rw,nosuid,nodev,relatime,size=102428k,mode=700)
On
Tue, Jan 22, 2019 at 8:36 AM
Steve N4IRS < szingman@...>
wrote:
Also
show result of mount
On
1/22/2019 10:34 AM, Skyler
Fennell wrote:
Interesting
.... So when I try to
write a file to this
directory and add content
to it, I get an error "No
Space Left on Device"
However, my root
directory has 17GB
remaining! How could
this be?
On
Tue, Jan 22, 2019 at
8:32 AM Skyler Fennell
via Groups.Io
<electricity440= gmail.com@groups.io>
wrote:
Heres
something else that is
interesting, I am also
running an instance of
MMDVM_bridge for
something else ( not
related to the P25 ),
and it's log files
have been blank for a
couple of months.
I have similar
log settings for
this
MMDVM_Bridge.ini
[Log]
# Logging levels,
0=No logging,
1=Debug,
2=Message,
3=Info,
4=Warning,
5=Error,
6=Fatal
DisplayLevel=1
FileLevel=1
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
On
Tue, Jan 22, 2019 at
8:26 AM Skyler
Fennell via
Groups.Io
<electricity440= gmail.com@groups.io>
wrote:
Nope,
it's still blank
root@stn3764:/var/log/mmdvm#
cat
P25Reflector-2019-01-22.log
root@stn3764:/var/log/mmdvm#
On
Tue, Jan 22,
2019 at 8:24 AM
Steve N4IRS < szingman@...>
wrote:
OK, good.
Check your log
file now.
Anything in
it?
On
1/22/2019
10:23 AM,
Skyler Fennell
wrote:
I: 2019-01-22
15:22:45.302
Opening P25
network
connection
I: 2019-01-22
15:22:45.386
Loaded 109242
Ids to the
callsign
lookup table
M: 2019-01-22
15:22:45.386
Starting
P25Reflector-20161101
I: 2019-01-22
15:22:45.386
Started the
DMR Id lookup
reload thread
M: 2019-01-22
15:22:47.724
Adding KG0SKY
(71.196.210.222:35143)
M: 2019-01-22
15:22:48.190
Adding WN0EHE
(71.228.144.180:42010)
On
Tue, Jan 22,
2019 at 8:18
AM Steve N4IRS
< szingman@...>
wrote:
when you run
P25Reflector
in the
foreground
what do you
get?
./P25Reflector
P25Reflector.ini
Steve
On
1/22/2019
10:15 AM,
Skyler Fennell
wrote:
First,
I would like
to put a great
thanks to
Steve and
everyone on
this group for
there efforts
helping
everyone out.
I
recently
installed
P25Reflector
and I wen't to
check my log
directory, and
I have blank
files
generated
every day with
the proper
date but with
no data in
them.
Below is
my config for
the
P25Reflector.ini
[General]
Daemon=0
[Id Lookup]
Name=DMRIds.dat
Time=24
[Log]
# Logging levels,
0=No logging
DisplayLevel=1
FileLevel=1
[Log]
FilePath=/var/log/mmdvm
FileRoot=P25Reflector
[Network]
Port=41000
Debug=1
|
|
|
Steve N4IRS
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening.
Start at one end and work to the other end.
Steve
toggle quoted messageShow quoted text
On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting
to it through my hotspot. I went to the CLI and keyed my radio and
nothing showed up. My server is setup as 311628005 and my
talkgroup is 310286.
Thanks
|
|
|
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.
Thanks
|
|
|
Steve N4IRS
Maybe this will help:
root@repeater:/opt/DMRGateway# ./DMRGateway DMRGateway.ini
I: 2019-01-23 18:31:40.982 This software is for use on amateur radio
networks only,
I: 2019-01-23 18:31:40.982 it is to be used for educational purposes
only. Its use on
I: 2019-01-23 18:31:40.982 commercial networks is strictly
prohibited.
I: 2019-01-23 18:31:40.982 Copyright(C) 2017 by Jonathan Naylor,
G4KLX and others
M: 2019-01-23 18:31:40.983 DMRGateway-20180606 is starting
M: 2019-01-23 18:31:40.983 Built 11:29:08 Jan 10 2019 (GitID
#9579565)
I: 2019-01-23 18:31:40.983 MMDVM Network Parameters
I: 2019-01-23 18:31:40.983 Rpt Address: 127.0.0.1
I: 2019-01-23 18:31:40.983 Rpt Port: 62032
I: 2019-01-23 18:31:40.983 Local Address: 127.0.0.1
I: 2019-01-23 18:31:40.983 Local Port: 62031
M: 2019-01-23 18:31:40.984 MMDVM Network, Opening
M: 2019-01-23 18:31:40.984 Waiting for MMDVM to connect.....
M: 2019-01-23 18:32:00.014 MMDVM has connected
I: 2019-01-23 18:32:00.015 Rule trace: no
I: 2019-01-23 18:32:00.017 Loaded 301 XLX reflectors
I: 2019-01-23 18:32:00.017 XLX Network Parameters
I: 2019-01-23 18:32:00.018 Id: 3112138
I: 2019-01-23 18:32:00.018 Hosts file: ./XLXHosts.txt
I: 2019-01-23 18:32:00.018 Reload time: 60 minutes
I: 2019-01-23 18:32:00.018 Local: random
I: 2019-01-23 18:32:00.018 Port: 62030
I: 2019-01-23 18:32:00.018 Slot: 2
I: 2019-01-23 18:32:00.018 TG: 6
I: 2019-01-23 18:32:00.018 Base: 64000
I: 2019-01-23 18:32:00.018 Startup: XLX334
I: 2019-01-23 18:32:00.018 Relink: 10 minutes
I: 2019-01-23 18:32:00.018 User Control: enabled
I: 2019-01-23 18:32:00.018 Module: E
I: 2019-01-23 18:32:00.019 XLX: Using original configuration
message: N4IRS 222340000224940000010141.73329-50.39989000Iceberg,
North AtlanMMDVM_Bridge
4https://groups.io/g/DVSwitch
20180423 MMDVM_Unknown
M: 2019-01-23 18:32:00.019 XLX, Opening DMR Network
M: 2019-01-23 18:32:00.019 XLX, Connecting to XLX334
I: 2019-01-23 18:32:00.019 Voice Parameters
I: 2019-01-23 18:32:00.019 Enabled: yes
I: 2019-01-23 18:32:00.019 Language: en_US
I: 2019-01-23 18:32:00.019 Directory: ./Audio
M: 2019-01-23 18:32:00.020 DMRGateway-20180606 is running
D: 2019-01-23 18:32:10.071 XLX, Sending authorisation
D: 2019-01-23 18:32:10.122 XLX, Sending configuration
M: 2019-01-23 18:32:10.173 XLX, Logged into the master successfully
M: 2019-01-23 18:32:10.173 XLX, Linking to reflector XLX334 E
toggle quoted messageShow quoted text
On 1/23/2019 1:29 PM, Doug - W4DBG
wrote:
There is an E but no parrot is installed.
I guess I have muffed something up. I have the
same thing as you but no module showing.
I checked the log and it looks like it connects
and disconnects.
On Wed, Jan 23, 2019 at 12:28 PM Steve N4IRS
< szingman@...> wrote:
Is there a Echo
module? E?
On
1/23/2019 9:44 AM, Doug - W4DBG wrote:
I will keep plugging away at it. I
must still have something “off” attached is a photo
of the reflector dashboard showing the module
missing.
On Wed, Jan 23, 2019 at 8:20 AM Steve
N4IRS < szingman@...>
wrote:
Doug,
I have zero experience with XLX and DMRGateway
but I think what you want is is DMRGateway.ini
[XLX Network]
Enabled=1
File=XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
# Local=3351
Slot=1
TG=6
Base=64000
Startup=950
Relink=10
Debug=0
#Allow user linking control using Private Calls
UserControl=1
#Override default module for startup reflector
#Module=A
<--------------------------------------------------------
Uncomment this and set to the module you want.
On
1/23/2019 9:15 AM, Doug - W4DBG wrote:
On Wed, Jan 23, 2019 at
8:15 AM Steve N4IRS < szingman@...>
wrote:
It is.
Are you using DMRGateway to connect to
XLX or going direct from MMDVM_Bridge?
Steve
On
1/23/2019 9:13 AM, Doug - W4DBG
wrote:
Maybe I am missing
something. Is YSF2DMR in the
setup?
I thought that was a
hotspot setting?
On Wed, Jan 23,
2019 at 7:13 AM Steve KC1AWV
< smiller@...>
wrote:
Hi Doug-
I assume you're using
YSF2DMR? The DMR Network
stanza by default shows
commented out settings
for XLX. Here's mine for
example.
[DMR Network]
Id=[Your DMR ID]
XLXFile=XLXHosts.txt
XLXReflector=740
XLXModule=B
#StartupDstId=9990
# For TG call:
StartupPC=0
#StartupPC=1
#Address=44.131.4.1
Port=62030
Jitter=500
EnableUnlink=1
TGUnlink=4000
PCUnlink=0
# Local=62032
Password=PASSWORD
# Options=
TGListFile=TGList-DMR.txt
Debug=0
Steve KC1AWV
Hello to the
group...
I have read other
threads but I haven't
really seen an answer
that I am looking for.
I want to bridge a
YSF reflector to a XLX
Reflector in DMR mode.
It looks like I am
successful connecting
to the YSF reflector
and the XLX reflector
using the proper
gateways but on the
XLX reflector it is
not connected to a
specific Module. I
just need to know what
to change to attach it
to a specific module.
Thanks!
Doug
W4DBG
--
--
--
--
|
|
|
