List Info

Thread: DMZ Pinholes for VPN as a destination




DMZ Pinholes for VPN as a destination
user name
2006-03-15 01:53:10
Bugs item #1450046, was opened at 2006-03-14 20:53
Message generated for change (Tracker Item Submitted) made
by Item Submitter
You can respond by visiting: 
https://sourcefor
ge.net/tracker/?func=detail&atid=428516&aid=1450046&
amp;group_id=40604

Please note that this message will contain a full copy of
the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: User Interface
Group: 1.4.10
Status: Open
Resolution: None
Priority: 5
Submitted By: Agent Green (agentgrn)
Assigned to: Nobody/Anonymous (nobody)
Summary: DMZ Pinholes for VPN as a destination

Initial Comment:
The DMZ pinholes section needs to have an allowance for
items in the DMZ to access items outside of the VPN.

For example, I have a server in my DMZ at
192.168.16.70, which requires the ability to access
192.168.3.2 over an existing VPN link.  The IP on the
VPN can access the DMZ server fine, but not vice-versa.
 If this network were on Green or Blue, I would
configure the necessary pinhole, but a destination over
VPN is not an option.

------------------------------------------------------------
----------

You can respond by visiting: 
https://sourcefor
ge.net/tracker/?func=detail&atid=428516&aid=1450046&
amp;group_id=40604


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )