"N. Sean Timm" wrote:
>
> David Douthitt wrote:
> > > I had to edit the "network" file because the CIPD
> > > (or something like that) variable was tacking on an extra
> > '/' to the ip,
> > > so it was ending up with something like '192.168.1.2//3'
> > (something like
> > > that...you get the idea).
> >
> > That should be fixed in the most recent versions using the new ipmask
> > binary. I'll check. THe most recent I think is 0827.
>
> I was using the 0827 build.
Check also what version of ipmask it's using; try
# ipmask
and see what version it's using. 0.31 should work; most current is
0.32.
> > Can you explain further? Was syslogd and klogd running?
>
> I'll check on this later and get back to you. Basically, the log files
> were all in /var/log, but they were all 0 bytes and stayed that way.
Doesn't sound like *logd was running; check and see.
> > Remember several things: 1) ping fails in at least FOUR different
> > ways... 2) Oxygen routers are not configured to answer to pings.
>
> Sorry...I should have been more clear on this. The set of pings I am
> testing work with the March version of Oxygen that I'm currently using.
> I can successfully ping the following with the March version:
>
> 1) Machines on my internal network - 192.168.1.2, 192.168.1.3, etc.
> 2) My DSL router - 123.45.67.89
> 3) www.yahoo.com
>
> If all three work, I know my network connection is good to go. In the
> development version of Oxygen, I could only get the first 2 to work. I
> also tried utilizing the IP number in case it had to do with resolving
> the name, but that didn't work, either.
You still didn't say HOW the ping failed. As I said, there's at least
four different ways it can fail. From what you said, it sounds like
there might be routing problems, but I'm just guessing - from the fact
that you can't ping www.yahoo.com, but internal systems work.
> > > Also, I had some trouble getting the latest dnscache.lrp
> > working...(not
> > > that it mattered while I couldn't hit the external network). :)
> >
> > You didn't get that from the Oxygen distribution :)
>
> Err... http://leaf.sourceforge.net/pub/oxygen/packages/dnscache.lrp?
Bah. I better erase that :-)
I don't believe that I compiled that (perhaps I did); look for Jacques
Nilo's page, I think he did something with dnscache. I'm tending to
stay away from djb tools; the licensing is too restrictive for me.
I'm looking at pdns and maradns and others...
> > > The syslinux.cfg seemed to indicate that it supported a
> > > CONF=myfile.cnf,
> > > but it didn't seem to like that keyword,
> >
> > It should work; what are the messages?
>
> I can get back to you on the exact message, but it was basically
> something like 'unknown keyword'. Originally, I took everything out of
> the file but "CONF=large.cnf" to see if that would work, and that's when
> I got the error.
That's odd indeed. The installation uses CONF= in a very critical
point: this is where ALL configuration now takes place. You must have
gotten a banner of some sort; did it say something about "Use the new
configuration files..." or did it say something to the effect of "All
other configuration directives will be ignored!!!"
I'll look these over again.
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
