[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipcop-devel
Subject:    [IPCop-devel] [ ipcop-Bugs-1696202 ] Port forwarding bug in 1.4.15??
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2007-04-07 21:40:04
Message-ID: E1HaIdg-000073-10 () sc8-sf-web24 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1696202, was opened at 2007-04-07 16:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1696202&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: General
Group: 1.4.15
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: John H (jhallford)
Assigned to: Nobody/Anonymous (nobody)
Summary: Port forwarding bug in 1.4.15??

Initial Comment:
Not sure, but I think I may have discovered a bug in the latest IPCOP build. I need \
to forward traffic from a given port from multiple external addresses to multiple \
internal addresses. For example:

External xxx.xxx.xxx.xx1 port 80 >> 192.168.1.240 
External xxx.xxx.xxx.xx2 port 80 >> 192.168.1.250

When adding a new rule in Port Forwarding, the first rule shown above sets up without \
any problem. When trying to setup the second, an error message saying the port is \
already in use is displayed even though different source and destination IPs are \
listed.

So, I tried to add to the existing rule. I can add another external source, but I \
cannot forward to a different internal IP. The net effect is the ability to accept \
multiple external traffic for a given port, but they all point to the same internal \
IP.

I used a prior version of IPCOP several years ago, and I am certain I was able to \
accomplish the task above without any problem (have not used IPCOP for quite some \
time due to other circumstances). The newest release does not allow it though it \
seems to me that it should. 

Anyone know if this is a bug or is this by design? If by design, how do you take, for \
example, port 21 traffic from multiple external IP's and point to different internal \
IP's? And do you know if version 1.3 allowed this?

Thanks for any help you can provide.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1696202&group_id=40604

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel


[prev in list] [next in list] [prev in thread] [next in thread]