Welcome, Guest. Please login or register.
Did you miss your activation email?
Friday 15 November 2024, 08:48:07 pm

Login with username, password and session length

Visit the Official Endian Bug tracker  HERE
14255 Posts in 4377 Topics by 6515 Members
Latest Member: hulteends
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Port Forwarding Problem
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Port Forwarding Problem  (Read 19033 times)
gatekeeper
Jr. Member
*
Offline Offline

Posts: 3


« on: Wednesday 31 March 2010, 03:12:23 am »

I tried setting up port forwarding but instead the webpage would appear.. the administration page of EFW appeared.. How to fix this? Thanks..
Logged
whoiam55
Full Member
***
Offline Offline

Posts: 71



WWW
« Reply #1 on: Wednesday 31 March 2010, 03:16:57 am »

Hi there, didn't get you, can you be more specific? at least please tell us the configuration of your setup.
Logged

सत्यमेव जयते!
gatekeeper
Jr. Member
*
Offline Offline

Posts: 3


« Reply #2 on: Wednesday 31 March 2010, 04:29:19 am »

Sorry for that...

I just installed EFC 2.3.0. Its WAN is setup as PPPoE. Now this is what I want to accomplish.. I want that my webserver which is located in GREEN interface could be accessible both from the outside and within the LAN using the domain name.

I tried several times already.. I even  read the forum.. but none of those worked in here. I tried port forwarding Destination NAT, Source NAT, Outgoing NAT...everything but of no avail.

What I am seeing actually is the webGUI interface of the EFC instead the webpage hosted locally. I tried the domain name yet still the EFC webgui appeared in the screen too..

What do you think is the problem? Thank you!

Logged
gatekeeper
Jr. Member
*
Offline Offline

Posts: 3


« Reply #3 on: Wednesday 31 March 2010, 01:30:02 pm »

Anybody here please who have successfully port forward traffic (http) from the public and from the inside (webserver).. thanks..
Logged
whoiam55
Full Member
***
Offline Offline

Posts: 71



WWW
« Reply #4 on: Wednesday 31 March 2010, 03:17:51 pm »

If you are getting the endian config page then you should have setup a system access rule from outside, try disabling that. Also, I tried with the setup you wanted and face no problem.

So please check if you have setup any system access rule.
Logged

सत्यमेव जयते!
mrt
Full Member
***
Offline Offline

Posts: 23


« Reply #5 on: Friday 09 April 2010, 11:36:50 pm »

Hi all,

I'm planning to convert my GW/Firewall from Clarkconnect 5.1 (ClearOS) and install the community version 2.3 and having som problems with reaching my mailserver (and bigger confusing after reading several post here about problems with portforwarding.)
I have read the  manual, tryed to "read" this, read several post here, but some says that that it must be an System access rule, other says no and it must be an Source NAT rule. Regarding to the manual, the System access rule is only to the Endian itself, and some predefined rule is working there. (efwsupport.com/index.php?topic=1065.0)

So, could someone help me out with this?


I have one Exchangeserver running on VMware INSIDE my network and want to forward port 80, 443, 25 and 21 to that server.
My Networks looks like this:

Red uplink = pppoe (public IP, e.g 88.89.123.123)
Green network (eth1=10.0.0.2)
Exchangeserver = 10.0.0.16

My forwarding rules is:              
                              
Access from                                                             Target
Type Zone/VPN/Uplink - <ANY Uplink>                     Type Zone/VPN/Uplink - Zone GREEN - IP 10.0.0.2

Filter policy: Allow

Service/Port
HTTP - TCP - 80

Translate to
IP               DNAT Policy NAT

Insert IP                Port/Range
10.0.0.16             80


And the same for port 443, 25 and 21

Is this the correct way of doing it or, what should I do, is there any other "official" HowTo on this?

Thanks alote in advance... :-)

With regards from Norway

PS, I have some screenshots if someone need it on PM
Logged
whoiam55
Full Member
***
Offline Offline

Posts: 71



WWW
« Reply #6 on: Saturday 10 April 2010, 04:12:43 am »

You are right, you should setup a port forward and not the system access rule.

The settings you posted looks ok, aren't they working?
Logged

सत्यमेव जयते!
mrt
Full Member
***
Offline Offline

Posts: 23


« Reply #7 on: Saturday 10 April 2010, 05:33:24 am »

No, it does not work. I haven't done anything else with the default setup in the Firewall setting.

I can't see anything "hit" the FW log for incoming. I see the Exchangeserver 10.0.0.16 "contact" some IP outside.

My Proxy is Off

I'm running DynDNS but haven't enable it yet due to that I have to be sure the FW forwarding rule work OK before I tell my Nameserver to point to DynDNS. So for this test I use my public IP to see if I came through to my Exchangeserver and OWA (Outlook Web Access). It should work with just the public IP, I have tested it with my ClearOS FW.

So, now I'm confused and "stucked".

Any other hints where to look ?

Regards


#UPDATE# Mine issue SOLVED: htt_://efwsupport.com/index.php?topic=1563.0
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.063 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com