In article <HJSTEIN.93Jul6164657@sunrise.huji.ac.il> hjstein@sunrise.huji.ac.il (Harvey J. Stein) writes:
quoted text
>
>So, what does this mean?  How do I get these ethernet boards working
>with NET-2?  Are there any test programs that I can run to figure
>things out?  Here's what ifconfig and route tell me:
>
># ifconfig
>lo        IP ADDR 127.0.0.1  BCAST 127.255.255.255  NETMASK 127.0.0.0
>          MTU 2000  METRIC 0  POINT-TO-POINT ADDR 0.0.0.0
>          FLAGS: 0x0049 ( UP LOOPBACK RUNNING )

Note the incorrect netmask: it should be 255.0.0.0.  Setting the netmask
explicitly with ifconfig at bootup fixes it - there is a bug in plain
0.99.10 that results in bogus netmasks when you let the kernel guess at
them. 

quoted text
>eth0      IP ADDR 128.253.154.32  BCAST 128.253.154.255  NETMASK
>255.255.255.0
>          MTU 1500  METRIC 0  POINT-TO-POINT ADDR 0.0.0.0
>          FLAGS: 0x0043 ( UP BROADCAST RUNNING )

This one is ok, it seems.

quoted text
># route
>Kernel routing table
>Destination net/address   Gateway address           Flags RefCnt    Use Iface
>128.253.0.0               *                         UN         0   1786 lo
>localhost                 *                         UH         0    153 lo
>blinky.cpaf.com           *                         UH         0      0 lo
>sebastian.cpaf.com        *                         UH         0    160 lo

Due to the netmask problems, all the routing information goes to the
loopback interface, as you can see, and nothing ever leaves the machine.
When you get your netmask set up correctly, the routing should work too,
and you should be up and running. 

                Linus