Quick links:
Product Overview
Installation
Settings and Administration
ADSL
SIP Support
Telephone ports
Network
Firewall
Wireless
VPN
Misc
Licenses
Troubleshooting
Differences
This shows you the differences between two versions of the page.
|
firewall:example_3 [2010/11/04 13:39] tibor |
firewall:example_3 [2010/11/04 13:58] (current) tibor |
||
|---|---|---|---|
| Line 59: | Line 59: | ||
| As you can see, we once again needed to check each ruleset to make sure the packets are allowed through, though many rulesets already allow them and does not need to be modified. Actually you only needed to add only one rule (in step 2), the rest was already present. And the modify action of the outgoing rule also helps our incoming packet to get back in and be sent to the correct PC. | As you can see, we once again needed to check each ruleset to make sure the packets are allowed through, though many rulesets already allow them and does not need to be modified. Actually you only needed to add only one rule (in step 2), the rest was already present. And the modify action of the outgoing rule also helps our incoming packet to get back in and be sent to the correct PC. | ||
| + | |||
| + | ===== Entering the rule ===== | ||
| + | You enter the rule of step 2 above into the "Additional rules" fields of the [[web GUI:security profile]] page: | ||
| + | | ET1 | Incoming user | post | proto == tcp && dport == 4044 accept | | ||
| + | All other necessary rules are already present in the standard firewall ruleset. | ||
