Searinox
7 Jan 2013, 18:09
WARNING: Headache ahead.
Here's my predicament:
I have a network with many ppl and ONE router which takes 16 network rules. Well, they're all filled up(yes I know it sounds stupid to actually be able to fill them up, please don't ask, and no I can't change them). I can't add anymore rules. Thankfully, the rules support port ranges. So what I did is made rules with port ranges for whatever was customizable.
Example: I explicitly changed the port ranges of some apps to 38001, 38002..... 38005 and put them under ONE rule. WA is among them.
Here's problem number two: when you have a SINGLE PORT in a rule, you can specify which port to forward to. For example I can listen to port 80 and forward it over the LAN to port 8080. You can't do that with port RANGE rules. So in other words, if I open port 38005 in the range for WA, I MUST send it port 38005 and only 38005. If this issue didn't exist, I'd have simply forwarded 38005 to 17011 and that'd be the end.
When I wanted to play with friends over Direct IP, I bumped into this issue, since I can only open port 38005 and Direct IP hosting always seems to listen to 17011. I had to rely on a messy workaround: I downloaded a free app called PassPort which listens to 38005 on my computer and forwards it back to itself via 127.0.0.1:17011 where Worms is listening. This will not work over WormNET. Users on WN try to connect to port 17011 because that's what my host is advertising. If I set it to 38005 I have to disable the app before playing, which is also forwarding some other services in the same manner because of my port predicament. If I don't, then the clients try to connect to 38005, which is picked up by PassPort and forwarded back to WA over 17011, which is now useless because WA is listening to 38005!
So what would help? It would help if WA could advertise port 38005 to the clients, but STILL listen to 17011. Any way to do this?
Here's my predicament:
I have a network with many ppl and ONE router which takes 16 network rules. Well, they're all filled up(yes I know it sounds stupid to actually be able to fill them up, please don't ask, and no I can't change them). I can't add anymore rules. Thankfully, the rules support port ranges. So what I did is made rules with port ranges for whatever was customizable.
Example: I explicitly changed the port ranges of some apps to 38001, 38002..... 38005 and put them under ONE rule. WA is among them.
Here's problem number two: when you have a SINGLE PORT in a rule, you can specify which port to forward to. For example I can listen to port 80 and forward it over the LAN to port 8080. You can't do that with port RANGE rules. So in other words, if I open port 38005 in the range for WA, I MUST send it port 38005 and only 38005. If this issue didn't exist, I'd have simply forwarded 38005 to 17011 and that'd be the end.
When I wanted to play with friends over Direct IP, I bumped into this issue, since I can only open port 38005 and Direct IP hosting always seems to listen to 17011. I had to rely on a messy workaround: I downloaded a free app called PassPort which listens to 38005 on my computer and forwards it back to itself via 127.0.0.1:17011 where Worms is listening. This will not work over WormNET. Users on WN try to connect to port 17011 because that's what my host is advertising. If I set it to 38005 I have to disable the app before playing, which is also forwarding some other services in the same manner because of my port predicament. If I don't, then the clients try to connect to 38005, which is picked up by PassPort and forwarded back to WA over 17011, which is now useless because WA is listening to 38005!
So what would help? It would help if WA could advertise port 38005 to the clients, but STILL listen to 17011. Any way to do this?