-
Updated
Nov 12, 2020 - Go
multicast
Here are 230 public repositories matching this topic...
-
Updated
Aug 28, 2019 - C++
-
Updated
Jul 15, 2020 - JavaScript
-
Updated
Apr 20, 2020 - Go
-
Updated
Nov 7, 2020 - C
-
Updated
Nov 7, 2020 - C
-
Updated
Aug 21, 2020 - Java
-
Updated
Nov 11, 2020 - Java
-
Updated
Jun 24, 2018 - Python
-
Updated
Nov 12, 2020 - Rust
-
Updated
Nov 2, 2020 - C++
-
Updated
Nov 16, 2020 - Python
-
Updated
Nov 10, 2020 - C
-
Updated
Oct 11, 2020 - Erlang
Currently, the firewall operates only on "allow/deny" basis for the whole packet, as long as it's answers includes a name from the whitelist.
Current situation creates unnecessary traffic in target network, extraneous data being transmitted over the tunnel and potentially exposes sensitive data to the whole target network.
Smarter firewall would solve this by re-creating the packet with
-
Updated
Sep 21, 2020 - Java
-
Updated
Oct 11, 2020 - Shell
-
Updated
Sep 15, 2020 - C++
-
Updated
Nov 12, 2020 - C
Improve this page
Add a description, image, and links to the multicast topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the multicast topic, visit your repo's landing page and select "manage topics."
Hi @Barracuda09 ,
When using the v1.6.2 with the last fixes of the ChildPipe frontend, I see time to time a "Segmentation fault". At time, I can't see where the error is (however, I'll try to debug it, so don't care about this now). But I suggest to implement some auto-restarting functionality to overcome such unkown errors. In my environment the SATPI acts as another SAT>IP server, so it is us