imzjustplayin
[H]ard|Gawd
- Joined
- Jan 24, 2006
- Messages
- 1,171
I was busy configuring my m0n0wall installation which BTW is running a lot better now since I've gotten more used to the system but I still have a few questions. I noticed that while the firewall rules allow for WAN port forwarding to a whole Lan subnet (which I've been doing for the most part), I noticed that this isn't the case for Network Address Translation. On some crappy consumer routers I've worked with, they supported port triggering, which means that what ever system requests that port within the network, they get it. Well I was wondering then, why can't I have this function with m0n0wall? Why is it not possible to have NAT translate a port range into multiple internal IP addresses?
I ask this question because lets say I'm using port 16567 (used in BF2) and I have NAT translate for that port into 192.168.0.184 (the internal IP for the computer using BF2). Now lets say a friend also wants to play BF2 and hes connecting to the same server, what I'd do is add in a NAT entry for his IP as well so that the port is forwarded to his system as well, thing is, m0n0wall won't let me do this. Is this an issue with m0n0wall or is this just not possible? Are two machines within a network not able to share the same port? How come I don't have to turn on NAT for port 80 but I do for these ports?
I ask this question because lets say I'm using port 16567 (used in BF2) and I have NAT translate for that port into 192.168.0.184 (the internal IP for the computer using BF2). Now lets say a friend also wants to play BF2 and hes connecting to the same server, what I'd do is add in a NAT entry for his IP as well so that the port is forwarded to his system as well, thing is, m0n0wall won't let me do this. Is this an issue with m0n0wall or is this just not possible? Are two machines within a network not able to share the same port? How come I don't have to turn on NAT for port 80 but I do for these ports?