Topic: Public and private urls to be the same

[xware]

Hello folks!
I have a problem to submit to you:
There it is :
I use a SME 6.01 as server-gateway with a DSL line connected via pppoe having it's own private public address.
Below the SME, I have another server, which hosts tomcat and an application which gives me a serious headache..
The problem is that the licensing system of this tomcat app is based on a static url which is defined when you unlock it. So if you want to use it both from the inside of the network and the outside of it, you MUST join it via the same URL..alas.. its is java software and the url is myip:8080/something.
So I first tried to set it up as follows :
- I used the port forwarding to forward my public ip port 8080 to my private ip's.. everything fine from the outside, and the app runs perfectly.
But from the inside, that's another matter.. I can connect to my public ip indeed, but when I call "mypublicIp:8080", it does not re-route the port to the private ip.. and I'm stuck..
And of course if I use "MyprivateIp:8080", I'm casted off the app with a licence voliation error

Has anyone an idea of what method to use in this case..?
I've spent half a day searching but I'm really stuck..

Thanks in advance for any help.
Cheers,
Phil.

[Franco]

This is because your ISP is blocking such ports.

[xware]

This is because your ISP is blocking such ports.

I don't think so.. if my ISP did block these ports, I would not access to "mypublicIp:8080" from the outside..
I think the problem is some tweaking needed in SME to allow to access from the inside to a forwarded port through the public Ip in order to be viewed by the tomcat server as coming from "mypublicIp:8080" (imho).

[Franco]

Then take a look at
/etc/e-smith/templates/etc/squid/squid.conf/20ACL15Safe_ports

after modifying you need to expand the template and restart squid.