multicast

Currently, WebSocket is working for client/server side. However, the browsers do not allow to create tcp connections direclty (which is the current implementation based). Instead, the web-sys must be used.

• Use a different WebSocket implementation if the target is wasm.
• wasm example of a client.

Hi @Barracuda09 ,

Some suggestion to improve the user interface experience:

• In the Frontend Overview (my preferable default page) why not convert the "Number of F.E." (or the "Name") to a link that displays directly the "Frontend Info" page of this f.e.?

Then it will be more easy to go directly to see the info (about two additional clicks).
What you think?

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