Acess apache remotely on slackware 13.1

bathory · 11-15-2010, 01:25 PM

I cannot think of something that has changed between Slackware 12.0 and 13.1, that is responsible for this behavior, except maybe iptables.
But as you said, even with blank iptables, you can't connect to the webserver.
Can you ftp to your server now? Because ftp is more tricky that http, as you have to open 2 port on the firewall!

Willian · 11-17-2010, 08:16 AM

I will make some tests here install slackware12 and 13.1 and analyze it I will leave the thread open for some days (till I end the tests) and I will return the results.

Thanks Mr(s).

Willian · 11-19-2010, 01:35 PM

Every time when I boot my computer I have to type ifconfig eth0 0.0.0.0 and after pppoe-start, I was thinking about it, it could be a problem ?

Apache works on Debian, Slackware 12, Windows and OpenSUSE but on slackware 13.1 no.
The unique diference is what I said about ifconfig. All configurations was the default for setup apache.

Thanks

bathory · 11-19-2010, 03:45 PM

Could be. When apache starts is binds on port 80 on every available interface (assuming that you use the "Listen 80" directive).
After running ifconfig and pppoe-start you get a new interface and a different IP address for eth0.
So stop/start apache to make it bind again on port 80 of the new interfaces.

Willian · 11-20-2010, 12:18 PM

I have ever started apache after to connect.

bathory · 11-20-2010, 04:03 PM

Hi,

Please confirm if the following procedure is correct and what you get each time:

1. Slackware boots and as root you have to run:

Code:

ifconfig eth0 0.0.0.0
pppoe-start

Whats gives:

Code:

ifconfig -a
iptables -L

2. You stop and the start apache.

Code:

/etc/rc.d/rc.httpd stop
/etc/rc.d/rc.httpd start

Whats is the output of:

Code:

netstat -tanpl|grep httpd

BTW, do you really need to run that ifconfig command at startup? I've never used a ppoe connection, but looking here at LQ I've found this thread about ppoe. Take a look at eth0 settings, because I think your initial ifconfig command is wrong and it's responsible for this situation.

Regards