News: This forum is now permanently frozen.
Pages: [1]
Topic: Problem with port forwarding... Please help.  (Read 2816 times)
« on: March 08, 2008, 22:39:36 »
DarkEagle *
Posts: 4

Greetz 2 all. I have a problem with port forwarding in m0n0wall 1.231. I'm so tired of solving.. so, any help would be greatly appreciated!

I have 2 interfaces:

1) WAN, PPPoE with real IP adress
2) LAN, 192.168.1.0 D-class net

I have a 192.168.1.122 server with Radmin (remote administrator proggie - like VNC and so on) on 28028 port. I need it to be acessed within WAN real IP adress from Internet by connecting to 28028 to the real-ip WAN adress.

So, what I've done:

First of all, I map external 28028 port to 28028 port into the LAN segment:

(http://img120.imageshack.us/img120/7615/m0n0wallpic01lw5.gif)

Second, I permit all from any to 1.122...

(http://img120.imageshack.us/img120/9982/m0n0wallpic02ky4.gif)


BUT.. It didn't work! And I wonder why... Could anybody tell me what's wrong? Thanks in advance...

PS. I've also tried to permit 1.122 packets in any direction onto the LAN page:

(http://img120.imageshack.us/img120/5852/m0n0wallpic03wh2.gif)

but it didn't works also Sad



« Reply #1 on: March 12, 2008, 17:09:25 »
dozzie152 *
Posts: 4

I am also having this same problem... Different IPs and subnets of course but i've done this before with NAT and port forwarding on other devices but for some reason i just can't get monowall to work am i missing something, ive tried all the same setups as the previous post?  I can get my pptp to work And sometimes i just use the vpn to get to my computer but i still would like to get this going.  I am using version 1.3b10 any suggestions? Shocked
« Reply #2 on: March 12, 2008, 19:03:35 »
fredg
Guest

Your Firewall Rule is wrong. You have Destination Port = * Don't use *, use the same port number you have as Int. Port Range in Firewall : NAT : Inbound, namely 28028.
« Reply #3 on: March 12, 2008, 20:39:49 »
DarkEagle *
Posts: 4

Ok, I've tried different configurations BUT nothing happens Sad First of all, I wrote 28028 everywhere I can.

(http://img204.imageshack.us/img204/8486/m0n00202tg5.gif)

I've applied the settings.. But.. Nothing.

Then I went to the Firewall States and get diagnostics there:

(http://img231.imageshack.us/img231/4195/m0n00201ge0.gif)

as you can see, my system (.110) is trying to connect to m0n0wall at .112 on 28028 and fails.. BTW my .110 system is using m0n0wall also - but via outbound NAT so it couldnt be a problem, am I right?

Well also I saw 9xxx ports coming from my .110 system to 28028 and tried to open theese ports like this:

(http://img134.imageshack.us/img134/8755/m0n00203uq6.gif)

but nothing happens.. still no connection :-/

BTW I set the "log packets for this rule" switch ON onto this rule.. but in LOGS I cant find anything declined by this rule (as permitted too..). I'm seriously confused.... Any ideas??
« Reply #4 on: March 12, 2008, 23:58:12 »
dozzie152 *
Posts: 4

What version of monowall are you using, im using 1.3b10 it does say its a beta version however i am forced to use this version due to the ports on the board im running it on.  I am looking in the forums and an awful lot of people are having this same issue, i wonder if it is a bug the developers missed or maybe they are working on it?
« Reply #5 on: March 13, 2008, 08:47:30 »
DarkEagle *
Posts: 4

I'm using 1.231 version.. As for bugfix there are no any port forwarding bug fixes or so on in whatsnew... The question still open Sad
« Reply #6 on: March 18, 2008, 23:32:03 »
DarkEagle *
Posts: 4

finally the problem is solved  Grin by adding routes to the WAN segment of the net into the LAN computer.  Roll Eyes
« Reply #7 on: April 01, 2008, 02:55:26 »
dozzie152 *
Posts: 4

Im not sure exactly what you are trying to say, you added routes to the wan segment? how did you accomplish this
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines