Skip to Content.
Sympa Menu

baslinux - Re: [BL] ADSL stuff-up (was ADSL setup)

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: Ron Clarke <ariadne AT earthlink.com.au>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] ADSL stuff-up (was ADSL setup)
  • Date: Tue, 1 Aug 2006 08:05:39 +1000

Hi Folks,

On Mon, 31 Jul 2006 14:52:08 +1200
3aoo-cvfd AT dea.spamcon.org wrote:

> > I can manually insmod rtl8139, and it appears in dmesg.
>
> I assume by that you mean eth0 appears in dmesg.

Yes.

> Until you see eth0 you should not do the next step.

Understood.

> > 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.

Agreed. :)

> > 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.

Nor to me.

>
> > 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".

OK.

> "route add default" is totally useless if you can't ping
> the address.
>
> 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.

This morning, I booted from cold.

insmod rtl8139

It showed up in dmesg.

ifconfig eth0 192.168.1.77

ifconfig -a showed it had taken.

then:

ping 192.168.1.1

there was a line to show the ping had been sent

there was a pause, then

neighbour table overflow
neighbour table overflow
neighbour table overflow

until I hit ctrl-c

I am getting that message a lot now. What does it mean ?



> 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.

That was what I did this morning. The ping failed. I can see the
lights flashing on the ADSL modem, but nothing is getting sent back to my
computer. Does the modem not know where to send the bounce ?
At this time of the morning, there is no other computer connected to the LAN.

FWIW: I fluked a net connection with BL2 once, and I don't know what made it
work.
I haven't been able to get past a failed ping ever since.

Has the kernel been damaged in some way ? Should I get a fresh kernel ?

Regards,
Ron

--
Ron Clarke
AUSREG Consultancy http://www.ausreg.com
Tadpole Tunes http://www.tadpoletunes.com
This mail sent to you from sylpheed running on penguin-power




Archive powered by MHonArc 2.6.24.

Top of Page