svxlink
svxlink copied to clipboard
sm0svx
Multiple SvxReflector
Hi Tobias , have you planned or thought about the possibility of connecting multiple SvxReflector? 73
Multiple reflectors are already in use, with differing results. The rrf4.f5nlg.ovh:82 still on v1 protocol has a server on v2 and talk groups. The svxportal-uk.ddns.net:81 has connections to the Swedish Portal. I already have a node on two reflectors but with individual connection between them. Success is not the word I would use but it seems to work. Chris.
On Wed, 7 Sep 2022, 17:31 Giacomo De Angelis, @.***> wrote:
Hi Tobias , have you planned or thought about the possibility of connecting multiple SvxReflector? 73
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/597, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5HMXLMJHNRKBPRUEITV5C7ORANCNFSM6AAAAAAQG54664 . You are receiving this because you are subscribed to this thread.Message ID: @.***>
What we need in future is a kind of interlink to transfer some or all possible talkgroups between reflectors. It's fact, we build now not only a reflector between a couple of repeaters, we want to build bigger networks. Here in DL we have now reflectors with over 80 client connections, so it will be very difficult to transfer a higher value or all talkgroups to other reflectors. The best solution will be an interface for a real server-2-server connection in svxreflector like the interlink option in xlxd. The need for such a solution is constantly increasing.
73 Heiko, DL1BZ
In addition, I would like the possibility that the audio can be sent in duplex both between the nodes and the reflectors. Gladly also configurable Mni 73s de Adi / DL1HRC
Yes, I have a plan for interconnecting reflectors so that talk groups can be used seamlessly in between reflectors all over the world.
Great to hear that this concepts is evolving. FM Poland has a continuous growth trend... no of node is ca 140 / i think in DL is double and more. @sm0svx have you got any time perspective ? is there any way to help you with execution?
My intention is to work on reflector interconnection code this summer. The first step will be to interconnect reflectors with the purpose of load sharing within a country. This interconnection variant is not meant to interconnect reflectors in other countries with each other though. That is the next step.
So interconnection is at the top of my TODO-list.
Thanks for reply. I'm very excited - this is a super GREAT NEWS.
We are observing a huge growth of FM modulation . Many people are tend to fallback to FM from Digital Voice space - what is good - but also create challange of scaling infrastucture. We have also some natural grow seeds from PL perspective - ex. USA / UK where local comunities of polish speaking operators are growing.
IMHO small steps approach with this topic is really good. First thing first. It's really good that you have plan for it. crossing fingers for idea.
What we can also see there is trend of IPv6 adoption. Many of telco providers like ORANGE or T-MOBILE started to active default settings with IPv6 connectivity - but svxlink works only with IPv4. This is very popular problem with mobile based cennectivity hotspots - especially with summertime / vacations. I hope you will find some time with this topic also. Crossing fingers for your plans and execution.
If I can suggest some implementation for federation protocol - maybe easer would be to start shaping communication ref-ref with speperated / dedicated ports and based the code on ref-node protocol - IMHO this part is really well stabilised. Reflectors are working without any problems. Many thanks for this implementation.
If there is anything that we can help with it - we are very happy to help.
I concur… Small take up so far in the UK, but hopefully increasing.
Chris
On 10 Jun 2024, at 21:03, Daniel SP0DZ @.***> wrote:
Thanks for reply. I'm very excited - this is a super GREAT NEWS.
We are observing a huge growth of FM modulation . Many people are tend to fallback to FM from Digital Voice space - what is good - but also create challange of scaling infrastucture. We have also some natural grow seeds from PL perspective - ex. USA / UK where local comunities of polish speaking operators are growing.
IMHO small steps approach with this topic is really good. First thing first. It's really good that you have plan for it. crossing fingers for idea.
What we can also see there is trend of IPv6 adoption. Many of telco providers like ORANGE or T-MOBILE started to active default settings with IPv6 connectivity - but svxlink works only with IPv4. This is very popular problem with mobile based cennectivity hotspots - especially with summertime / vacations. I hope you will find some time with this topic also. Crossing fingers for your plans and execution.
If I can suggest some implementation for federation protocol - maybe easer would be to start shaping communication ref-ref with speperated / dedicated ports and based the code on ref-node protocol - IMHO this part is really well stabilised. Reflectors are working without any problems. Many thanks for this implementation.
If there is anything that we can help with it - we are very happy to help.
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/597#issuecomment-2159187594, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5B6QTQ7BGP6WURJUO3ZGYBC3AVCNFSM6AAAAABJCDGLROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGE4DONJZGQ. You are receiving this because you commented.