|
|
@@ -37,6 +37,7 @@ The currently supported operatins are:
|
|
|
* `admin.vm.firewall.Get`
|
|
|
* `admin.vm.firewall.Set`
|
|
|
* `admin.vm.firewall.Reload`
|
|
|
+
|
|
|
These actions can be tested by using the `qvm-firewall` utility. It is important to note that both the client and the daemon are more flexibile compared to the settings available via the GUI.
|
|
|
|
|
|
##### Configuration files
|
|
|
@@ -100,7 +101,7 @@ qvm-firewall <vmname> add action=accept dsthost=1.1.1.1 proto=tcp dstports=80-80
|
|
|
```
|
|
|
|
|
|
### Proposal
|
|
|
-Currently, all firewall rules have an `action` properties which can be either `accept` or `drop`. The plan is to add a third option `forward` specifically for implementing automatic port forwarding. Sych options must be supported both in the configuration file and in the Sdmin API (client-server). Lastly, it shall be implemented in the agent daemon.
|
|
|
+Currently, all firewall rules have an `action` properties which can be either `accept` or `drop`. The plan is to add a third option `forward` specifically for implementing automatic port forwarding. Such options must be supported both in the configuration file and in the Admin API (client-server). Lastly, it shall be implemented in the agent daemon.
|
|
|
The main issue however is the fact that currenly, the firewall client library is designated to operate only on the AppVM configured Firewall NetVM. However, in order to forward ports from the outside world, specific rules needs to be applied to the Firewall NetVM Networking NetVM. (ie: both is `sys-firewall` and `sys-net`, as currently done for manual port forwarding).
|
|
|
|
|
|
### action=forward
|
