SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0004340: DNAT and routing issue - MantisBT

Endian Issue Tracker

Please see now our new Bugtracker system: JIRA

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0004340

Endian Firewall

Firewall (iptables)

public

2012-04-26 11:34

Reporter

amitk

Assigned To

Priority

normal

Severity

minor

Reproducibility

always

Status

new

Resolution

open

Platform

OS Version

Product Version

2.4.1

Target Version

Fixed in Version

Summary

0004340: DNAT and routing issue

Description

I have got stuck in a problem. I have mapped a private ip of webserver (192.168.100.10) which is in DMZ zone, with public ip say 14.x.x.x. in DNAT/Portforwading rules. So any user coming to eth1 (RED) interface with the destination of that public ip is Dnated to private ip successfully and can browse successfully.

But what if internal client would like to access website using the public IP say 14.x.x.x. client is not able to browse that website. Problem might be with the DNAT rule.

But below tracerouter clearly show that destination is getting DNATed. But not able to browse.

C:\Users\Amit>tracert -w 200 -d 14.x.x.x

Tracing route to 164.100.31.118 over a maximum of 30 hops

1 15 ms <1 ms <1 ms "endian green interface ip"
2 1 ms <1 ms 1 ms 192.168.100.10

Is there any workaround. so that internal clients accessing that website can be Dnated.

Issue History
Date Modified	Username	Field	Change
2012-04-26 11:34	amitk	New Issue

Relationships

Notes
There are no notes attached to this issue.