Networking question...

**swemic** · 03-18-2005

After you have issued "ping" command, what does

Code:

arp -a

show?

**Sonyk** · 03-18-2005

? (192.168.0.1) at <incomplete> on eth0

**adrenaline** · 03-18-2005

Here is something to try. I have ran into this before in slackware. two things actually

first.
cd /etc/rc.d/rc.inet1.conf
scroll towards the bottom. there is a section that says gateway.
see if there is actually a gateway there if not enter between the quotes
192.168.0.1 that should be your default gateway once you have saved and exited actually reboot your box and see if that fixes it.

Second
sometime resolv.conf doesn't get written the first try.
to check this try to put a valid ip in your address bar of your browser and see if it resolves or
cd /etc and less resolv.conf and see if your valid dns servers are in there
They should not start with a 192.168 number.

Mike

**Sonyk** · 03-19-2005

Gateway is set... I don't know what's wrong

with bare.i all worked OK

**Sonyk** · 03-31-2005

can somebody help ? I don't believe that i'm alone with this problem...

**Flatline** · 03-31-2005

I have seen acpi bork network cards before. You may just not be able to have acpi enabled and have a working net card. You could try upgrading to a 2.6 kernel and seeing if that helps.

Go into your install cd #2 and go to

Code:

/mnt/cdrom/testing/packages/linux-2.6.10

Then:

Code:

installpkg kernel-generic-2.6.10-i486-1.tgz
  installpkg kernel-modules-2.6.10-i486-1.tgz
  installpkg mkinitrd-1.0.1-i486-1.tgz

Then go into your boot directory and type

Code:

mkinitrd -c -k 2.6.10 -m <your FS type>

Then update lilo.conf with something like this (leave your default kernel section alone! create this as a new section)

Code:

image = /boot/vmlinuz-generic-2.6.10
  initrd = /boot/initrd.gz
  root = /dev/hdb3
  label = Linux2.6.10
  read-only

Then run

Code:

lilo

to update your bootloader, reboot, and pray.

Don't delete your 2.4.x kernel image...it could come in handy.

Thread Tools

Display

Posting Permissions