Topics

1

Installation and Upgrades / Dyndns and firewall issue

« on: July 27, 2009, 12:18:16 am »

Hi,

I'm experiencing some strange firewall behavior. Hope someone can help me sort this out:

I'm managing my Hardy box with Ebox. It is serving as (amongst others) a firewall. I'm also using dyndns.org (through ebox) for easy remote access. Running a ssh server, webserver, deluge bittorrent daemon with webinterface, firefly daap daemon with webinterface etc.

Firewall settings:

• All traffic from LAN to WAN is allowed
• All traffic between LAN and Ebox is allowed
• All traffic from Ebox to WAN is allowed
• Access from WAN to Ebox is allowed only for the ports required for above-mentioned services (e.g. ssh, http, 8112, etc.)
• I've set no rules for WAN to LAN (e.g. assuming this is all blocked by default)

I can access all these services from the LAN using the server's 10.0.0.1 IP address I have assigned to it. For example, going to http://10.0.0.1:8112 will give me the Deluge webui and ssh to 10.0.0.1 works.
I can also access all these services from remote locations by using the dyndns address. E.g. going to http://myname.dyndns.org:8112 will give me the Deluge webui and ssh to myname.dyndns.org also works just fine.

What I cannot do is use the dyndns URLs from inside the local area network. All services time out (firefox saying "connecting to http://myname.dyndns.org:8112"). The only service for which the dyndns URLs work from the LAN and WAN is the regular Apache webserver (e.g. port 80).

To me this looks like a firewall configuration issue. What do I need to change to be able to use the dyndns URL from inside the internal network?

Thanks!

p.s. other than this small issue, Ebox is great!