According to Dick Kalin: While burning my CPU.
>
> At 09:40 AM 5/31/99 +0000, Richard Adams wrote:
> >According to Dick Kalin: While burning my CPU.
> >>
> >>
> >
> >The interface is attached ok or so it seems from the information given, i
> >would take a bet that you dont have any routes pointing to eth0.
> >You could try the following on the command line;
> >
> >route add 123.123.123.123 eth0
> >route add default gw 123.123.123.123 eth0
> >
> ># Where 123.123.123.123 would be your_ISP's IP# or the IP# of the
> >destination address.
> >
> >>
> >> If more information is needed, I'll be happy to provide. Just tell me
> how to
> >> get it :-)
> >
> >Try using 'route <-n>' to check routes before adding the above.
> >
>
> route -n yields
>
> Destination Gateway Genmask Flags Metric Ref Use Ifac
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 2 eth0
> 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 14 eth0
>
> but neither (.1.0 nor .1.254 ) exist.
> what I'm trying to do is have Linux (192.168.1.10) be the server for
> Win98 ( 192.168.1.98) and WinNT (192.168.1.4).
192.168.1.0 means add a route to the whole 192.168.1 subnet on eth0.
Your system is sending ALL packets to 192.168.1.254 because it is stated
that that is the gateway which ALL packet MUST be sent.
Obviously that is where your problem starts.
>
> also, the first problem I see in the LILO boot messages is
> Appletalk <...>
> ipcalc: not found.
This is not a cause of the routing problem, if you dont have any MAC
computers then why use appeltalk anyway.
>
> also, I think I see under
> eexpress: module not recommended. use IO=xx.
This is a common messages from modprobe, it could be discarded as your card
is found and initisalised at bootime.
I get simalar messages with my smc-ultra card, basicly modprobe is saying
that you should define the I/O base in /etc/conf.modules
>
> how can I create a log of these boot messages to see the problems? or
> perhaps the proper question is "is there a place where these problems are
> logged?"
'dmesg' should show most of them, others may appier in /var/log or /var/adm
"messages" "debug" "syslog" or "kernel".
>
> ## I found the messages ( thanks to your answer to another newbie's question.)
> < snip >
> kernal: eexpress.c: Module autoprobe not recommended, give io=xx
> kernal: eth0: EtherExpress at 0x300, IRQ 9, Interbace BNC, 32k
> kernal: eexpress.c: v0.10 < etc. >
> v0.14 < " >
> v0.15 < " >
> named[270]: starting, ...
> named[270]: cache zone ""(IN) loaded (serial 0 )
> named[270]: master zone "0.0.127.in-addr.arpa" (IN) loaded (serial .... )
> named[270]: listening on [192.168.1.10].53 (eth0)
> named[270]: Forwarding source address is [0.0.0.0].1027
> named[270]: ready to answer quieries.
> named[270]: sysquery: sendto([198.41.0.4].53): Network is unreachable
>
This is the final answer to your problem, "named" is sending requests to
198.41.0.4 VIA your gateway which we have established to be "bogus" so you
get the error, "Network is unreachable", of which it is, so your system
cannot function.
If you need more help, let me know, its late here (2 am) and i am tyred.
> < snip >
>
> does any of this help?
Yup, your information is very detailed and allows us all to tell you whats
wrong.
>
> Dick
>
> Dick Kalin
> Minneapolis, MN
>
--
Regards Richard.
[EMAIL PROTECTED]
