smcroute | Static multicast routing for UNIX | Router library

by troglobit C Version: 2.5.6 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | smcroute Summary

smcroute is a C library typically used in Networking, Router applications. smcroute has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

SMCRoute is a UNIX/Linux tool to manage and monitor multicast routes. It supports both IPv4 and IPv6 multicast routing. SMCRoute can be used as an alternative to dynamic multicast routers like [mrouted][] or [pimd][] in setups where static multicast routes should be maintained and/or no proper IGMP or MLD signaling exists. Multicast routes exist in the UNIX kernel as long as a multicast routing daemon runs. On Linux, multiple multicast routers can run simultaneously using different multicast routing tables.

Support

Quality

Security

License

Reuse

Support

smcroute has a low active ecosystem.

It has 186 star(s) with 58 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 135 have been closed. On average issues are closed in 225 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of smcroute is 2.5.6

Quality

smcroute has 0 bugs and 0 code smells.

Security

smcroute has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

smcroute code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

smcroute is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

smcroute releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of smcroute

Get all kandi verified functions for this library.

smcroute Key Features

No Key Features are available at this moment for smcroute.

smcroute Examples and Code Snippets

No Code Snippets are available at this moment for smcroute.

Community Discussions

Trending Discussions on smcroute

Receive specific multicast message on a client connected over VPN

QUESTION

Receive specific multicast message on a client connected over VPN

Asked 2019-Jan-02 at 20:24

Case: [ Subnet A , 192.168.2.0/24, Padavan firmware based internet gw ]

[ Subnet B , 192.168.1.0/24, Padavan firmware based internet gw ]

Host from subnet A (2.155) is connected via VPN (possible options: PPTP, OpenVPN, L2TP w/o ipsec) to subnet B, and receives address, saying 1.245/32

In subnet B exists host (1.10/32) which sends multicast datagramms to 224.0.0.50:9898 ; On router I see them with

tcpdump -i br0 -c 10 dst host 224.0.0.50 and port 9898 and multicast

13:46:54.345369 IP 192.168.1.10.4321 > 224.0.0.50.9898: UDP, length 135

I am looking for solutions, to receive/forward those broadcast messages, so they could be seen by hosts, connected via VPN

On router B, which is Padavan firmware based, I have, and limited to udpxy, igmproxy utilities, if needed.

On client host, I am debian based, and generally not limited in tools.

Datagrams are proprietary protocol, i.e. not a iptv or video stream.

Any ideas are welcomed.

[UPD] Additional info - per discussion in comments

That's a very specific hardware device, which is not very chatty in ethernet terms (saying max 1-2 datagramms in 5 seconds), thus for sure should be pretty forwardable. Unfortunately, It sends status updates purely via broadcasting. in Subnet A do exist similar device + control software. Thus I am looking for a way datagramms broadcasted to 224.0.0.50:9898 in subnet B to re-appear in subnet A. May be with help of some tool. May be smcroute, may be udpxy, maybe igmproxy

...

ANSWER

Answered 2018-Dec-09 at 14:57

As I don't like to leave resolved questions unanswered, here is currently working solution

In subnet B I have installed openVPN server endpoint, configured as L2.

In subnet A, on a control host I have installed openvpn client, that connects to subnet B, assigned interface is tapz

Source https://stackoverflow.com/questions/53171353

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install smcroute

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: