SVXReflector - PTT issues

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

SVXReflector - PTT issues

Tomek

Hi,

In our FM-LINK network in Poland we use SVXReflector as the main HUB to which 14 repeaters are connected. Everything works great, but lately we have had problems with the internet provider SVXReflector HUB. When the internet connection was broken during transmission and the repeaters lost contact with SVXReflector - the whole network remained in PTT mode - endless. It was required to restart all 14 repeaters to disable broadcasting.
This looks like a lack of protocol security if you break a link from a server to a client.
The situation was repeated several times.

Greeting,
Tom SQ4BJA


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

svxlink-devel mailing list
Tomek, which version of SvxLink are you running? A bug like that was fixed on april 8.

Date:   Sat Apr 8 16:18:11 2017 +0200

    ReflectorLogic audio flush timeout on incoming audio
   
    If there was an active talker and the connection was lost to the
    reflector server, the audio pipe was not flushed and so the TX would
    hang.

So it should be fixed from SvxLink version 1.5.99.7-svxreflector.

73's de SM0SVX / Tobias


On 07/17/2017 09:46 PM, Tomek wrote:

Hi,

In our FM-LINK network in Poland we use SVXReflector as the main HUB to which 14 repeaters are connected. Everything works great, but lately we have had problems with the internet provider SVXReflector HUB. When the internet connection was broken during transmission and the repeaters lost contact with SVXReflector - the whole network remained in PTT mode - endless. It was required to restart all 14 repeaters to disable broadcasting.
This looks like a lack of protocol security if you break a link from a server to a client.
The situation was repeated several times.

Greeting,
Tom SQ4BJA



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Tomek

Hi Tobias,

We have SVXLINK=1.5.99.6.

I`m going to upgrade it to 1.5.99.11-svxreflector

Thanks,

Tom SQ4BJA


W dniu 2017-07-18 o 00:10, Tobias Blomberg via Svxlink-devel pisze:
Tomek, which version of SvxLink are you running? A bug like that was fixed on april 8.

Date:   Sat Apr 8 16:18:11 2017 +0200

    ReflectorLogic audio flush timeout on incoming audio
   
    If there was an active talker and the connection was lost to the
    reflector server, the audio pipe was not flushed and so the TX would
    hang.

So it should be fixed from SvxLink version 1.5.99.7-svxreflector.

73's de SM0SVX / Tobias


On 07/17/2017 09:46 PM, Tomek wrote:

Hi,

In our FM-LINK network in Poland we use SVXReflector as the main HUB to which 14 repeaters are connected. Everything works great, but lately we have had problems with the internet provider SVXReflector HUB. When the internet connection was broken during transmission and the repeaters lost contact with SVXReflector - the whole network remained in PTT mode - endless. It was required to restart all 14 repeaters to disable broadcasting.
This looks like a lack of protocol security if you break a link from a server to a client.
The situation was repeated several times.

Greeting,
Tom SQ4BJA



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Tomek

Hi,

After upgrade SVXLink to 1.5.99.11-svxreflector - the Reflector module can`t talk to old SVXReflector server. So if I upgrade SVXReflector, old one SVXLink (1.5.99.6) cant talk to new reflector. So I cant upgrade all in one day. Older svxreflector protocol is not compatible with new one?

Tom SQ4BJA


W dniu 2017-07-18 o 20:35, Tomek pisze:

Hi Tobias,

We have SVXLINK=1.5.99.6.

I`m going to upgrade it to 1.5.99.11-svxreflector

Thanks,

Tom SQ4BJA


W dniu 2017-07-18 o 00:10, Tobias Blomberg via Svxlink-devel pisze:
Tomek, which version of SvxLink are you running? A bug like that was fixed on april 8.

Date:   Sat Apr 8 16:18:11 2017 +0200

    ReflectorLogic audio flush timeout on incoming audio
   
    If there was an active talker and the connection was lost to the
    reflector server, the audio pipe was not flushed and so the TX would
    hang.

So it should be fixed from SvxLink version 1.5.99.7-svxreflector.

73's de SM0SVX / Tobias


On 07/17/2017 09:46 PM, Tomek wrote:

Hi,

In our FM-LINK network in Poland we use SVXReflector as the main HUB to which 14 repeaters are connected. Everything works great, but lately we have had problems with the internet provider SVXReflector HUB. When the internet connection was broken during transmission and the repeaters lost contact with SVXReflector - the whole network remained in PTT mode - endless. It was required to restart all 14 repeaters to disable broadcasting.
This looks like a lack of protocol security if you break a link from a server to a client.
The situation was repeated several times.

Greeting,
Tom SQ4BJA



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

svxlink-devel mailing list
On 07/19/2017 12:10 AM, Tomek wrote:

Hi,

After upgrade SVXLink to 1.5.99.11-svxreflector - the Reflector module can`t talk to old SVXReflector server. So if I upgrade SVXReflector, old one SVXLink (1.5.99.6) cant talk to new reflector. So I cant upgrade all in one day. Older svxreflector protocol is not compatible with new one?


Remember, SvxReflector is experimental and unreleased software under development. It is expected to have flaws during the development period (like hanging transmitters, crashes, security problems or worse). New versions is likely to be incompatible with old ones.

Someone using the experimental software must be aware of this and realize what it will mean for their system installation. In this case it means that you need to upgrade all nodes at the same time for continued operation.

I try to keep the master branch pretty stable but when you choose to run SvxLink software from a task branch (like svxreflector) you should expect problems. It may be good to know that when a pull request on GitHub is marked "WIP" it means "Work In Progress". The primary reason for such a pull request is for developers being able to collaborate on developing the branch.

It is great that others want to take part in the development as testers, like you do. It is very much appreciated! It is very important though to understand that a system under development/test may have all sorts of problems and that you are prepared to deal with them. Some way to easily upgrade all participating nodes in one sweep is highly recommended since testers should normally always run the latest version.

I hope this explains what it means to be a software tester. Please keep testing. It helps getting SvxReflector becoming stable!

73's de SM0SVX / Tobias


Tom SQ4BJA


W dniu 2017-07-18 o 20:35, Tomek pisze:

Hi Tobias,

We have SVXLINK=1.5.99.6.

I`m going to upgrade it to 1.5.99.11-svxreflector

Thanks,

Tom SQ4BJA


W dniu 2017-07-18 o 00:10, Tobias Blomberg via Svxlink-devel pisze:
Tomek, which version of SvxLink are you running? A bug like that was fixed on april 8.

Date:   Sat Apr 8 16:18:11 2017 +0200

    ReflectorLogic audio flush timeout on incoming audio
   
    If there was an active talker and the connection was lost to the
    reflector server, the audio pipe was not flushed and so the TX would
    hang.

So it should be fixed from SvxLink version 1.5.99.7-svxreflector.

73's de SM0SVX / Tobias


On 07/17/2017 09:46 PM, Tomek wrote:

Hi,

In our FM-LINK network in Poland we use SVXReflector as the main HUB to which 14 repeaters are connected. Everything works great, but lately we have had problems with the internet provider SVXReflector HUB. When the internet connection was broken during transmission and the repeaters lost contact with SVXReflector - the whole network remained in PTT mode - endless. It was required to restart all 14 repeaters to disable broadcasting.
This looks like a lack of protocol security if you break a link from a server to a client.
The situation was repeated several times.

Greeting,
Tom SQ4BJA



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Adi Bier-3

Hi Tobias,

was is the version of svxreflector binary that fits to svxlink binary (1.5.99.11-svxreflector)? SvxReflector v0.1.99.3-svxreflector ?

The clients connects, then disconnect after about 5 seconds. No further info (Major/Minor,...)

## DB0HAL_70cm: MsgAuthResponse(b9d9dc80a2fe84a6a721cb89744d6d0abded47)
DB0HAL_70cm: Login OK from xx.xx.xx.xx:45592
: Heartbeat timeout
### ReflectorClient::disconnect: Heartbeat timeout
### ReflectorClient::onDiscTimeout
Client xx.xx.xx.xx:47472 disconnected: Locally ordered disconnect
DB0BLA: Client xx.xx.xx.xx:47303 disconnected: Connection closed by remote peer
Client xx.xx.xx.xx:47304 connected
### xx.xx.xx.xx:47304: MsgProtoVer(0, 6)
### DB0BLA: MsgAuthResponse(eb457e95a55e70b57ba36698e3beda92a6b88)
DB0BLA: Login OK from xx.xx.xx.xx:47304
DB0FIB: Client xx.xx.xx.xx:54766 disconnected: Connection closed by remote peer
Client xx.xx.xx.xx:54767 connected
### xx.xx.xx.xx:54767: MsgProtoVer(0, 6)
DL1HRC/p: Client xx.xx.xx.xx:52135 disconnected: Connection closed by remote peer
DB0HAL_2m: Client xx.xx.xx.xx:37444 disconnected: Connection closed by remote peer
### DB0FIB: MsgAuthResponse(33b96b6c74d5eb2f245887adc4e55889e8e21e)
DB0FIB: Login OK from xx.xx.xx.xx:54767
Client xx.xx.xx.xx:52138 connected
### xx.xx.xx.xx:52138: MsgProtoVer(0, 6)
...

73s Adi


Am 19.07.2017 um 11:25 schrieb Tobias Blomberg via Svxlink-devel:
On 07/19/2017 12:10 AM, Tomek wrote:

Hi,

After upgrade SVXLink to 1.5.99.11-svxreflector - the Reflector module can`t talk to old SVXReflector server. So if I upgrade SVXReflector, old one SVXLink (1.5.99.6) cant talk to new reflector. So I cant upgrade all in one day. Older svxreflector protocol is not compatible with new one?


Remember, SvxReflector is experimental and unreleased software under development. It is expected to have flaws during the development period (like hanging transmitters, crashes, security problems or worse). New versions is likely to be incompatible with old ones.

Someone using the experimental software must be aware of this and realize what it will mean for their system installation. In this case it means that you need to upgrade all nodes at the same time for continued operation.

I try to keep the master branch pretty stable but when you choose to run SvxLink software from a task branch (like svxreflector) you should expect problems. It may be good to know that when a pull request on GitHub is marked "WIP" it means "Work In Progress". The primary reason for such a pull request is for developers being able to collaborate on developing the branch.

It is great that others want to take part in the development as testers, like you do. It is very much appreciated! It is very important though to understand that a system under development/test may have all sorts of problems and that you are prepared to deal with them. Some way to easily upgrade all participating nodes in one sweep is highly recommended since testers should normally always run the latest version.

I hope this explains what it means to be a software tester. Please keep testing. It helps getting SvxReflector becoming stable!

73's de SM0SVX / Tobias


Tom SQ4BJA


W dniu 2017-07-18 o 20:35, Tomek pisze:

Hi Tobias,

We have SVXLINK=1.5.99.6.

I`m going to upgrade it to 1.5.99.11-svxreflector

Thanks,

Tom SQ4BJA


W dniu 2017-07-18 o 00:10, Tobias Blomberg via Svxlink-devel pisze:
Tomek, which version of SvxLink are you running? A bug like that was fixed on april 8.

Date:   Sat Apr 8 16:18:11 2017 +0200

    ReflectorLogic audio flush timeout on incoming audio
   
    If there was an active talker and the connection was lost to the
    reflector server, the audio pipe was not flushed and so the TX would
    hang.

So it should be fixed from SvxLink version 1.5.99.7-svxreflector.

73's de SM0SVX / Tobias


On 07/17/2017 09:46 PM, Tomek wrote:

Hi,

In our FM-LINK network in Poland we use SVXReflector as the main HUB to which 14 repeaters are connected. Everything works great, but lately we have had problems with the internet provider SVXReflector HUB. When the internet connection was broken during transmission and the repeaters lost contact with SVXReflector - the whole network remained in PTT mode - endless. It was required to restart all 14 repeaters to disable broadcasting.
This looks like a lack of protocol security if you break a link from a server to a client.
The situation was repeated several times.

Greeting,
Tom SQ4BJA



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

svxlink-devel mailing list
On 07/19/2017 09:20 PM, Adi Bier wrote:

Hi Tobias,

was is the version of svxreflector binary that fits to svxlink binary (1.5.99.11-svxreflector)? SvxReflector v0.1.99.3-svxreflector ?

Just have a look at the versions file in the svxreflector branch:

    https://github.com/sm0svx/svxlink/blob/svxreflector/src/versions

SVXLINK=1.5.99.11-svxreflector
SVXREFLECTOR=0.1.99.3-svxreflector

73's de SM0SVX / Tobias


The clients connects, then disconnect after about 5 seconds. No further info (Major/Minor,...)

## DB0HAL_70cm: MsgAuthResponse(b9d9dc80a2fe84a6a721cb89744d6d0abded47)
DB0HAL_70cm: Login OK from xx.xx.xx.xx:45592
: Heartbeat timeout
### ReflectorClient::disconnect: Heartbeat timeout
### ReflectorClient::onDiscTimeout
Client xx.xx.xx.xx:47472 disconnected: Locally ordered disconnect
DB0BLA: Client xx.xx.xx.xx:47303 disconnected: Connection closed by remote peer
Client xx.xx.xx.xx:47304 connected
### xx.xx.xx.xx:47304: MsgProtoVer(0, 6)
### DB0BLA: MsgAuthResponse(eb457e95a55e70b57ba36698e3beda92a6b88)
DB0BLA: Login OK from xx.xx.xx.xx:47304
DB0FIB: Client xx.xx.xx.xx:54766 disconnected: Connection closed by remote peer
Client xx.xx.xx.xx:54767 connected
### xx.xx.xx.xx:54767: MsgProtoVer(0, 6)
DL1HRC/p: Client xx.xx.xx.xx:52135 disconnected: Connection closed by remote peer
DB0HAL_2m: Client xx.xx.xx.xx:37444 disconnected: Connection closed by remote peer
### DB0FIB: MsgAuthResponse(33b96b6c74d5eb2f245887adc4e55889e8e21e)
DB0FIB: Login OK from xx.xx.xx.xx:54767
Client xx.xx.xx.xx:52138 connected
### xx.xx.xx.xx:52138: MsgProtoVer(0, 6)
...

73s Adi


Am 19.07.2017 um 11:25 schrieb Tobias Blomberg via Svxlink-devel:
On 07/19/2017 12:10 AM, Tomek wrote:

Hi,

After upgrade SVXLink to 1.5.99.11-svxreflector - the Reflector module can`t talk to old SVXReflector server. So if I upgrade SVXReflector, old one SVXLink (1.5.99.6) cant talk to new reflector. So I cant upgrade all in one day. Older svxreflector protocol is not compatible with new one?


Remember, SvxReflector is experimental and unreleased software under development. It is expected to have flaws during the development period (like hanging transmitters, crashes, security problems or worse). New versions is likely to be incompatible with old ones.

Someone using the experimental software must be aware of this and realize what it will mean for their system installation. In this case it means that you need to upgrade all nodes at the same time for continued operation.

I try to keep the master branch pretty stable but when you choose to run SvxLink software from a task branch (like svxreflector) you should expect problems. It may be good to know that when a pull request on GitHub is marked "WIP" it means "Work In Progress". The primary reason for such a pull request is for developers being able to collaborate on developing the branch.

It is great that others want to take part in the development as testers, like you do. It is very much appreciated! It is very important though to understand that a system under development/test may have all sorts of problems and that you are prepared to deal with them. Some way to easily upgrade all participating nodes in one sweep is highly recommended since testers should normally always run the latest version.

I hope this explains what it means to be a software tester. Please keep testing. It helps getting SvxReflector becoming stable!

73's de SM0SVX / Tobias


Tom SQ4BJA


W dniu 2017-07-18 o 20:35, Tomek pisze:

Hi Tobias,

We have SVXLINK=1.5.99.6.

I`m going to upgrade it to 1.5.99.11-svxreflector

Thanks,

Tom SQ4BJA


W dniu 2017-07-18 o 00:10, Tobias Blomberg via Svxlink-devel pisze:
Tomek, which version of SvxLink are you running? A bug like that was fixed on april 8.

Date:   Sat Apr 8 16:18:11 2017 +0200

    ReflectorLogic audio flush timeout on incoming audio
   
    If there was an active talker and the connection was lost to the
    reflector server, the audio pipe was not flushed and so the TX would
    hang.

So it should be fixed from SvxLink version 1.5.99.7-svxreflector.

73's de SM0SVX / Tobias


On 07/17/2017 09:46 PM, Tomek wrote:

Hi,

In our FM-LINK network in Poland we use SVXReflector as the main HUB to which 14 repeaters are connected. Everything works great, but lately we have had problems with the internet provider SVXReflector HUB. When the internet connection was broken during transmission and the repeaters lost contact with SVXReflector - the whole network remained in PTT mode - endless. It was required to restart all 14 repeaters to disable broadcasting.
This looks like a lack of protocol security if you break a link from a server to a client.
The situation was repeated several times.

Greeting,
Tom SQ4BJA



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Adi Bier-3
Am 19.07.2017 um 23:08 schrieb Tobias Blomberg via Svxlink-devel:

> Just have a look at the versions file in the svxreflector branch:
>
>     https://github.com/sm0svx/svxlink/blob/svxreflector/src/versions
>
> SVXLINK=1.5.99.11-svxreflector
> SVXREFLECTOR=0.1.99.3-svxreflector
>

exactly this versions I've runnig here. The problem was that the libs are not overwritten with make install.
I think this problem has already been discussed? Could it be changed this way?

73s Adi

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Tomek
Hi all,

We have the same problem. Every one repeater still connecting and
disconnecting from svxreflector. What`s wrong?

SvxReflector v0.1.99.3-svxreflector
SvxLink v1.5.99.11-svxreflector

Tom SQ4BJA


W dniu 2017-07-20 o 12:21, Adi Bier pisze:

> Am 19.07.2017 um 23:08 schrieb Tobias Blomberg via Svxlink-devel:
>
>> Just have a look at the versions file in the svxreflector branch:
>>
>>      https://github.com/sm0svx/svxlink/blob/svxreflector/src/versions
>>
>> SVXLINK=1.5.99.11-svxreflector
>> SVXREFLECTOR=0.1.99.3-svxreflector
>>
> exactly this versions I've runnig here. The problem was that the libs are not overwritten with make install.
> I think this problem has already been discussed? Could it be changed this way?
>
> 73s Adi
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Svxlink-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
>
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Adi Bier-2
You have to _manual_ copy the created libs under ~/svxlink/src/build/* to the destination path e.g. /usr/lib/* or /usr/lib64 depending on your system.
Do it on svxreflector and on the nodes as well. The problem is, that a "make install" do not overwrite the old libs in the destination path on your system :/
That should be fixed.

73s de Adi / DL1HRC

Am 20.07.2017 um 18:08 schrieb Tomek:
> Hi all,
>
> We have the same problem. Every one repeater still connecting and
> disconnecting from svxreflector. What`s wrong?
>
> SvxReflector v0.1.99.3-svxreflector
> SvxLink v1.5.99.11-svxreflector
>
> Tom SQ4BJA


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Adi Bier-3
In reply to this post by Tomek
You have to _manual_ copy the created libs under ~/svxlink/src/build/* to the destination path e.g. /usr/lib/* or /usr/lib64 depending on your system.
Do it on svxreflector and on the nodes as well. The problem is, that a "make install" do not overwrite the old libs in the destination path on your system :/
That should be fixed.

73s de Adi / DL1HRC

Am 20.07.2017 um 18:08 schrieb Tomek:
> Hi all,
>
> We have the same problem. Every one repeater still connecting and
> disconnecting from svxreflector. What`s wrong?
>
> SvxReflector v0.1.99.3-svxreflector
> SvxLink v1.5.99.11-svxreflector
>
> Tom SQ4BJA


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Rob Janssen
Adi Bier wrote:
> You have to _manual_ copy the created libs under ~/svxlink/src/build/* to the destination path e.g. /usr/lib/* or /usr/lib64 depending on your system.
> Do it on svxreflector and on the nodes as well. The problem is, that a "make install" do not overwrite the old libs in the destination path on your system :/
> That should be fixed.
>
> 73s de Adi / DL1HRC
>

I think there should be a "make uninstall" that removes all binaries and libraries (not configfiles).
I wrote a script that does this as part of a rebuild, because in the past I have had problems because of different library versions existing at different locations.
So now I first run a "make", then stop svxlink/remotetrx (noting if it was running), remove all binaries and libraries from all locations used now and in the past,
do a "make install" and then restart what was running.
It would be nice when it was available as part of the makefile, so everyone can use it.
(making an installable package is another solution, but often too much trouble and too many different package managers exist)

Rob

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Adi Bier-3

> I think there should be a "make uninstall" that removes all binaries and libraries (not configfiles).
> I wrote a script that does this as part of a rebuild, because in the past I have had problems because of different library versions existing at different locations.
> So now I first run a "make", then stop svxlink/remotetrx (noting if it was running), remove all binaries and libraries from all locations used now and in the past,
> do a "make install" and then restart what was running.
> It would be nice when it was available as part of the makefile, so everyone can use it.
> (making an installable package is another solution, but often too much trouble and too many different package managers exist)
>
> Rob
>

Hi Rob,

yes, I think this problem it should be solved. It's also a trap for people who standing close to the development.

vy 73s de Adi / DL1HRC


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

F5VMR Orange

Hi Guys - I had the problem too, but have started the re-install as you have discussed.

Many Thanks

Chris f5vmr

 

 

 

 

> Message du 20/07/17 19:15

> De : "Adi Bier" <[hidden email]>
> A : "Discussions about development issues" <[hidden email]>
> Copie à :
> Objet : Re: [Svxlink-devel] SVXReflector - PTT issues
>
>
> > I think there should be a "make uninstall" that removes all binaries and libraries (not configfiles).
> > I wrote a script that does this as part of a rebuild, because in the past I have had problems because of different library versions existing at different locations.
> > So now I first run a "make", then stop svxlink/remotetrx (noting if it was running), remove all binaries and libraries from all locations used now and in the past,
> > do a "make install" and then restart what was running.
> > It would be nice when it was available as part of the makefile, so everyone can use it.
> > (making an installable package is another solution, but often too much trouble and too many different package managers exist)
> >
> > Rob
> >
>
> Hi Rob,
>
> yes, I think this problem it should be solved. It's also a trap for people who standing close to the development.
>
> vy 73s de Adi / DL1HRC
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Svxlink-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel

.vcf (378 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

F5VMR Orange
In reply to this post by Adi Bier-3

No - Still doesn't solve the problem.

Thu Jul 20 20:09:59 2017: ReflectorLogic: Connection established to 192.168.0.100:5210

Thu Jul 20 20:10:09 2017: *** WARNING[ReflectorLogic]: Unknown protocol message received: msg_type=0

Thu Jul 20 20:10:14 2017: *** WARNING[ReflectorLogic]: Unknown protocol message received: msg_type=0

Thu Jul 20 20:10:24 2017: ReflectorLogic: Disconnected from 192.168.0.100:5210: Connection closed by remote peer

 
I copy the build library on the repeater (/usr/lib/armhf-linux-gnueabhif) and on the server (/usr/lib/i386-linux-gnu)

using sudo cp -r -i etc, to confirm the overwrite of the files. No change to the operation unfortunately

 

Chris


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel

.vcf (378 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

F5VMR Orange
In reply to this post by Adi Bier-3

Hold the Front Page!!!! I did the copy as you suggested, then continued the make_install - It works.

Chris

 

 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel

.vcf (378 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Tomek
In reply to this post by F5VMR Orange

So, i have different errors on repeater side:

### FMLinkReflector: Reconnecting to reflector server
FMLinkReflector: Disconnected from 217.61.2.1:5300: Locally ordered disconnect

Nothing helps... All libraries, bins are the same as in source.

Tom SQ4BJA

W dniu 2017-07-20 o 20:14, f5vmr pisze:

No - Still doesn't solve the problem.

Thu Jul 20 20:09:59 2017: ReflectorLogic: Connection established to 192.168.0.100:5210

Thu Jul 20 20:10:09 2017: *** WARNING[ReflectorLogic]: Unknown protocol message received: msg_type=0

Thu Jul 20 20:10:14 2017: *** WARNING[ReflectorLogic]: Unknown protocol message received: msg_type=0

Thu Jul 20 20:10:24 2017: ReflectorLogic: Disconnected from 192.168.0.100:5210: Connection closed by remote peer

 
I copy the build library on the repeater (/usr/lib/armhf-linux-gnueabhif) and on the server (/usr/lib/i386-linux-gnu)

using sudo cp -r -i etc, to confirm the overwrite of the files. No change to the operation unfortunately

 

Chris



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

svxlink-devel mailing list
In reply to this post by Adi Bier-3
On 07/20/2017 12:21 PM, Adi Bier wrote:

> Am 19.07.2017 um 23:08 schrieb Tobias Blomberg via Svxlink-devel:
>
>> Just have a look at the versions file in the svxreflector branch:
>>
>>      https://github.com/sm0svx/svxlink/blob/svxreflector/src/versions
>>
>> SVXLINK=1.5.99.11-svxreflector
>> SVXREFLECTOR=0.1.99.3-svxreflector
>>
> exactly this versions I've runnig here. The problem was that the libs are not overwritten with make install.
> I think this problem has already been discussed? Could it be changed this way?
So you mean that existing library files are not overwritten by newly
built library files even though they are different from the old ones?

73's de SM0SVX / Tobias


>
> 73s Adi
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Svxlink-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

Adi Bier-3
>
>> exactly this versions I've runnig here. The problem was that the libs are not overwritten with make install.
>> I think this problem has already been discussed? Could it be changed this way?
> So you mean that existing library files are not overwritten by newly built library files even though they are different from the old ones?
>
> 73's de SM0SVX / Tobias
>

correct Tobias, I think it's a pending and urgent problem.
A "make install" doesn't overwrite the old so-files in _some_ cases, not in any cases.
When I'm working on DMR branch (as root) it's working very well here under Ubuntu with new lib's created by make install.
When I login to some nodes later to make some installings I'll facing this problems. It's independent from the system, I'm using openSuse, Debian, Ubuntu, Armbian
At the moment I can not specify more detailed where we should search for the problem, sri :/

Please could you check this? I think we have only two urgent problems at the moment in the field of development:

1) this make install problem
2) the assert in AsyncTimer class that causes a segfault under some circumstances


vy 73s de Adi / DL1HRC



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVXReflector - PTT issues

svxlink-devel mailing list
In reply to this post by Rob Janssen
On 07/20/2017 06:54 PM, Rob Janssen wrote:
> (making an installable package is another solution, but often too much
> trouble and too many different package managers exist)
I have added experimental support for CPack to SvxLink. CPack is
integrated in CMake and is a rather simple way to create a package. The
produced package is not of distributable quality but may be good enough
to be used for local installations instead of "make install".

One problem is that I have not found a way to tell CPack which files are
configuration files and thus should not be overwritten by a new package.
A workaround is to place the original files in a non-standard locations
and copy the configuration files to /etc/svxlink and then point out the
config file using the --config command line option.

I have only briefly tested with DEB package. It will only work in a
directory cloned from Git for now.

Do something like this:

# Clone
git clone https://github.com/sm0svx/svxlink.git

# Install
cd svxlink/src
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr -DSYSCONF_INSTALL_DIR=/etc
-DSVX_SYSCONF_INSTALL_DIR=/etc/svxlink/dist -DLOCAL_STATE_DIR=/var
-DCPACK_GENERATOR=DEB ..
make
make doc
make package
sudo dpkg -i svxlink-15.11.310.g896da2b-Linux.deb

# After first install
sudo cp -a /etc/svxlink/dist/* /etc/svxlink/
sudo useradd -r -g daemon svxlink
sudo chown -R svxlink.daemon /var/spool/svxlink

# Run
svxlink --config /etc/svxlink/svxlink.conf

Not the prettiest solution but maybe useful?

73's de SM0SVX / Tobias


>
> Rob
>
> ------------------------------------------------------------------------------
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Svxlink-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
12
Loading...