Topic: 2 Question, Upgrade Apache to v2 and change listening port

[girkers]

I am interested how to upgrade to Apache 2 with versin 6.01 of SME.

And/Or

My ISP is blocking port 80 so I want to change it to something else.  I have looked at the how to by Dan Brown but this doesn't work for this version.  Any help would be appreciated.

Thanks.

[NickR]

To change the default port, you need a custom template:
(This is untested, but it should work)

mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf

cp /etc/e-smith/templates/etc/httpd/conf/httpd.conf/35Listen80 \
/etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/.

mcedit /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/30Listen80

Change the port in the first & last line of the fragment to the one you want (eg. 85).

/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf

service httpd restart

You'll also need to open that port to allow external connections - do a search for the port opening contrib on here.

[schirrms]

Hi,

Maybe another (untested by me on 6.0, worked fine on 5.5) way :

Just let your web server on the 80 port, and do a iptables redirection : for instance, tell that all incoming connections to 8080 are to send back to 80.

HTH,

[girkers]

Thanks schirrms for your thoughts and it would make things really easy, but the problem is that my ISP doesn't let port 80 through, but thanks for the thought.

NickR thanks, I will give that a go, I know how to do the port forwarding on my router, so once I do the change to SME server I will let you guys know how it goes.

[SSBN]

Go to www.no-ip.com when you have your web server on another port. They will allow you to host DNS to web page on a nonstandard port and let the rest of the world se it. It is free as well.

[girkers]

Thanks SSBN, I am already using DYNDNS.org so thanks for the thought.

[schirrms]

Thanks schirrms for your thoughts and it would make things really easy, but the problem is that my ISP doesn't let port 80 through, but thanks for the thought.

NickR thanks, I will give that a go, I know how to do the port forwarding on my router, so once I do the change to SME server I will let you guys know how it goes.

OK, that a common problem with my great English
Let's try to explain better :
On your SME box, just let the web server running at port 80.
From your inside network, you can access your web server on port 80
With IPTABLES (I don't know if port forwarding will let you do that), create a rule telling that every incoming connections on port 8080 (for instance) are redirected on port 80.
So, people trying to access your web server have to connect to
http://{your server}.dyndns.org:8080/
On your server, IPTABLES connect each incoming session on the 8080 port to your web server (still running on port 80).

That was the idea.
(But i think that the solution via dyndns.org is smarter, maybe).

Regards,

[girkers]

I have a Netgear WGT624 and unfortunately this does not allow port mapping.

I have copied 35Listen80 to the correct directory and editted it as directed and restarted httpd, but I still can not connect.

Any other thoughts?

Thanks in advanced

[Anonymous]

I worked it out, it is much simpler than I thought.

There is a file called 05Port with one line in it:

Port 80

I have simpled changed this to the port I wanted and internally I can now access my webserver through this port.

Internally I access the server through 192.168.0.10:8043

But when I try to access the server externally I get an "Invalid Syntax Error" and page can not be displayed, so one problem is solved, but another has been created.

Is there anyway I can track where the connection is being stopped.

For reference the links is:
http://www.girkers.kicks-ass.net:8043

[girkers]

I worked it out, it is much simpler than I thought.

There is a file called 05Port with one line in it:

Port 80

I have simpled changed this to the port I wanted and internally I can now access my webserver through this port.

Internally I access the server through 192.168.0.10:8043

But when I try to access the server externally I get an "Invalid Syntax Error" and page can not be displayed, so one problem is solved, but another has been created.

Is there anyway I can track where the connection is being stopped.

For reference the links is:
http://www.girkers.kicks-ass.net:8043

This was actually posted by me, sorry.

[girkers]

The problem with having a modem/router and a Wireless Router.  Stupid me was not forwarding the packets from my modem.

[waterboy]

Thanks schirrms for your thoughts and it would make things really easy, but the problem is that my ISP doesn't let port 80 through, but thanks for the thought.

NickR thanks, I will give that a go, I know how to do the port forwarding on my router, so once I do the change to SME server I will let you guys know how it goes.

OK, that a common problem with my great English :-)
Let's try to explain better :
On your SME box, just let the web server running at port 80.
From your inside network, you can access your web server on port 80
With IPTABLES (I don't know if port forwarding will let you do that), create a rule telling that every incoming connections on port 8080 (for instance) are redirected on port 80.
So, people trying to access your web server have to connect to
http://{your server}.dyndns.org:8080/
On your server, IPTABLES connect each incoming session on the 8080 port to your web server (still running on port 80).

That was the idea.
(But i think that the solution via dyndns.org is smarter, maybe).

Regards,

Can any iptables guru out there let me know how to do exactly what has been described here?  My SME box is my Internet/PPPoE gateway so I would like to have all requests coming in on port 8080 get redirected to port 80.  I'm not quite sure what IP to redirect the requests to since there is no other server, my SME server is the only one on my network.  If I can get this to work in conjunction with the dyndns.org redirect service I will have outsmarted my ISP who blocks inbound port 80.

Thanks!

[waterboy]

I figured it out.  For those interested, this rule got it for me:

iptables -t nat -A PREROUTING -p tcp --dport 8080 -j REDIRECT --to-port 80

[splunk]

That works for me, the iptables thing.  Been using it since I got my fios.  Is there anyway to have the server automatically configure like that.  Anytime I reboot I have to ssh in and re-enter it.

[splunk]

I've been using the iptables thing too to get around a blocked port.  

Now, my question is, is there a way to have the server run...

iptables -t nat -A PREROUTING -p tcp --dport 8080 -j REDIRECT --to-port 80

...automatically everytime it boots up so that I don't have to do it myself?  It'd be really convienient, especially when the power goes out longer than the UPS can back up, so that when my server restarts itself, it'd be back to normal.

Thanks.

[gordonr]

My ISP is blocking port 80 so I want to change it to something else.  I have looked at the how to by Dan Brown but this doesn't work for this version.  Any help would be appreciated.

Thanks.

Leave the web server listening on port 80. On the port-forwarding panel, forward port 8080 (or whatever) to  port 80. In 6.0, the destination IP must be your ExternalIP. For 7.0, you can enter any of "localhost", ExternalIP, InternalIP, or 127.0.0.1 for such redirects.

Gordon

[splunk]

Leave the web server listening on port 80. On the port-forwarding panel, forward port 8080 (or whatever) to  port 80. In 6.0, the destination IP must be your ExternalIP. For 7.0, you can enter any of "localhost", ExternalIP, InternalIP, or 127.0.0.1 for such redirects.

Gordon

Since I'm on 6.0 and have a dynamic IP, I can't use this method.  I'm hoping someone can pop in with a way to automatically run the iptables thing on startup.

[gordonr]

Since I'm on 6.0 and have a dynamic IP, I can't use this method.  I'm hoping someone can pop in with a way to automatically run the iptables thing on startup.

I haven't tested, but it's quite likely that the 7.0 e-smith-portforwarding version will work on 6.0. However, it plays with firewall rules, so they need to be checked carefully.

[splunk]

I tried installing some of the rpms for the portforwarding, but they stated I must have an esmith library newer than what I did.  Any other clues?

[CharlieBrady]

Thanks schirrms for your thoughts and it would make things really easy, but the problem is that my ISP doesn't let port 80 through, but thanks for the thought.

Your ISP doesn't need to, if you follow Pascal's advice. All traffic which flows through your ISP would be on port 8080. Apache would still listen on port 80. Iptables would connect the two. All you would need would be to enter a port forward in the port forwarding panel.

However...

The 6.0 and 6.0.1 versions of the portforwarding panel don't correctly support portforwarding to a port on the server itself. You'll need to use an updated version of e-smith-portforwarding (IIRC) to have it work.

[splunk]

I wasn't able to get any of those running on 6.x.  Is there any way to have the server automatically run an iptable command upon boot?


Thanks