[TriLUG] why is it slow?

[Rick DeNatale]

On 9/15/06, Greg Cox <glcox at pobox.com> wrote:
> > The typical way to handle this problem is at the name space level.
>
> Not the original poster, but...
>
> One reason I don't like handling this via DNS is that I don't have a
> static IP, and I like living with one dyndns name on the outside
> interface.  And I don't get to manage views with them.  And to me it's
> kinda cool to have one name that always works, whether I'm home or away.
>
> > that this is dramatically easier to do on an honest-to-god router.
>
> I think it's not the Linux tools, so much as the network layout.  It
> becomes easier when you segment up the network to where you use the
> gateway box like a router.  Most of the problems I'm hearing are from
> trying to do this magic routing all on one internal network, which is
> going to kill you ded.

I'm glad that I asked the question.  I hope I learn quite a bit.  I'm
hoping to clarify in my mind why some appliance routers allow server
'wrap-back', to coin a term, and the issues. I've got the same kind of
requirements mind-set as Greg.  I'm also thinking, perhaps naively,
that wrapping back through the same DNS lookups that outside folks do
getting to my servers, let's me see problems that I might not see
otherwise.  Sort of a poor mans approach to the issues raised in this
blog entry:
http://www-03.ibm.com/developerworks/blogs/page/BillHiggins?entry=the_value_of_self_hosting

As for the two vs. one interface question, those appliance routers
certainly have two interfaces, and some of them are no doubt
implemented on an [embedded] Linux platform.

> VLAN'ing your home is probably more than most people want to monkey
> with, but it's pretty cool once it's all set.

It's something I'd like to learn a bit more about. Particularly since
I just 're-flashed' my WRT-54G with OpenWrt, and I'm really using it
more of a switch than a router right now anyway, since I'm not using
it's WAN port.  As I understand it it's implemented on an ethernet
chipset which uses vlan to separate the WAN and LAN networks already.

Of course, I'm one of the guys who thought to himself during Jason's
presentation last night. "Why WOULDN'T I use thin clients in my
house?"

     * Kitchen 'computer' to browse recipes on our home recipe
database web-app, or check e-mail via squirrelmail, or view our
calendar?  I've already got all these apps running, and my wife and I
use them. Well, my wife more than me.

     * Browser clients in guest rooms?

     * Browsers in the commodes?  Nah, that's going too far.

Heck, we put a h*ll of a lot of cat-5 in this house when we built it a
few years ago, might as well use it. <G>


-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/