Linux Webserver - Apache Configuration Assistance, please!!

Got it connected to the Linux box, and it works (I'm amazed)!

I'm currently installing all the updates I can get my grubby little paws on, then I'll start working on getting the server running. I'll have to do a little network trickery for that to happen, though (tell thr router to let such and such IP through, the firewall, then figure out how to tell Linux that).

The access point works great, going to order a switch soon. One small hitch, it decided that it wanted to play router, and the battle between the router and access point was heated (crashed the network), but I think it is fixed now

I'm also going to sign up for a no-ip account...

This Linux stuff is prety nice (comes with great games too!), although I'm sticking with Windows on the other computers

 

This is posted from the Linux box! Wohoo!

It still is no replacement for Windows, but it does work prety well.

I like windows updare much better, this updater is slow and unstable

I have regestered with no-ip.com, and I'm proceeding to work on getting the right stuff downloaded.

One thing in Mozilla's favor, the smilies don't freeze Going to have to fix this refresh rate, though, I'm getting a headache from it

Signing out, live from the Linux box...

 

Ok, I have everything ready to go (hardware), but I don't have the faintest clue as to how to set it up!!!

What do I do? I'm using No-IP free, and trying to figure out:

A. How to install mysql
B. How to configure Apachie
C. How to install the No-IP client!

Any guides out there?

Thanks in advance for your help!

I did order the switch, it should be here by the end of the week

 

Looking at the noip v2.0.7 package it looks pretty straight forward... copy and untar the package to your favorite directory (tar -xzvf noip-duc-linux.tar.gz will do the trick) ... run 'make' and 'make install' (you must be root for the make install). This and everything else you'd need to know is located in the ./noip-2.0.7/README.FIRST file that comes with the package... looks pretty straight forward...

Give me some more specifics as to what you are trying to configure on this and i'll shoot you the directives you need to add tothe httpd.conf file to get it going the way you want. Its fairly simple but the shear length can make look scary. Apache's site is pretty complicated for the noob trying to sort through all the possible directives, they throw all the basic stuff in with the more advanced.

Also what version of Apache are you using? Just out of curiosity more than anything relavant.

I could be wrong but i seem to remember wiht RH there being an option to install MSQL from the install cd. You can pop your CD back in, boot from it and go through the upgrade option to look for uninstalled packages. Other than that i'm of no help at all with it.

 

I did all the make and make install, but it doesn't appear to do anything! I still can't run the program.

I prety much need to know alot about configuring apache, what IP address to use, etc. I honestly have no clue. Any guides would be apreciated I am using the version that came with RedHat 8, Apache HTTP server 2.0, according to website.

I installed everything, and the only database stuff I can see is ProtegeSQL, or some such thing.

I realy am new to this kind of thing, so a step by step guide for dummies would be realy good

 

Ok, I'm stupid

When I installed Linux, I didn't chose server install, so MySQL was not a option.

I happened to mess the system up prety bad, so I ended up reloading, selected server install, and boom, there in plain sight is MySQL!

I have been wresling with my access point, the tech support people say that I'm the first person they know of that has tried this, and it seems to work most of the time, but it randomly decides not to work, requireing a reset of both the access point and the router. I am going to do a couple firmware upgrades, and try again later.

I could use some (more) help with configuring apache, as far as what IP address to use, the domain alias, NS info, etc. I know nothing about such stuff

Thanks!

Got to go attend to daily life

 

Rl got in the way of things for me as well... for the basics of the webserver you should be able to leave most of the httpd.conf alone... as far as the ip address... you can generally leave it default so it answers any requests forwarded to it.
The virtual host stuff is very straight forward...
heres a snip from my running httpd.conf file for the virtual hosts


#
# Use name-based virtual hosting.
#
NameVirtualHost *

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
<VirtualHost *>
ServerAdmin webmaster@hardwarehacking.com
DocumentRoot /home/dave/www/hh/
ServerName www.hardwarehacking.com
ErrorLog /var/log/apache/hh.com.error_log
CustomLog /var/log/apache/hh.com.custom_log common
</VirtualHost>

<VirtualHost *>
ServerAdmin webmaster@partnersforever.net
DocumentRoot /home/dave/www/pf/
ServerName www.partnersforever.net
ErrorLog /var/log/apache/pf.net.error_log
CustomLog /var/log/apache/pf.net.custom_log common
</VirtualHost>

<VirtualHost *>
ServerAdmin webmaster@spiritofspringnursery.com
DocumentRoot /home/dave/www/sos/
ServerName www.spiritofspringnursery.com
ErrorLog /var/log/apache/sos.com.error_log
CustomLog /var/log/apache/sos.com.custom_log common
</VirtualHost>


and also change the ServerTokens entry to Prod for good measure... this hides the version, modules, and a lot of data about yoru server from the outside world.... telnet yourhost.com:80 and a phoney GET command will reveal everything.
ServerTokens Prod

That should get you going..... if not holler!

 

Thanks, I'll give it a try!

Finaly figured the access point out, after upgrading the firmware. I have to leave the e-mail up set to check every minute, to keep it from losing the connection with the router. Weird, and I have to do it on both computers. Something fishey is going on...

 

Ran into a similar problem with my wireless network.... I needed another PCM/CIA wireless card earlier this week (war driving is too much fun ) But after doing a little research i decided for the same price to try out a 11g card, my WAP is 11b, needless to say the 11g card is junk for this situation... it randomly decides its deaf, watching the packet count it sends just fine...but never recieves packets, back to the shop to exchange for another straight 11b card. This is all under winders..

But are you loosing conenctivety via Linux box or winders? If Linux i've got a couple of scripts that do a connectivity checking routine wiht a hook that you can set to call another script to restart things.... I used it to check on my dialup connections. But it could be easily adapted to help 'keep alive' your wireless links.

Just some thoughts....let me know how you get on with your Apache setup.

 

Linux, strangely enough, doesn't seem to lose the connection I'll have to do some testing, but the Windows computers usualy lose the connection after around 5-10 min, sometimes it retains for as long as a half hour. I had the linux computer running for around 45 minutes, and internet still worked the entire time it was on!

A "keep alive" script would be nice, though, just so that I am sure the connection will stay there

Wi-Fi is great, just some of the hardware is junk. I try to use stuff with the TI chips, as I like TI (they make good calculators ). I will definately be calling D-Link (again ).

Heh, I don't need to war drive, my neighborhood is full of id10ts!! The local broadband company offers a package where they connect your fast internet to a Linksys wireless network, configure it all, and rent you the hardware. All a good idea, but they neglect to password the routers Worse than that, they leave the routers all on the same channel, so that you may have a signal strengh war on your hands If only I had known these cases existed, I woulen't be paying for internet

The neighbors I know that have wireless networks, I go and offer to fix it all for them, letting them chose the passwords (without telling me), and the such. I won't be trying to break into their network, but It is just better to have all the Wi-Fi stuff secured.

Then the cable guys come to fix/adjust something, the owner has forgotten the password, so the guy resets the darn thing, and again, dosen't put a password on it Some people! I'm waiting for someone to sue the cable company for data loss, because a 12 year old AOL lamer who thinks they can hack decided to reformat the poor unsuspecting person's hard drive

Signing out...

 

For the Linux side of the keepalive del take a look at a daemon called pppupd... its a really simple script that you can hack pieces out of if you need to take some action if the ping times out...otherwise just to maintain connectivity you can write a short shell script (probably 2 lines) being run as a cron job to toss 5 ping packets or something at your wap or somewhere else every minute or two or what not.... As for the windoze boxes....little surprise there... and i'd not be a lot of help unless you install ActivePerl, then the same scripts would work. or you could always run a small batch file to accomplish the same the, ping this addy, maybe increase the standard packet size to ensure enough data is really sent to keep the connection alive...if response time is greater than 200ms then call this other batch file to fix things...add it as a scheduled task to run as often as needed.... But i'm sure there has to be a neater way to do the same thing with VisualBasic or somthing (of which i have no clue either)

Now as far as the war driving... its just something to do... I have a 83 mile drive each way to work and back home...so i might as well do somthing constructive, and it beats smoking half a pack of cigs each way from boredom..... so i take portions of the route differently each trip... building quite a database of 'open' AP's. I'll post them on a page for folks with just enough info.....ie GPS location and last 4 of thier MAC so they MIGHT actually be concerned enough to lock them down to some degree. More of a public service than abything else, a few more weeks and i'll have a good portion of south central WI scanned and plotted. I'm not into hijacking WLAN's or anything. Although i will admit there were a couple of times stupid windoze decided it wanted to connect to the AP and did grab an IP from a few WLANs. Switching to Kismet to run under Linux as soon as i get the time to find a decently supported card to support an external antenna, looking at an Orinco Gold setup.
Even though i am still stuck with analog dialup BS at the house... i have a full OC3, a couple of T1's, and now a 1.5 ADSL line at my disposal at the office.... so there would be no thrill in hijacking a stupid person's WLAN.

Man we've gone a ways off topic.... so ummmmm... Yeah Apache is extremely flexible and with such a small footprint you can even run multiple instances of it on the same box, thats how i ran a few sites...all the non secure stuff ran on one daemon, and another completely separate instance handled only the https stuff. Worked out great for keeping sensitive data a bit more secure.

 

Eventualy I'm hoping to get this Linux thing figured out enough, so that I can ditch my webhost, and host my own sites, probibly get a better connection if I do that (ohh, I would have an excuse ). I have 3 domains that I run, only one is active at the moment, until I make the sites for the other domains, but it would save me the frustration of having to ask another human to upgrade the PHP version (instead, I attempt to do it myself, and mess the entire computer up )

Just another experament I have going on in this wackey world of mine

Windows has been known to defect to other wireless networks, which I hate, because I have to release and renew my IP address so I can access my own network. Such a pain

One neighbor told me it was no busness of mine, offering to fix their router, and now I see the router on every once in a while, and off most of the time. I think she is turning it on only when she wants to use the internet One way to keep hackers out

Oh well...