Best of the Newsgroups: OSR5 routing default route

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

From: Jeff Liebermann <jeffl@comix.santa-cruz.ca.us>
Subject: Re: RealTEK 8139a, SCO OSR 5.0.5 and Sony Vaio PCG-FXA63
Date: Sun, 05 Jan 2003 00:25:18 -0800
References: <z85R9.17843$Xc.9198@nwrddc04.gnilink.net> 

On Fri, 03 Jan 2003 00:51:43 GMT, "ews" <whyeven@ask.com> wrote:

>Over the last week or so I have been attempting to get OSR5.0.5 running
>properly on a Sony Vaio PCG-FXA63.
>The biggest hangup I am having now is with the built-in ethernet card.
>Although the Vaio docs neglect to mention the chipset, The Windows install
>reported using the RealTEK RTL8139 driver / chipset.

Correct.  The FX series uses the RTL8139CL.  See:
   http://www.myplc.com/sony/vaio_compare.htm
for clues.

>So, I downloaded the SCO driver from
>http://www.realtek.com.tw/downloads/downloads1-3.aspx?keyword=sco+rtl8139a
>and installed the software, added a new LAN controller, relinked and reboot.

Methinks(not sure) that the 3.2v5.0.5 version I installed two weeks
ago, had the RTL-8139 driver on the distribution media.  However,
autodetect didn't find the ethernet card and I had to install it
manually.  I'm not sure if the "SCO Unix 5.0.x" version on the Realtek
web pile is the same.  There are also some no so subtle differences
between the RTL-8139 and the RTL-8139C Plus.  Sorry, I have no details
on how this affects driver issues.

>The first is
>
>#ping 10.0.0.1
>ping: sendto: No route to host
>ping: wrote 10.0.0.1 64 chars, ret=-1
>
>#netstat -rn
>
>Destination    Gateway    Flags    Refs    Use    Interface
>10.0.8            10.0.8.2    UC        1        0        net1\
>10.0.8.2        127.0.0.1   UGHS   0        0        lo0
>127.0.0.1      127.0.0.1   UH        3        17      lo0
>224                10.0.8.2    UCS       0       0        net1
>
>Same message with the route to 10.0.8 removed

Why would you want to remove the only route that goes somewhere?

You have no default route.  You need a default route.  Run:
   route add default 10.0.0.1
or whatever reflects your default route.

Note:  You can live without a default route, but you will not be able
to ping anything outside of your netmask.

>#ifconifg reports that net1 is up, with the ipaddress of 10.0.8.2 and mask
>of ff000000

[Insert general gripe about paraphrasing error messages and trunc..ing
diagnostic output].  What duz:
  ifconfig -a
really output?  Mine looks like:
  -> ifconfig wdn0
  wdn0: flags=23<UP,BROADCAST,NOTRAILERS>
        inet 192.168.111.1 netmask ffffff00 broadcast 192.168.111.255

There was a bug in an older version of ODT or OSR5 that prevented
ifconfig netmask from delivering anything larger than /24.  I think it
was fixed long ago.  It would therefore be interesting to see what the
ifconfig lines in /etc/tcp look like.  Run:
  grep ifconfig /etc/tcp
Mine (from 3.2v4.2) looks like (slightly edited):
  ifconfig lo0 localhost
  ifconfig wdn0 192.168.111.1 -trailers netmask 255.255.255.0
     broadcast 192.168.111.255

>after #route flush
>
>the routing table looks like (summarized output)
>
>Dest.            GW            If
>10                10.0.8.2     net1
>127.0.0.1     127.0.0.1   lo0
>224              10.0.8.2     net1

Well, if the above is true, then you should be able to now ping
10.0.0.1 since the route from your machine at 10.0.8.2 to the
10.xxx.xxx.xxx network is up.  

Incidentally, for 3.2v5.0.5, please kill the "routed" daemon (RIP).
Then edit /etc/tcp by inserting comment symbols in front of the
section that starts tcp/ip.  That will prevent accidental changes to
the routes from being broacast all over the LAN and from misconfigured
NT4 servers and cheap routers from trashing the OSR5 machines routeing
table.

>and no messages are displayed. IE
>#ping 10.0.0.1 (10.0.0.1): 56 data bytes

OK.  So the route is there, but nobody is home.  Lots of possible
reasons for that which have nothing to do with OSR5 or the RLT-8139.
Start with the simple stuff like:
1. Are the ethernet lights on?  At both ends of the cable?
2. Can you ping yourself?  Try both localhost and 10.0.8.2
3. Can whatever device is at 10.0.0.1 ping the laptop at 10.0.8.2?
4. Can you ping *ANY* other machine on the 10.0.8.xxx network?
5. Is the ethernet device enabled in the Sony CMOS setup?
6. You mentioned Windoze on the Vaio.  Did the ethernet port work
under Windoze?
 
>Any suggestions?

1.  Check your assumptions.
2.  Don't blame the obvious.
3.  Test what's easiest first.
4.  Offer sacrifice to the computah gods in the form of a burnt 386
motherboard.
5.  Start with a *SIMPLE* network configuration.  That means that your
laptop IP address is in the same /24 block as the default router.  Use
a netmask of 255.255.255.0.  Keep it VERY simple.  When that works,
then configure it to whatever weird netmask and creative route suits
your fancy.  If it suddenly stops working, the problem will be
obvious.

>If you need more informations please ask!

1.  Exact version including patches:
   customquery listpatches | head -1
2.  Some clue as to your network topology.  Methinks it's sorta
working but the TCP/IP configuration is wacko.

Incidentally, don't try the:
  route flush
incantation when connected over a network link.  It clears all the
routes including the default route.  It disconnected me from my office
server (I'm at home now) until I get it rebooted.  I should have known
better.  Dumb...dumb...dumb...


-- 
Jeff Liebermann  150 Felker St #D  Santa Cruz CA 95060
(831)421-6491 pgr  (831)336-2558 home
http://www.LearnByDestroying.com   WB6SSY
jeffl@comix.santa-cruz.ca.us   jeffl@cruzio.com
 

Take Control of Your Domain Names

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.