have you tried traceroute to see where your packets are getting lost?
________________________________ From: Johan Boshoff <[EMAIL PROTECTED]> To: eBox users <[email protected]> Sent: Tuesday, 11 November, 2008 14:13:06 Subject: Re: [Ebox-user] Port forwarding Yes, I have, I also tried to first redirect to the other interface eth1 and then to 200.200.200.150, but nothing. It is very strange as all my other redirections works 100%. I know how to set it up…but this one is different. Johan ________________________________ From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of nicolas diogo Sent: 11 November 2008 04:03 PM To: eBox users Subject: Re: [Ebox-user] Port forwarding have you created a redirection like firewall > redirects, and then: interface = <your external nic - connected to netgear: 192.168.0.X > external port = 1234 protocal = tcp (maybe udp) ip address = 200.200.200.150 (echoServer) port = 1234 ________________________________ From:Johan Boshoff <[EMAIL PROTECTED]> To: eBox users <[email protected]> Sent: Tuesday, 11 November, 2008 13:20:33 Subject: [Ebox-user] Port forwarding Good day, I am running the latest EBOX 0.12 on a small network. We have a capped ADSL account with no static IP addresses with a Netgear Router. The EBOX server acts as a proxy server connected straight into the Netgear Router and the other point in the switch where all the rest of the computers are linked to. I have set up EBOX so that I can administer it via the interface and via SSH with a dynamic dns account from dyndns.org. This is all working. I am allowing all squid requests with no content filtering. The squid’s port is set to 8080. I now have a PC on the network running Echo Server – remote desktop server (www.echogent.com). This program is set up to run on port 1234. For those who do not know how this Echo server works, please visit the website. It is really cool! Anyway, once your Echo server is running, you can test it to see if the outside world can connect to it via InstantVNC. Basically the client connects with InstantVNC and once they are connected to the Echo Server, I can run a VNC program connecting to their PC’s for remote support, file transfer, etc. Before the EBOX server came in place this was working fine. Obviously I needed to change a few things, so this is what I did. 1. Netgear Router – IP 192.168.0.1 On here I have added a service for the Echo server to forward to the external ebox IP address on port 1234. 1. Ebox On here I have created a port forwarding from eth0 wioth port 1234 to forward the request to my PC with IP 200.200..200.150 on the same port 1234. When I test the Echo server, it tells me that the connection timed out. How canI trouble shoot this as I have tried different ports, different firewall rules, but nothing. Please help. Thanks, Johan
_______________________________________________ Ebox-user mailing list [email protected] https://lists.warp.es/mailman/listinfo/ebox-user
