Homemade Dot-Mac with OS X
Pages: 1, 2, 3
Setting up the Client
Go to the Network Preferences Pane and make sure your network connection is set to DHCP so that your ISP will properly assign you an IP address.
A Note About Firewalls/Routers: If your Internet connection travels though Firewall software or a Router, you may experience some trouble accessing your computer. Make sure it is set to accept inbound connections to port 80 (the default for HTTP requests). If you are using a cable/DSL router, make sure you've properly set up port forwarding (check your router's manual for instructions). Still having trouble? Check if your ISP blocks inbound connections to port 80 (some have done this because of Internet worms). If this affects you, set up your HTTP server on a different port (for example, 8080).
Now, if you've made your donation, and followed the DynDNS instructions to create your account, you need to add this account information to the Mac Dynamic DNS application. It has an easy-to-follow "wizard" that will walk you through creating the client account. Set this as your master account, turn the account on, and click "Check Now" to update your IP address with the DynDNS service. When it has communicated with the service, it will show your current IP address in the window. Don't forget to set the application's preferences to automatically update the address!
|
|
Because I don't know how often my DSL provider updates my IP, I've set the Dynamic DNS application to check my connection every 15 minutes, and notify DynDNS.org of any changes.
Important Note: Be sure that you set this application (and its background application) to launch at startup via the Login Preferences Pane.
Step 3. Starting Up Your Server
Now, go to the Network Preferences Pane and check that your computer's IP address is the same number that's listed in the Dynamic DNS application. If so, your computer is properly communicating with the DynDNS site. I can't stress how important it is that your router isn't assigning an internal IP address without proper Port Mapping.
Next, head over to the Sharing Preferences Pane. If Web Sharing is off, turn it on. If you would also like to have ftp access to your computer (I'll cover this later) enable it here.
Important Tips: While you can allow your display and HD to go to sleep, it is important to keep your entire system from going down. In the Energy Saver Preferences Pane, be sure to set "put system to sleep," to never. You should also tell the computer to restart after a power failure. One last item, you need to be sure that Login will automatically log a user in to ensure the server and Dynamic DNS software will start up. If you are concerned about security, create a auto-login account with a name like "server" that will run your Web server, but won't give anyone access to your administration or other accounts. You can always log out of this account and log back in as yourself.
|
|
Step 4. Testing 1..2..3... Can I Get a Level?
OK, here is where we find out if you have everything set up properly. Open up a Web browser and type in your DynDNS Domain Name (http://yourname.homeunix.com or whatever) and hit return. You should see this logo on a Web page:
![]()
Congrats! Your Web server is up and running.
|
Related Reading Mac OS X Pocket Reference |
Step 5. Mirror Your Settings
If your computer has multiple users with separate accounts, you need to make the same settings across each account to ensure that when people log into their account, the server will remain running. Also, be sure the DNS client launches on login to each account.
.Alan
Let's recap. We've set up our basic Web server and tested it to see that it works. We can now host our own Web pages and databases on our home computer. We can also set up our own version of iDisk, which is limited only by the storage space on our HD. In future articles, we'll complete our .Mac clone and start using it. You know what they say, "When Apple closes a door, just start looking for the window."
In Part 2, we'll add our own Web site, set upand move our own domain name, setup a Firewall, create our own version of iDisk, learn FTP, and launch our Web site.
Alan Graham is the creator of the Best of Blogs book series and is a frequent writer on the O'Reilly Network.
Return to Mac DevCenter.
You must be logged in to the O'Reilly Network to post a talkback.
Showing messages 1 through 55 of 55.
-
Against Contract?
2005-08-10 18:15:42 conradhubbard [Reply | View]
Unless I am misreading it, it looks like the user agreement for Comcast and many other ISPs directly forbids using your cable internet to host a website. Since use of service technically means agreeing to the use terms, doesn't this leave the standard user who sets up a web server using the directions included here in breach of contract?
-
home made .com article part II
2005-04-02 05:16:16 menoti [Reply | View]
Part I was very interesting, but I couldn't find part II.
I couldn't see any links to it from Part I and didn't find it in the general article listings. Seems odd and I apologize in advance if I'm just being a dork. Thanks a lot.
-
Got help...
2005-03-26 14:05:38 kathryne [Reply | View]
Thanx....someone from another forum [Apple] directed me as to what I had to do in order to get my DNS to work. So, I think that may have solved the problem.
kathryne
-
Where Oh Where???
2005-03-25 03:08:42 kathryne [Reply | View]
Please HELLLLPPPP!!!! I'm trying to add my domain address to my DNS. I got the server up and running, but I can't show the entire world my webpages, because my server is set to localhost.
I followed the instructions [DynDNS], given on your website, but can't for the life of me, figure out where the Macintosh Dynamic DNS is so that I can add my domain. Nothing I click looks like the diagram you show on your page. I'm on OS X 10.3.8. Would you please be so kind as to enlighten me where to go to find the Dynamic DNS on my computer? I'd be ever so grateful for any help! Thank you.
Regards,
Kathryne
-
This article is DANGEROUS!
2005-01-17 08:51:13 npenny [Reply | View]
I am a simple home mac hobbyist. I stumbled across this article (part 1 & 2) and followed it to the letter. Turning on Apache, setting up my router to forward port 80 requests, setting up a personal DNS address with DynDNS.org. It was all quite simple and within an hour I had a nice little "Welcome" html page served up. This was last Friday (1/14/05)
I went to bed that night and pondered over what kind of security I had since this article didn't even touch on it and resolved to look into it further the next day.
When I awoke the next morning my PowerMac was suspended in a Kernel Panic & I rebooted. Here is what I discovered:
1. My login password was no longer accepted.
I rebooted of the restore DVD & reset password.
2. Once I got in to the system, my external firewire hard drive nor my DVD drive would mount, effectively leaving me unable to back up any data.
3. My firewall settings were grayed out and it told me that there was a system error and could not start the firewall.
I started looking through all my logs. All kinds of kernel modules & services were simply GONE! Permissions were changed.
I did a little online research (on my ibook) and found where to see the Apache server logs. Lo and behold, there it was. Someone had been hammering through my system around 3:15am Saturday morning and continued to monkey with my computer until 4:30am. I sent every possible log I could find to my ISP and hopefully they will be able to do something (his isp showed up in several of the logs). I had to completely reload my system and it still acted "weird", so I zeroed out the hard drive and reloaded again. Finally, I have a stable system again. I have to change the password to every website I frequent as well as notify the bank.
This article did nothing to make me aware of the fact that I was simply handing over my system to any punk on the internet that wanted it. I've learned my lesson. I had heard how "secure" apache and Mac OSX was and I was bitten by believing it.
-
Re: This article is DANGEROUS!
2005-01-17 09:14:23 Alan Graham |
[Reply | View]
I'm sorry you were the victim of an attack...there are some real crappy people oout there, but I would point out that at the end of this piece it mentions Part 2 and setting up a Firewall.
From Part 2:
"The importance of this is simply to keep private information private and keep nasty people from nefarious tasks...A firewall is a security measure to prevent unwanted users from gaining access to a LAN (Local Area Network). Usually, a firewall consists of one computer that acts as a gateway to the Internet. All Internet traffic must pass through that computer."
...plus much more.
Again I'm sorry this happened to you, but this piece was intended to be read in two installments. I've been running my Homemade Dot Mac server for two years and I've never had a hacker penetrate my network...however as with anything...that is possible. Even browsing the web can put a computer at risk. One thing you might look at is creating a account on your machine that is dedicated to hosting, with limited permissions and access to other portions of your machine. Then just made a copy of that account on CD in case you ever have to restore it. And don't forget a firewall.
Wish you the best.
Alan -
Re: This article is DANGEROUS!
2006-02-11 03:03:23 Donaldo [Reply | View]
What this article really should have mentioned was to get an up-to-date version of Apache. Apache is very secure. It sounds however like the hacker acquired priveleges greater than what should be allocated to Apache, suggesting that Apple's out-of-the-box configuration of Apache for your system, npenny, was poor. This is in addition to your Apache being out-of-date.
Alan: A firewall wouldn't have helped if npenny's computer was compromised through Apache, which based on what he mentioned in his post, it probably was.
Readers: A firewall only blocks other systems on your network from accessing not-explicitly-exposed applications and services running on your system. This way every application is by default inaccessible, and if there is a vulnerability in one of them, they cannot be accessed by anyone on the other side of your firewall. If you want people to access your web server or any other application or service, then you must expose it to the internet, nullifying the effect of the firewall for that particular application / service.
-
Port mapping NAT network for FTP server
2005-01-06 16:32:08 countrygeek [Reply | View]
I have DSL using NAT for all the computers. I like to configure my OS X as FTP server. My ISP opened up FTP port 21 but don't know how to set up the server in my end.
Your suggestions, comments, will be most appreciated.
thanks
countrygeek
-
stand alone
2005-01-05 16:01:17 gigadiva [Reply | View]
I have a mac powerbook g4 running OS X 10.3.7. I normally connect to the internet using DSL without a router. I rely on software firewall for primary protection.
I have a web site on the www. I would like to set up a stand alone environment where I can develop and debug web forms etc. I've been researching and reading about personal web server, Apache, etc.
I need help on the basics. Where to put a "home grown" verson of my web site on the powerbook. Then how to configure what ever needs to be configured.
Your suggestions, comments, etc will be most appreciated!
gigadiva
-
problems pinging back to through my home DSL connection
2004-10-24 18:32:50 jrgruen [Reply | View]
I am trying to execute an x-window client from my home computer (mac ibook running OS_10.3), using my computer at work as the host. The host is a Mac G4, also running OS_10.3. I have x-windows working on my home ibook (X11).
The system works well at work: the application runs on the host computer, and I can x-window client at work as well.
The x-window client, however, does not work from home. I believe that is because of the firewall present on my DSL router (2wire home router). I connect to the home DSL/2wire router through an apple airport card.
To alleviate the problem I have done the following:
1) I have reset the IP address on my home ibook to one of the static addresses provided by SBC/2Wire.
2) I have created an alternative port in the 2Wire firewall router to receive incoming data.
3) I have added a command line in my httpd.config file to "listen" to port 8080 for incoming data on my home ibook. I rebooted and I can map this port and see that it is available.
Despite the above, when I try to ping from the host computer (at work) back to my static IP address, there is no echo.
It would be extremely helpful if I could use an x-window client on my home computer to do work. I would greatly appreciate some help.
Thank you very much.
Sincerely,
Jeff Gruen
jeffrey.gruen@yale.edu
-
Help Please: getting around (blocked) port 80
2003-08-10 13:15:52 anonymous2 [Reply | View]
You need to set up apache to listen on a different port. 8080 is a common choice for servers that do not have access to port 80.
Use the "Listen" directive in the httpd.conf file to cause the server to use a different IP address.
Listen 8080
Also, you'll want to investigate having your DynDNS provider redirect traffic on "www.mysite.com" to "www.mysite.com:8080". I know this is possible with Zoneedit (www.zoneedit.com). Not sure about other providers.
-
Cheap SDSL?
2003-06-03 14:40:19 anonymous2 [Reply | View]
If you know where to find a 768/768 SDSL connection (in Europe and that allows servers) for less than $580 a year (ADSL+.Mac), I'd like to know. Around here (CH), 512/512 symmetric DSL is more like $1500 a year.
-
Help Please: getting around (blocked) port 80
2003-05-27 15:38:07 kelvis [Reply | View]
I have verizon as a ISP, I wanted to get the server up and running only to find that Verizon has Port 80 blocked due to security reasons,
How can I remap this, Can I do this w/out UNIX.
I am not adept w/ UNIX so,...
Thanks
Kevin Duggan -
Help Please: getting around (blocked) port 80
2003-08-02 06:31:16 anonymous2 [Reply | View]
I have Verizon too, but they aren't blocking my port 80. -
Help Please: getting around (blocked) port 80
2003-07-17 12:51:32 anonymous2 [Reply | View]
I have verizon also and the same problem. Did you ever figure it out or anyone for that matter? -
Help Please: getting around (blocked) port 80
2003-08-10 13:12:12 anonymous2 [Reply | View]
You need to set up apache to listen on a different port. 8080 is a common choice for servers that do not have access to port 80.
Use the "Listen" directive in the httpd.conf file to cause the server to use a different IP address.
Listen 8080
Also, you'll want to investigate having your DynDNS provider redirect traffic on "www.mysite.com" to "www.mysite.com:8080". I know this is possible with Zoneedit (www.zoneedit.com). Not sure about other providers.
-
Help Please: getting around (blocked) port 80
2003-11-08 02:43:56 anonymous2 [Reply | View]
Another thing to note, at least here in the Northeast Verizon DSL uses a wonderful tool we all know and love called PPoE. If you are using PPoE with Verizon there is a slim chance your site will ever go public. This is the primary reason I ditched DSL and went back to cable. Hard to beat the routable and accessible IP. :-]
-
error trying to open my page
2003-04-06 16:20:45 anonymous2 [Reply | View]
hello, I use a client software from the no-ip website itself, the sync with the service seems to be alright. yet, my browser opens a window asking for a password to open my site with this text: "The name or password entered for area ?Login to the Router Web Configurator? on 36e.hopto.org was incorrect. Please try again."
My mac is connected to a local server in the building through a ethernet connection. i have no access to the server.
also, when i start my apache web server my web sharing stays grey (not blue, like the ftp access box, for example) and keeps on showing web sharing starting up: also, i cannot turn it down, if I want...
help! -
error trying to open my page
2003-06-26 13:38:21 anonymous2 [Reply | View]
aloha,
when i start my apache web server my web sharing stays grey (not blue, like the ftp access box, for example) and keeps on showing web sharing starting up: also, i cannot turn it down, if I want...
help!
I have the same problem.
did you find a solution?
mahalo, joseph W. Guillaume
-
Personal Web server woes
2003-02-05 08:29:25 anonymous2 [Reply | View]
Okay, I think I've done everything in the "Homemade Dot Mac" article to set up my desktop as a web server, but when I try to log on with my laptop (using my dial-up so I'm outside the LAN), I get the old "Server Not Found" message.
I'm using my Airport Snow as my router. I registered with dyndns I'm now at: <http://phreddyv.isa-geek.net> and I'm running DNS update.
I know that my ISP, ATT Broadband, is blocking Port 80, so, as reccomended in the article, I mapped Port 8080 to 10.0.1.2 and added 8080 to the Network Firewall exceptions. Do I need to change something somewhere else as well?How about the Proxies tab in the Network Prefs? There's a web Proxy option and a place to add a port. I tried adding 8080 there, but it didn't seem to make a difference.
Anyone out there have any tips on anything else I should try?
Thanks
Fred V
-
Re: Problems with Port mapping
2003-01-19 12:34:45 anonymous2 [Reply | View]
If you can see the Apache page while on your Airport network...that does sound like your problem is specific to Port Mapping. You may need to restart the Airport or the computer. It is also possible that you have a port conflict, but I doubt it.
I discovered the same problem with the Airport at one time...it was long ago and I can't remember how I fixed it...but I think it was restarting one of the two.
If you still have trouble you can email me direct.
alang@oreilly.com
-
Problems With Port Mapping
2003-01-19 10:40:00 anonymous2 [Reply | View]
Hello all. I'm using a snow airport and have followed all of the directions to get the web server end of this up and running. I have enabled DHCP on the ABS, checked share connection, and set-up the port mapping. On the iBook end, I have the webserver running, have manually input the private IP of 10.0.1.201, input the router (ABS) manually, as well as the subnet manually. All of my settings seem to match those in the article. I have registered with DynDNS.org and when I input the name I chose (http://barclay.homeunix.org) I can see my apache test page. However, nobody else can get through at all. I went to NetStat to have it try to get through and it cant. I contacted Earthlink cable support to ask if they block any ports and their answer was no. I then had them ping my public IP and they were able to do so, but when they attempted to connect via http they could not get through. I do not have the OS X firewall enabled so I'm curious as to what I am doing wrong. Any hints and/or suggestions. Feel free to try my DynDNS address because you will have better idea of the problem. Thanks!
Rick
rickzki@earthlink.net
-
Re: Apple Laptop Keyboards Unsuitable for Unix Users
2002-12-19 17:57:09 anonymous2 [Reply | View]
Actually, I'm a long time UNIX user and I dearly whish that I could remap the ctrl and caps lock keys. It has nothing to do with the Sun keyboard, it has to do with using emacs. Emacs is unbearable with the ctrl key in the current position. I don't develop on my mac because it's just to painful.
-
just a few comments
2002-12-17 13:51:44 olealf [Reply | View]
1. Great article. Thanks!
2. There are routers that support dyndns. At least mine. So you don't need to install software on your machine in that case (it took me a while to figure that out).
3. dyndns is FREE! But I think I'll give them a donation for this great service.
4. I tried to setup a mail server, with the help of a few other articles. It's not working reliable. Some mails get through some give me "host unreachable". Not sure why. I'm no Unix geek...
Thanks again!
-
Re: Apple Laptop Keyboards Unsuitable for Unix Users
2002-12-17 07:51:42 anonymous2 [Reply | View]
Idiotic... Unix Users dont want this. Only people who use the proprietary Sun keyboards... And posting this same message everywhere and then linking to your other anonymous post on slashdot... get a life!
-
Mail Server Followup...
2002-12-05 23:39:02 anonymous2 [Reply | View]
Great job on the first two articles. Very empowering. I've now got 3 sites flying from home thanks to you. Now if i only had a mail server ; )
Looking forward to the next segment.
pg
memphis
-
Client Software
2002-11-09 22:08:12 anonymous2 [Reply | View]
DynDNS.org now lists only one client for it's Custom DNS service--DNSUpdate 2.6 by Julien Jalon. MacDynDNS v1.2 by James Sentman is listed under Dynamic DNS but has a note saying that only v2 is recommended. DNSUpdate v2.6 note says it's only been tested with Jaguar. Can anyone advise as to which client should be used with OSX 10.1.5? Thanks.
BTW, Great tech article. Can't wait to start serving up my own site.
-
Fixed IP?
2002-10-04 09:58:54 anonymous2 [Reply | View]
What happens if I have a fixed IP? Do I just specify that as my name server when I get my domain? -
Fixed IP?
2002-11-01 14:57:21 sckz [Reply | View]
A fixed IP is good. If you only use your server for testing - not to host a real site - you can just type:
http"//yourIP to connect to your server. Just bookmark that link and you can use it easily.
If you want a system that routes to you server by typing a name, you need a service like described in the article. In that case: I use Open Domain Service. It works very good and it is free. Then you can type something like:
http://yourname.ods.org
Easier to remember... :) You find them at www.ods.org.
Subcribe and type in the settings your IP. You don't need the client program since your IP doesn't change.
I hope this helps you.
Grtz,
Sckz
-
Apple Laptop Keyboards Unsuitable for Unix Users
2002-09-18 02:27:42 anonymous2 [Reply | View]
Apple laptops are effectively unusable for unix users.
I am a long-time Unix user. That means I need to have the Ctrl key to the left of the A key. This is a genuine need, not merely a want; it is based upon ergonomics. The Ctrl key is heavily used in unix, and it must be easily accessable. It cannot be off in the lower left corner of the keyboard where it is difficult to get at, and where it distorts the position of your left hand such that you can't easily type other keys while holding the Ctrl key down.
Apple desktop keyboards are now all USB. They are all OK. The CapsLock key can be re-mapped into a Ctrl key.
Unfortunately, even in this modern age, all Apple laptops have built-in ADB keyboards. The ADB keyboard is broken-by-design. It is, in general, not possible to remap the CapsLock key into a Ctrl key.
There are some exceptions, but they are horrible kludges. They are
horrible kludges because the original design of the ADB keyboard was a horrible kludge. The correct solution would be for Apple to re-design their laptop motherboards to use built-in USB keyboards. This hasn't happened yet. If you run Linux, use Debian's solution. For Mac OS X users, uControl works. There are no solutions (that I know of) for either NetBSD or OpenBSD. Please note once again that the "solutions" above are in fact kludges, because of the original bad design of the ADB keyboard.
Apple is (currently) ignoring Unix users! This is not merely speculation on my part. In an on-going email exchange I am having with an Apple employee (whom I won't name) in their marketing department, the Apple marketing person directly stated to me that Apple was catering to their historic Mac customers, and is purposely ignoring the Unix market. He also claimed that Apple would soon start paying more attention to the Unix market. I won't hold my breath. Apple has been ignoring Unix users for more than 10 years. I expect that trend to continue. (Also note that my Apple contact indicated that Macs would never ship with a 3-button mouse, even though Apple intended to port almost all X-window software and deliver it either on a CD/DVD or installed directly on each Mac's hard drive. How Unix friendly is a 1-button mouse with X programs that often require 3 buttons?)
Apple has now lost two opportunities to sell me hardware. I really wanted an Apple laptop for their superior battery life, and for the PowerPC with Altivec CPU. (The Altivec is vastly superior to the x86 line for DSP.) Because I can't live with the broken-by-design built-in ADB keyboard in all Apple laptops, Sony and IBM sold me laptops instead. If Apple fixes this problem, they will sell me a PowerBook next year; if they don't, I'll still be running OpenBSD on x86 hardware, and wishing I could use a Mac.
-
Apple Laptop Keyboards Unsuitable for Unix Users
2003-08-13 20:30:05 anonymous2 [Reply | View]
How many places am I going to have to see this rant? Give it a rest politician. -
Apple Laptop Keyboards Unsuitable for Unix Users
2003-10-07 10:09:48 anonymous2 [Reply | View]
My friend, I have been using and developing with and on emacs for about 15 years now, and I can tell you that the VAST majority of emacs users get by perfectly well with control in the same row as the spacebar.
Please don't try to include all of us in your complaint to make yourself feel better. Good luck with getting apple to support keyboard remapping, though. It's a worthy goal.
-
Help with AirPort
2002-08-23 13:47:22 cartoonheroii [Reply | View]
This is a great article, I thought there was a way to do this but I couldn't find out how. I'm having a problem though. I've set everything up but I can't get me server to work with AirPort. When I connect directly to my DSL Modem I can serve web pages fine, but when I use AirPort I get a connection failure message. I have set up Port Mapping on port 80 on my base station, but it still dosn't work. If anyone has any suggestions I would appreciate them. Thank You -
RE: Help with AirPort
2002-08-29 01:39:56 coyotered [Reply | View]
Ok I was stumped all day on this one too. here's how you solve it.
your base station should be set up with NAT and DHCP. On port mapping set the public port to 80 the IP to 10.0.1.201 and the private port to 80. on your web server go to the airport tab of the network system prefs. Do not select DHCP though select manual assign 10.0.1.201 as the ip and 255.255.255.0 for the subnet mask. Assign 10.0.1.1 as the router address. (if you select DHCP and hit apply now you should get it to fill in most of this info for you. Then switch it to manual and put in the correct IP)
A couple of notes: You put 10.0.1.201 because the base station will select a dynamic ip between 10.0.1.1 and 10.0.1.200 (it may actually only be to 10.0.1.50 but put 201 just to be safe)
Second note: This is the big one, it may appear to not be working with these settings but before you tear your hair out in frustration try the following: Go to www.whatismyip.com to find out your connections public ip. then access the internet from a different subnet i.e. not your airport network. try a dial up connection if you have it. Basically from what i could gather there is some type of endless loop going on until it times out. In order to access your server from with in your airport network you need to use the private ip 10.0.1.201 . A neat little trick i just learned is to go under machines in net info manager and put in an entry for 10.0.1.201 that serves local (just copy 127.0.0.1 and change the ip and "localhost") in place of localhost you could put mydevelopementserver.dev or www.mydevserver.dev or your name what ever you like. In a web browser try http://www.mydevserver.dev and you should get your site (this only works from the machine that the netinfo database resides on).
hope this helps feel free to email me if can't get it with this angleterre at earthlink.net
Adam
-
Watch for overheating of original iMacs!
2002-08-20 22:09:38 mariox19@mac.com [Reply | View]
Regarding Energy Saver and the original iMacs, I believe there is an issue to watch for. If I'm not mistaken, it is unwise to allow the display to sleep while the rest of the computer is running.
The original iMac has no fan, and relies on convection cooling. I seem to remember an Apple tech article saying the machine will not cool properly if the display is sleeping and risks overheating.
Using the screen saver rather than display sleep circumvents this problem. -
Watch for overheating of original iMacs!
2003-08-26 12:05:18 anonymous2 [Reply | View]
My slotloading DV400SE is having CRT problems from the (no fan) overheating problem. The display will not hold at higher resolutions than 640x480. Owners Manual I believe says do not operate over 94 degrees Its 104 outside now! DOH! I have installed a fan on top of the processor now but it was too late! Damage already done! Why doesn't apple fess up up to the bad convection cooling design and help fix these iMacs?
Loved it till it failed, & failed & failed... -
Watch for overheating of original iMacs!
2003-08-10 17:53:11 anonymous2 [Reply | View]
I have come across three 2nd Generation iMacs in the last month that have failed due to issues relating to overheating. All were prodiced via Singapore. Is anybody else having problems. Note the 2nd Gneration iMacs were fanless and the failures appear to be related to cooked parts e.g. simultaneous failure of hard disk and slo loading CD, Vidoe controller etc.
-
What about mail?
2002-08-12 13:30:43 ooklac [Reply | View]
Thanks for the good article. I did this on my
iMac a couple months ago, but it's good to see that I wasn't doing it in a totally screwy way. However, one .Mac feature I'd like to implement is running my own mail server so instead of myname@mac.com I can have myname@mydomain.com. I've fiddled with sendmail according to the Terminal articles, but from looking at the man pages this seems a bit more complicated. Any ideas or places to start? Any chance you'll
cover this in a future article? -
What about mail?
2002-08-12 19:20:01 Alan Graham |
[Reply | View]
I will be covering this in a future article...
-
More secure setup...
2002-08-12 07:14:45 sfoerster [Reply | View]
I would set up to go from the DSL/Cable modem directly to the router THEN to any other hubs, etc. Most DSL/Cable routers have some sort of firewall built in. I have a NetGear RT314 which does (although I know it's not nearly as secure as a high end firewall, it seems to do the job...). The router will forward any requests to port 80 (or any others you set up) to your webserver, but other ports will be blocked there and never see your internal network... -
Re: More secure setup...
2002-08-12 07:31:32 Alan Graham |
[Reply | View]
My setup protects my internal network since the direct/external connection to the web server is wired ethernet (with a software firewall)...and the internal network is behind my router, wireless, and invisible through NAT. In a way I have a double line of protection, one through my router, and another through my Airport. It may be possible to hack my server, but I think it would be very difficult to jump from the server to the wireless network.
But hey...there are plenty of different options for any network...it just depends on the hardware/software you have.
I'll cover more advanced security in a future piece.
-
Be Careful
2002-08-10 11:16:35 ershler [Reply | View]
Be sure that the ISP you choose will allow you to run servers on your account. Most will but for an additional price.
-
Re: Nice, but...
2002-08-09 23:31:20 befletch [Reply | View]
I'm a moderately competent and relatively security conscious BSD UNIX system administrator by day, and it wouldn't scare me to serve static web content from my home iMac, if that's any comfort.
The most important thing to do on any net-connected Mac is to keep current with Software Update. Apple is doing much of the work a knowledgeable system administrator would do for you through the magic of that 'Update now' button.
Oh, and backing up your personal data (mainly your user directory) is pretty key, too.
Assuming you have those two bases covered, enabling Apache really shouldn't add much more risk than you get from having an always connected computer. Particularly so if you just use it for serving static pages. Active content (e.g. the ever popular PHP/MySQL combination) requires a little more security knowledge to do safely.
-
Nice, but...
2002-08-09 21:33:03 ethanbrand [Reply | View]
I've had my mind whirling around doing this very same thing. Thanks for the steps you took, especially how to handle the dynamic-IP problem.
But I'm curious as to how exposed this leaves your entire home network? My one reserve for heading down this path is that I'm no network admin and with little experience, I could leave open too many back doors for prying eyes to get in. Firewall software works to a point, but even that can't help a flawed web server.
Any thoughts?
- Kevin McGinley








