--Dr. S.K. Singh,
On Wed, 5 Aug 1998, Max Klohn wrote:
> Thanks,
> I found the definition of SIOCADDRT in the source tree, "add routing table entry"
> I had a static route entry to net 192.168.121.0 through eth0 (192.168.121.10), I
> think I had put it there for troubleshooting... I zeroed it out and now I don't get
> the SIOCADDRT error message...
>
> But eth0 still fails to transmit/receive packets... so the real problem is yet in
> another place.
> my current networks table:
> ---------------------------------------------------
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> localnet * 255.255.255.0 U 0 0 2 eth0
> loopnet * 255.0.0.0 U 0 0 2 lo
> ---------------------------------------------------
>
> I am thinking seriously of getting the S.U.S.E release maybe I'll have better
> results than with Red Hat?
>
>
> Glynn Clements wrote:
>
> > Max Klohn wrote:
> >
> > > I noticed I am getting the following message at boot, just after the
> > > initialization of the amd pcnet32 netcard:
> > > (for memory: RH5.1, failed detection at first install script, driver manually
> > > installed after, fails pings and shows TX errors, but "sees" the wire with
> > > tcpdump)
> > >
> > > SIOCADDRT: invalid argument
> >
> > The most likely reason for this message is that you have a route
> > command of the form:
> >
> > route add ... gw xxx.xxx.xxx.xxx dev eth0
> >
> > where the gateway isn't itself reachable.
> >
> > You would need to check the scripts which initialise networking.
> >
> > --
> > Glynn Clements <glynn@sensei.co.uk>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu