12,270
edits
FireBrick Portmapping: Difference between revisions
m
no edit summary
No edit summary |
mNo edit summary |
||
| (7 intermediate revisions by 2 users not shown) | |||
|
<indicator name="FireBrick">[[File:Menu-FireBrick.svg|link=:Category:FireBrick|30px|Back up to the FireBrick Category]]</indicator>
==FireBrick port mapping example==
Mapping is done using Firewall rules.
<rule-set name="Mapping Example">▼
The principle is that you describe the original traffic (source/target interface, IP, protocol, port etc) and then define a Rule with what you want to happen to that traffic - eg, set a new target IP, port and enable NAT.
</rule-set>▼
source-interface="pppoe"
target-interface="self"
no-match-action="continue">
▲ </rule-set>
And then add a rule for RDP to this rule-set:
<rule name="Map RDP to server1"
target-port="3389"
set-target-ip="192.168.1.101"
set-nat="true"
action="accept"/>
You can add more requirements as needed, such as changing the port if needed, or adding source IPs so as to restrict access to known IPs. You can also use profiles to control access further.
If you have more port mappings then you can add more rule's as required, eg to add access to an internal web server you could map port 8080 to port 80 of the internal webserver:
<rule name="Map 8080 to web server2"
target-port="8080"
set-target-ip="192.168.1.102"
set-target-port="80"
set-nat="true"
action="accept"/>
You can then test this rule using the built in Firewall test diagnostic.
If you put in:
*source IP = anything you want
*Target IP = The FireBrick's IP
*Protocol = 17
*Target port = 3389
Then you should see it match your rule and change the target IP etc:
Checking rule-set 5 [Mapping] - Rule 3 [RDP to server1] matched, action is ACCEPT, no further rule-sets considered
NAT set (true)
Target IP set to 192.168.1.101
[[Category:FireBrick|Port]]
| |||