Port forwarding is not working

Saleem · 06-17-2009, 02:40 AM

Hi,
I am using 6.2.0~svn20090527r23446release6.2-1lenny

My network setup:
Modem (complete bridge mode) -> Untangle (Router mode) -> Switches -> PC

I've followed the http://wiki.untangle.com/index.php/P...shooting_Guide 9 steps and doing the 10th step now.

I have created a port forward to forward port 8080 to a local server.

It is not working.

Other port forwards are working fine. (I did a new port forward to 8083 and for the same machine and it is working fine!!)

Please find the attached screen shot.

mdh · 06-17-2009, 04:13 AM

Try adding SOURCE INTERFACE = EXTERNAL. As you have it, external accesses on port 8080 are supposed to go to that same port on the private address. That's probably what you planned on, but I'm just mentioning it to be safe.

Saleem · 06-17-2009, 04:40 AM

Added that, still no go

WebFooL · 06-17-2009, 05:05 AM

The portforward looks good.
Dose the host (1.14) have any firewall?

Saleem · 06-17-2009, 05:39 AM

No it doesn't have any firewall. And the url works internally (192.168.1.14:8080). Where as accessing it from outside, domain.name:8080 isn't working. The request is not even showing up in the tcpdump. I have tried,

tcpdump -i eth0 -n "port 8080"
tcpdump -i eth1 -n "port 8080"

both of them are blank. May be 8080 is used by the Untangle itself?

WebFooL · 06-17-2009, 05:44 AM

try the external IP and 8080
What type of traffice is it http/tcp &udp? or is it some other?

Do you have the firewall module installd in Untangle.
Is it a windows box?

Saleem · 06-17-2009, 05:51 AM

Tried with external ip, still no go. It is http traffic with tcp. Jboss is running on the 192.168.1.14 machine. It is a Cent OS 5.2 box with JBoss.

Saleem · 06-18-2009, 12:10 AM

Well, After forwarding port 8080 and checking in canyouseeme.org reports that the connection is refused. Is port no 8080 used by anything/blocked by default in untangle?

dmorris · 06-18-2009, 01:10 AM

Quote:

Originally Posted by Saleem

tcpdump -i eth0 -n "port 8080"
tcpdump -i eth1 -n "port 8080"

both of them are blank. May be 8080 is used by the Untangle itself?

if tcpdump isn't even seeing it on eth0 then something upstream must be blocking it. tcpdump basically listens right at the wire before anything in untangle would have a chance to even block it.

try testing it from inside.
or try disabling the rule and running 'nc -l -p 8080' (or something like that) to start listening on port 8080
then try to connect from outside

Saleem · 06-18-2009, 04:38 AM

Ok, My Bad. Apparently my ISP was blocking the port 8080 saying to prevent the viruses from spreading. I don't know how they can do this to an enterprise pipe. Anyway I've sent an email to unblock it and it is working beautifully.

Thanks for your time and sorry for wasting it, my bad.

<3 Untangle

06-17-2009, 04:13 AM	#2 (permalink)
mdh Join Date: Aug 2007 URLs submitted: 171 Posts: 4,535	Try adding SOURCE INTERFACE = EXTERNAL. As you have it, external accesses on port 8080 are supposed to go to that same port on the private address. That's probably what you planned on, but I'm just mentioning it to be safe. __________________ This space reserved for profound thought.....which does happen on occasion."

06-17-2009, 05:05 AM	#4 (permalink)
WebFooL Join Date: Jan 2009 Location: Sweden (Eskilstuna) URLs submitted: 57 Posts: 2,172	The portforward looks good. Dose the host (1.14) have any firewall? __________________ "Of all the things I've lost, I miss my mind the most" Video Showing 7.1 Alpha: http://fakenews.se/ut/

06-17-2009, 05:44 AM	#6 (permalink)
WebFooL Join Date: Jan 2009 Location: Sweden (Eskilstuna) URLs submitted: 57 Posts: 2,172	try the external IP and 8080 What type of traffice is it http/tcp &udp? or is it some other? Do you have the firewall module installd in Untangle. Is it a windows box? __________________ "Of all the things I've lost, I miss my mind the most" Video Showing 7.1 Alpha: http://fakenews.se/ut/

06-17-2009, 04:40 AM	#3 (permalink)
Saleem Untangler Join Date: Sep 2008 URLs submitted: 15 Posts: 75	Added that, still no go

06-17-2009, 05:39 AM	#5 (permalink)
Saleem Untangler Join Date: Sep 2008 URLs submitted: 15 Posts: 75	No it doesn't have any firewall. And the url works internally (192.168.1.14:8080). Where as accessing it from outside, domain.name:8080 isn't working. The request is not even showing up in the tcpdump. I have tried, tcpdump -i eth0 -n "port 8080" tcpdump -i eth1 -n "port 8080" both of them are blank. May be 8080 is used by the Untangle itself?

06-17-2009, 05:51 AM	#7 (permalink)
Saleem Untangler Join Date: Sep 2008 URLs submitted: 15 Posts: 75	Tried with external ip, still no go. It is http traffic with tcp. Jboss is running on the 192.168.1.14 machine. It is a Cent OS 5.2 box with JBoss.

06-18-2009, 12:10 AM	#8 (permalink)
Saleem Untangler Join Date: Sep 2008 URLs submitted: 15 Posts: 75	Well, After forwarding port 8080 and checking in canyouseeme.org reports that the connection is refused. Is port no 8080 used by anything/blocked by default in untangle?

06-18-2009, 04:38 AM	#10 (permalink)
Saleem Untangler Join Date: Sep 2008 URLs submitted: 15 Posts: 75	Ok, My Bad. Apparently my ISP was blocking the port 8080 saying to prevent the viruses from spreading. I don't know how they can do this to an enterprise pipe. Anyway I've sent an email to unblock it and it is working beautifully. Thanks for your time and sorry for wasting it, my bad. <3 Untangle