[CLUE-Tech] Junkbuster can't bind 127.0.0.1:8000

[Jed S. Baer]

On Sun, 24 Mar 2002 13:08:09 -0700
Dave Anselmi <anselmi at americanisp.net> wrote:

> "Jed S. Baer" wrote:
> 
> > I think I might have figured this out. The lo device is missing.
> > However, loading the nbd module didn't allow me to ifup ifcfg-lo, so
> > maybe that isn't it. I'm going to build the kernel with nbd included,
> > instead of modular, which is what I was doing in the past.
> 
> No lo would do it.  Does ifconfig tell you anything?  Can you bring up
> the lo interface with ifconfig?  If you can't I'd guess you don't have
> any of the basic networking enabled (I'd think you have to go out of
> your way to get that kind of kernel).

Well, depends upon what you mean by basic networking. Dialup-IP obviously
was OK. eth0 came up fine as well. At this point, I don't remember what
got me going on the nbd module. Something pointed in that direction.
However, the actual problem was CONFIG_RTNETLINK. In xconfig, this is said
to relate to user-space programs receiving routing information. Not
immediately obvious to my brain that a proxy would need this, and I
wouldn't make a mental connection to the lo device either, fer that
matter. I guess my brain has too much of a conception of "routing" as
being part of "router", which I know isn't really the case.

> What's nbd?  Network block device?  That has little to do with basic
> networking so I'd ignore it while chasing lo problems.

Perhaps I'll make it a module, next time I build the kernel, or leave it
out, and see what happens. I think I've had sufficient kernel compiles for
one day. ;-)

Thanks, Dave.
jed
-- 
"Those who expect to reap the blessings of freedom must, like men,
 undergo the fatigue of supporting it."
 - Thomas Paine