Comment 7 for bug 1044155

I found the problem of my server.

Tt was a series of missing iptables lines who were blocking any connection attempt to whatever the port was.

So by correcting it, my server is now available from the wan side. I don't know how this lines went to the state of being erased. It may be something near to this particular soho router attack named "sql injection".

The router may run properly or may block any type of connections to it as it can go from high to low performances. This is a known hack attack who are made especially for soho routers (Ubiquiti antenna for example) Anyway that's not what i want to talk about.

Everything's fine as long as we have the apache2 config files (httpd.conf) build. So now i have my server up and running, and the proc is describe in the post i wrote about the "DD-WRT Side" is running nice it is very very stable.

But my main problem is to made my server working on a typical way it is used until now. I flashed a ubiquiti device with my domain name adress now accessible through the internet but as soon as there is something else that's where the problems occurs.

So

http://www.libresansfil.org

work good but if i made this :

http://www.libresansfil.org/login/?gw_address=192.168.5.125&gw_port=2060&gw_id=00:1D:60:6B:B3:B5&url=http%3A//www.google.com/

Yes there is a login screen and suprisingly a token coming out the server as it is known, but there is always this page with the "192.168.5.125 as been rejected" erroir. Somehow, by having my mouse over the "actualisez" part of the error page i can see the token value at the bottom of the page.

Any idea about it ?