Baslinux mailing list

[3aoo-cvfd AT dea.spamcon.org]

Ron Clarke wrote:
>
> On reboot, the rc.inet1 was back to 0 bytes, and the 
> backup file had disappeared altogether.

That is decidely weird behavior.  Either rc.inet1 is on
a ramdisk or something is overwriting that file (which
should not be happening).

> I can manually insmod rtl8139, and it appears in dmesg.

I assume by that you mean eth0 appears in dmesg.
Until you see eth0 you should not do the next step.

> I can ifconfig eth0 192.168.1.5 (or 7 or 77), and ifconfig 
> shows it is OK with netmask at 255.255.255.0

That's positive.

> route    gives me something different everytime !

How is that possible.  You execute route and get one
result, and then execute route immediately and get
something else???  That doesn't seem possible.

> route add default gw 192.168.1.1     gives the result:

Do not do "route add" until you can ping the address.
I repeat:  first ping the address.  If ping works, then
(and only then) do the "route add".

> And no amount of repeating "add default etc.." seems to 
> make any difference.

"route add default" is totally useless if you can't ping 
the address.

> Needless to say, ping 192.168.1.1 does nothing 

ping is the first thing you must get working.  You said
it was working yesterday.  You need to figure out why it
is not working today.

> I am nearly ready to rip the whole ADSL stuff out and 
> go back to carrier pidgeons.

Forget about rc.inet1 (for now).  Please re-read the step-by-step
I gave you yesterday.  Insmod the card.  Give the card an address
(using ifconfig).  Ping the router.  It is not complicated.  Do 
not do the ifconfig until you are sure the insmod worked.  Do not 
do the ping until you are sure the ifconfig worked.

We need to pinpoint exactly which step is failing.

Cheers,
Steven