Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm lucky enough to have a static IP, but my ISP blocks my server on port 80 so I've got it on 5000, FYI.
Anyway, I'm behind the same router as my server, and when I try to access anywhere on my site, it absolutely crawls. It DOES work, but only in the technical sense of the word. I go over to my friend's place and its remarkably fast in comparison. Its pretty annoying, but not entirely unexpected.
I had read something that routers (And mines just the basic LAN/WAN router) can't operate in full duplex, which would make sense of why it works better from another IP.
Does anybody have any insight into this or some suggestions to fix this?
If you've got anything to share it would be greatly appreciated.
Are you trying to connect to your static (external) IP? or to the LAN IP of the webserver? The first one does cause some weird TCP behavior behind a router, that I could explain in detail if you'd like.
Both, and I'm sorry I forgot to mention that I'd done that. BUT you got me to look into it again, and it seems as if it WANTS to work, but it also wants me to pull my hair out.
I'm not quite sure how to describe it, so let me run thru it like this:
What is fast: I hit up 192.168.0.3:5000/06art/ drops me into a directory full of 600k-sized images that load like, awesome man.
What isn't fast: it seems like my server keeps wanting to forward me thru my domain name, and its not just dynamic content either i.e., if I put 192.168.0.3:5000/06art instead of 192.168.0.3:5000/06art/ I get forwarded and the very same content downloads like butt.
So, I can't figure out how access mambo without being forwarded through my domain. (wth?)
If you've got anything on this, I'll worship you. Also, I would actually like to hear about TCP cos' I'm just that kind of guy, but it sounds like it'll be bit lengthy tho so you can spare your fingers if you like.
Well, you're basically describing typical Apache behavior, but I honestly don't know how to fix it. I've encountered it on my own machines before. One thing you could try is putting the hostname of the apache server in your /etc/hosts file.
When you access a directory without a trailing "/", Apache needs to send what is called a redirect to the client to tell it to add the trailing slash. If it did not do so, relative URLs would not work properly. When it sends the redirect, it needs to know the name of the server so that it can include it in the redirect. There are two ways for Apache to find this out; either it can guess, or you can tell it. If your DNS is configured correctly, it can normally guess without any problems. If it is not, however, then you need to tell it.
Add a ServerName directive to the config file to tell it what the domain name of the server is.
The other thing that can occasionally cause this symptom is a misunderstanding of the Alias directive, resulting in an alias working with a trailing slash, and not without one. The Alias directive is very literal, and aliases what you tell it to. Consider the following example:
Alias /example/ /home/www/example/
The above directive creates an alias for URLs starting with /example/, but does not alias URLs starting with /example. That is to say, a URL such as http://servername.com/example/ will get the desired content, but a URL such as http://servername.com/example will result in a "file not found" error.
The following Alias, on the other hand, will work for both cases:
This all does makes sense. I'm running late tonight but I'll be working on this tomorrow for damn sure, and will be back with results (of some sort). Thanks, you guys are awesome, and I wholeheartedly apologize for my stupid bump. But thanks again.
Last edited by cyngallery; 08-19-2006 at 06:40 PM.
Sorry to have been the n00b to never reply, I do appreciate the responses.
Its taken some time to get around to, but I have taken a look into everything thats been mentioned here, to no avail.
Whoever may stumble upon this however, I think I've found at least some solution for this, in running another instance of apache bound to a different port that utilizes the exact same assets. This way when I access 192.168.0.3, I'll only remain on the connection to the IP in my network, bypassing anything that so much as references the domain.
Supposedly this is how it will work. I'll be working on this during the week and I'll document my findings, because surely (hopefully) I'm not the only one thats plagued by this.