Monday March 03, 2008
End-to-end... and everything in betweenDan McDonald's Sun blog, covering IPsec, general networking goodness, and other stuff too.
Kebe's Home Data Center (or f''(Bart's new home server)) A little over a year ago, Bart Smaalders blogged about his new home server. Subsequently Bill built a similarly-configured one. (I thought that he had blogged about his too, but he hadn't.)
So why four ethernet ports (covering three drivers)? Well, like Indiana, Crossbow is exciting, but not yet integrated into the main OpenSolaris tree. I do, however, very much like the idea of Virtual Network Machines and I'll be using these four ports to build three such machines on this server using prerequisite-to-Crossbow IP Instances. Two ports will form the router zone. The router will also be a firewall, and maybe an IPsec remote-access server too. With Tunnel Reform in place, I can let my or my wife's notebook Macs access our internal home network from any location. One port will be the public web server, and assuming Comcast doesn't screw things up too badly on their business-class install, the new home of www.kebe.com. The last port will be the internal-server and global-zone/administrative station. All of that ZFS space needs to be accessible from somewhere, right? I'd like to thank Bart and Bill for the hardware inspiration, and to my friends in OpenSolaris networking for offering up something I can exploit immediately to create my three machines in one OpenSolaris install. I'll keep y'all informed about how things are going. (2008-03-03 08:21:22.0) Permalink Comments [4]
Trackback URL: http://blogs.sun.com/danmcd/entry/kebe_s_home_data_center
Post a Comment: |
Calendar
RSS Feeds
All /Entertainment /IPsec /Miscellany /Networking SearchLinks
NavigationReferersToday's Page Hits: 96 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Nice home setting indeed.
About the need for multiple interfaces, with onnv83 you've got a couple of other alternatives to get by with a signle physical NIC on the system:
1.Use multiple VLANs over the same physical NIC, and assign them to zones with exclusive IP stack. The other nodes in the home network of course need to be configured with the VLAN of the zone they're connecte to on the home server.
2. XVM or Xen has been part of onnv for a few builds. It uses Crossbow vnics under the hood. You could for example have the WAN facing webserver entirely live in a guest domain connected through its vnic carved out the same NIC. One caveat: you need a lotta RAM.
Posted by kais on March 04, 2008 at 11:36 AM EST #
Kais
I have no VLAN-capable switches in my house, never mind that I find VLANs undesirable from a traffic separation POV. I trust OUR stuff, but not someone else's. As for xVM/Xen - I only have 2GB RAM, with only 2 more to go until I max out the motherboard. I'll stick with zones.
And when Crossbow does putback, I could get rid of the two iprb ports, but to be honest, since I got 'em, I might as well use 'em.
Posted by Dan McDonald on March 05, 2008 at 01:00 AM EST #
Just wondering, why you think Indiana is less stable? The kernel and userland bits are exactly the same ones used as in the SX*E builds (well, minus the encumbered ones). The real difference here is the packaging, mostly the installer and IPS.
Posted by Mario Goebbels on March 30, 2008 at 12:10 PM EDT #
Mario - Indiana builds don't get cut every two Nevada builds to my knowlege. SXCE does. (And there is the matter of those pesky encumbered bits...) I should've not mentioned stability and been more clear.
Posted by Dan McDonald on April 01, 2008 at 10:49 AM EDT #