MyHomeNetwork

Webs: Faemalia -:- Greatprawn -:- Playground -:- Technical -:- Tweak
Technical Web Sections: Register -:- Users -:- Changes -:- Index -:- Search -:- Statistics

Update December 2004. Wow. It sure is funny to read all that. That's the way it was about half a decade ago, I guess.

These days I use a Netgear wireless router as my firewall, with a couple of ports punched through to my Debian/SPARC Linux box running on an Ultra5.

Inside my network lives an 800MHz Linux box (Yeh, December 2004, an 800MHz Linux box is my main workstation -- I'm not a gamer. That should be obvious), a 500 MHz Linux box that isn't even plugged in due to its RAID finally flaking out (IBM Deskstar drives from a bad batch it would appear. I went through four of them before finally just giving up on it), and a 2.7GHz Win32 box that does Blender, FlightGear, and Faemalia.ThereInc's 3D client. There is a litany of little laptops that sit around doing whatever I like, too.

I've got MySQL's distributed database running on these machines, which is pretty funny if you think about it.

--
PhiloVivero

cool...

1. setup a 'firewall' machine in my home. put it out there on the web. it's still http://faemalia.org to y'all, but it's a different machine entirely. no more accounts, sorry... maybe will set that up again in a while. thanks go out to the Nickster for the name of the computer: HandOfGod?.

2. setup apache on that machine to proxy to my internal machine. therefore if you try going to http://faemalia.org you will be proxied through to my internal machine which actually serves up the content.

3. did a neato /etc/hosts trick so that the wiki wouldn't stop working. this was because I had dynamic DNS. you wouldn't have to worry if you don't.

4. TimBishop? will tell you that it's not too bad to setup Apache to do proxyservering in this manner. for me, it was a matter of reading the online documentation for about 15-20 minutes, then adding some lines to make it all work: 

Listen PORT
NameVirtualHost EXTERNAL_IP:PORT
<< VirtualHost EXTERNAL_IP:PORT >>
    ServerName A.EXTERNALNAME
    ProxyPass / http://A.internal/
    ProxyPassReverse / http://A.internal/
<< /VirtualHost >>

<< VirtualHost EXTERNAL_IP:PORT >>
    ServerName B.EXTERNALNAME
    ProxyPass / http://B.internal/
    ProxyPassReverse / http://B.internal/
<< /VirtualHost >>

I think NameVirtualHost? ip:port means that, if someone comes in on that ip:port, do virtual host stuff based on Host: header.

6. Using the above, I created all the domains I need!


Edit -:- Attach -:- Ref-By -:- Printable -:- More