EFW Support
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email?
Sunday 24 November 2024, 12:30:44 am
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Visit the official Endian Community Mailinglist
HERE
14258
Posts in
4377
Topics by
6517
Members
Latest Member:
Sandro
Search:
Advanced search
EFW Support
Support
General Support
Internal access to internal server through External IP (loopback NAT)
0 Members and 0 Guests are viewing this topic.
« previous
next »
Pages:
[
1
]
Author
Topic: Internal access to internal server through External IP (loopback NAT) (Read 18989 times)
maxim
Full Member
Offline
Posts: 23
This forum was a waste of time.
Internal access to internal server through External IP (loopback NAT)
«
on:
Tuesday 09 March 2010, 01:22:08 pm »
Ok, server located at 192.168.0.6
I am located at 192.168.0.253.
The port is 80.
Port forwarding setup from red:80 to 192.168.0.6:80.
Access red:80 from green, EFW somehow translates that to access to the GREEN interface, but at the IP of red.
So in my browser is the RED IP, and on my screen is EFW's web login screen which is not available from RED.
I want to be able to access the service on 192.168.0.6 through normal means, without jumping through hoops such at modifying my hosts file, or setting up a hosts record on EFW.
Logged
rwebb616
Full Member
Offline
Posts: 16
Re: External access to internal server (loopback NAT)
«
Reply #1 on:
Thursday 11 March 2010, 05:14:50 am »
I didn't see your post before I posted mine - I'm having the same issue. I did not have the problem in 2.1.2. Generally speaking 2.3 seems to be quite a bit more buggy than 2.1.2 was. I'm having problems with the DHCP settings as well - which is apparently fixed in 2.3.1 but I don't have a way to get that either.
-Rich
Logged
Steve
Sr. Member
Offline
Posts: 108
Re: External access to internal server (loopback NAT)
«
Reply #2 on:
Thursday 11 March 2010, 10:07:30 am »
If I understand your problem correctly,
You want to access your Internal webserver (On Green) from another machine on the Green network,
BUT you want to use your Public IP address.
In Firewall > Port forwarding / NAT > Destination NAT
Try this:
Logged
rwebb616
Full Member
Offline
Posts: 16
Re: External access to internal server (loopback NAT)
«
Reply #3 on:
Thursday 11 March 2010, 10:50:50 am »
It looks like I was able to get it to work by adding a source nat rule:
Network: 192.168.x.0/24
Destination: GREEN
Service: <ANY>
Nat To: Auto
The GREEN network in this case would be the same as the network.
I don't know why this is needed or works, but it does.
-Rich
Logged
maxim
Full Member
Offline
Posts: 23
This forum was a waste of time.
Re: External access to internal server (loopback NAT)
«
Reply #4 on:
Friday 12 March 2010, 01:51:20 pm »
I have applied both of these settings. The behavior is still the same. I find the behavior very odd. Thank you for your replies. I'll be installing some new hardware this weekend with 2.3 Final on it. The current system I have has 2.3RC1.
Logged
maxim
Full Member
Offline
Posts: 23
This forum was a waste of time.
Re: Internal access to internal server through External IP (loopback NAT)
«
Reply #5 on:
Saturday 08 May 2010, 04:40:21 am »
I finally got around to swapping out the hardware today and the 2.3 final doesn't not appear to have an issue performing this task.
Logged
kboddy
Jr. Member
Offline
Posts: 4
Re: Internal access to internal server through External IP (loopback NAT)
«
Reply #6 on:
Friday 28 May 2010, 02:16:44 am »
Hi there,
Just looking for the official setup instructions to do this. I've tried what was posted, but to no avail. It also looks like the above admin post is missing info?
Thanks,
K
EDIT: I applied both the Destination NAT rule above (image), and the SNAT rule above to get this to work. It is now working. Thanks!!!
Logged
whoiam55
Full Member
Offline
Posts: 71
Re: Internal access to internal server through External IP (loopback NAT)
«
Reply #7 on:
Friday 04 June 2010, 02:11:59 am »
Quote from: Steve on Thursday 11 March 2010, 10:07:30 am
In Firewall > Port forwarding / NAT > Destination NAT
Try this:
should not it be 10443 port instead of 443 as Endian uses 10443?
Logged
सत्यमेव जयते!
Pages:
[
1
]
« previous
next »
Jump to:
Please select a destination:
-----------------------------
Announcements
-----------------------------
=> Project News
=> Latest News and Updates
-----------------------------
Support
-----------------------------
=> General Support
=> Installation Support
=> EFW SMTP, HTTP, SIP, FTP Proxy Support
=> VPN Support
=> Hardware Support
-----------------------------
Development
-----------------------------
=> EFW Wishlist
=> Contribute Your Customisations & Modifications
Page created in 0.109 seconds with 19 queries.
Powered by SMF 1.1 RC2
|
SMF © 2001-2005, Lewis Media
Design by
7dana.com