[SOLVED] connect: Network is unreachable

clubslacker · 02-03-2013, 12:10 AM

I just installed slackware on my dell dimension 4300 that previously had a working copy of ubuntu on it. I didn't have any problems going through the install process. I have been following this guide: http://docs.slackware.com/slackware:beginners_guide and i'm at the part where where it tells me to do run these commands:
# slackpkg update gpg
# slackpkg update

and i get "unable to resolve host address 'ftp.mirrorservice.org'" and so I tried re-editing /etc/slackpkg/mirrors file again to choose a different mirror and it still doesn't connect to any mirrors. So I tried pinging a random ip and get "connect: Network is unreachable"

so I ran netconfig and set it up as:
hostname: dim4300
domainname: localhost
configuration type: DHCP
set DHCP hostname:

and that didn't fix anything at all.

Now i'm beyond my abilities. I do know that the internet worked in ubuntu, nothing has changed.

I am trying to connect through a wired, DSL connection from a router.

Thanks to anyone who can help.

allend · 02-03-2013, 12:25 AM

Quote:

domainname: localhost

Likely to be a DNS problem caused by the choice of domain name. 'localhost' is a special name that is set to '127.0.0.1'.
Re-run netconfig using a different domain name (I use home.net.au, but the choice is yours).

volkerdi · 02-03-2013, 12:31 AM

Rerunning netconfig changes the config files, but the changes won't actually take effect until you reboot, or run: sh /etc/rc.d/rc.inet1 restart

If that still doesn't do the trick, it's worth trying the NetworkManager option in netconfig. It works here.

allend · 02-03-2013, 12:34 AM

^^ :-)
Thanks boss!

@clubslacker - You are very privileged. That is "The Man" himself.

clubslacker · 02-03-2013, 12:41 AM

@volkerdi, wow thank you for stopping by

ok i changed in netconfig:
hostname: dimhostname
domain name: dimdomain
teh rest: use DHCP server

then i ran "sh /etc/rc.d/rc.inet1 restart"

I still get:
failed: temporary failure in name resolution.
wget: unable to resolve host address 'ftp.mirrorservice/org'

thank you guys for fast replies

clubslacker · 02-03-2013, 12:44 AM

ok, now i have tried the networkmanager option in netconfig, and i did sh /etc/rc.d/rc.inet1 restart again after i changed the setting. Still no cigar.

allend · 02-03-2013, 12:45 AM

Try re-booting so that the hardware is reinitialised.

clubslacker · 02-03-2013, 12:53 AM

Quote:

Originally Posted by allend

Try re-booting so that the hardware is reinitialised.

ok melbourne i just tried setting netconfig to networkmanager >reboot still not connection. Then i tried setting the option back to DHCP>reboot and still no connection.

allend · 02-03-2013, 01:01 AM

Can you ping your router?

Code:

ping -c2 <IPaddress of router>

What is the content of /etc/resolv.conf?
On my setup I see

Code:

nameserver 10.1.1.1

where 10.1.1.1 is the IP address of my ADSL modem/router.

Has your network card got an IP address?

Code:

/sbin/ifconfig

clubslacker · 02-03-2013, 01:13 AM

stand by

clubslacker · 02-03-2013, 01:24 AM

1.
i ping -c2 192.168.1.1 and got:
connect: Network is unreachable

(i tested simply pinging 192.168.1.1 from my windows 7 laptop and it works fine.)

2.
i ran # nano /etc/resolv.conf and all it says is "search dimdomain"

3.
i ran /sbin/ifconfig...
I do not really see where it does, or does not show my network card ip address? I can see stuff, but I don't know what most of it means.... I do not see any 192.x.x.x. numbers. I do see 127.0.0.1 netmask 255.0.0.0 inet6 ::1 etc

allend · 02-03-2013, 01:35 AM

Quote:

do not really see where it does, or does not show my network card ip address? I can see stuff, but I don't know what most of it means.... I do not see any 192.x.x.x. numbers. I do see 127.0.0.1 netmask 255.0.0.0 inet6 ::1 etc

Don't worry. We could make a Slacker of you yet.

It appears that your network card is not up and working.
The output of ifconfig should show lines like this

Code:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.1.1.2  netmask 255.255.255.0  broadcast 10.1.1.255
        inet6 fe80::219:d1ff:fe2d:7748  prefixlen 64  scopeid 0x20<link>
        ether 00:19:d1:2d:77:48  txqueuelen 1000  (Ethernet)
        RX packets 45977  bytes 55925851 (53.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32480  bytes 3168315 (3.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 21  memory 0xdffe0000-e0000000

The eth0 is your network card.
The next line starting inet are network parameters that should be supplied by DHCP from your router.

Please post the output of

Code:

/sbin/ifconfig -a

This should show your network card even if it is not up.

Also please post the output of

Code:

/sbin/lspci | grep Ethernet

This should show details of your network card if it is PCI based.

clubslacker · 02-03-2013, 01:51 AM

please keep in mind i am transcribing these out by hand:

root@dimhostname:~# /sbin/ifconfig -a
lo: flags=73<UO,LOOPBACK,RUNNING> mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 overruns 0 frame 0
tx packets 0 bytes 0 (0.0B)
tx errors 0 droppped 0 overruns 0 carrer 0 colisions 0

root@dimhostname:~# /sbin/lspci | Ethernet
02:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev31)

allend · 02-03-2013, 02:06 AM

Quote:

02:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev31)

That device is supported by the dmfe.ko kernel module.

Check the output of 'lsmod'. It may be that the tulip.ko kernel module is being loaded. If you see 'tulip' then try

Code:

rmmod tulip
modprobe dmfe
sh /etc/rc.d/rc.inet1 restart

If that works, then you will need to blacklist the tulip.ko kernel module so that it is not loaded at boot.

allend · 02-03-2013, 02:18 AM

It seems that the dmfe.ko kernel module is blacklisted in Slackware by default.
From /lib/modprobe.d/tulip.conf

Code:

##############################################################################
# Do not edit this file; instead, copy it to /etc/modprobe.d/ and edit that
##############################################################################

# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
blacklist de4x5

# At least 2.4.3 and later xircom_tulip doesn't have that conflict
# xircom_tulip_cb
blacklist dmfe

Try copying the above file to /etc/modprobe.d/tulip.conf and comment out the line that blacklists dmfe i.e.

Code:

# blacklist dmfe

It is probably best to reboot to test this.