-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce the XRF peer type #85
base: master
Are you sure you want to change the base?
Conversation
XRF peers can now be defined in the xlxd.interlink file, allowing linking of a local module to a remote using the DExtra protocol. XRF peers are shown in the peer list, along with their XLX siblings. Changes affect only how the reflector initiates the link, as xlxd already supports incoming DExtra links. Each peer is associated internally with a remote client, so code changes include distinguishing peer connect acks from non-peer ones and handling timeouts differently for peer clients to clean up the peer data structure. The DExtra disconnect packet is now properly implemented.
Hi, so if I want to try XRF linking from XLX reflector I just change files and restart service or I need to do something more? |
You just need to add the respective configuration in |
Up and running now on my test server... can we do multiple module links between two reflectors? |
It's implemented. Not a feature request.
… On 4 Jun 2018, at 07:57, sixfootseven ***@***.***> wrote:
Is this a feature you have written? Or a request for someone else to implement?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#85 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABnsxZ0gMfcCXVUJkbmq8fYGKyZC1gLIks5t5L5AgaJpZM4SakS9>.
|
I wonder if it would be possible for this feature to be modified so multiple links between two reflectors could be achieved? |
Just be aware that all the xrf peer links seem to stop responding if you
have too many. Not sure on number sorry.
Very good feature though. Have decommissioned my separate dxrfd linking
server.
Tony Hughes
ZL2EZ
…On Mon., 11 Jun. 2018, 5:07 am Colby Ross, ***@***.***> wrote:
I wonder if it would be possible for this feature to be modified so
multiple links between two reflectors could be achieved?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#85 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AkzDNm1wPcZJQMXViYShu5I0bduvbiJ0ks5t7VJEgaJpZM4SakS9>
.
|
Running your code on my reflector, only have 2 XRF links but it's working perfectly so far. Thanks! |
XRF peers can now be defined in the xlxd.interlink file,
allowing linking of a local module to a remote using
the DExtra protocol. XRF peers are shown in the peer list,
along with their XLX siblings.
Changes affect only how the reflector initiates the link,
as xlxd already supports incoming DExtra links.
Each peer is associated internally with a remote client,
so code changes include distinguishing peer connect acks
from non-peer ones and handling timeouts differently for
peer clients to clean up the peer data structure.
The DExtra disconnect packet is now properly implemented.