Skip to content

iamd3vil/magicportal

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Magicportal

Magicportal allows you to forward multicast UDP data from one place to another where multicast is not supported.

Magicportal has to be run on both servers. It uses Gnatsd(https://nats.io) message queue for sending messages between them.

It can be run on two modes:

  1. forwarder: Has to be run in this mode on the server where data has to be received.
  2. agent: Has to be run in this mode on the server where multicast isn't supported.

Note: TLS can be enabled, but currently Magicportal doesn't support client certificates. This will be suppported in the future.

Usage

$ ./magicportal.bin -h
  --config string   Configuration path (default "config.toml")

An example config:

mode = "agent"
multicast_groups = [
    {multicast_addr = "233.1.2.5:34074", interface = "lo"}
]
max_packet_size = 1024

[nats]
tls = false
nats_url = ["nats://127.0.0.1:4222"]
auth_enabled = false
username = ""
password = ""

[agent]
send_as_unicast = true

[agent.unicast_addrs]
"233.1.2.5:34074" = "127.0.0.1:24113"

Magicportal needs a config file which can be in json or toml. See config.sample.json / config.sample.toml for example configuration.

We can give multiple multicast groups in the multicast_groups array. send_as_unicast will tell the agent to send the data as unicast to the address mapped with the multicast group in unicast_addrs.

About

Magicportal allows you to forward multicast UDP to places where multicast is not supported

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published