connect: Network is unreachable
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.:D |
Quote:
Re-run netconfig using a different domain name (I use home.net.au, but the choice is yours). |
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. :) |
^^ :-)
Thanks boss! @clubslacker - You are very privileged. That is "The Man" himself. |
@volkerdi, wow thank you for stopping by :D
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 |
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.
|
Try re-booting so that the hardware is reinitialised.
|
Quote:
|
Can you ping your router?
Code:
ping -c2 <IPaddress of router> On my setup I see Code:
nameserver 10.1.1.1 Has your network card got an IP address? Code:
/sbin/ifconfig |
stand by
|
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 |
Quote:
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 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 Also please post the output of Code:
/sbin/lspci | grep Ethernet |
please keep in mind i am transcribing these out by hand: :D
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) |
Quote:
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 |
It seems that the dmfe.ko kernel module is blacklisted in Slackware by default.
From /lib/modprobe.d/tulip.conf Code:
############################################################################## Code:
# blacklist dmfe |
ok so i checked lsmod | less and did not see anything 'tulip' anywhere.
however i did do this: cp /lib/modprobe.d/tulip.conf /etc/modprobe.d/tulip.conf and then did nano /etc/modprobe.d/tulip.conf and commented out #blacklist dmfe saved computer restarted and it is working! THANK U ps. do u know why it was blacklisted? |
Glad it all worked out for you.
I do not know why it was blacklisted, but the likely reason is that it causes conflicts with other modules. |
Quote:
I tried setting resolve.conf to use opendns and that fixed the problem immediately, however the fix was temporary??? because when i restart my pc it reverts back to the old resolv.conf file. 1. is there a way to make my internet run properly with my normal DNS settings? 2. if no, then how do i make it remember to use opendns or google dns settings so that my internet is not broken every time i restart the computer. thanks... :D edit: so my current resolv.conf file looks like this: Quote:
Quote:
|
Network manager is overwriting the dns configuration so you could either,
reconfigure the network without networkmanager now that you've got the driver problem taken care of so it will keep your settings, or tell network manager which servers to try. I think to configure dns in network manager the GUI way is right click on the networkmanager icon - click edit connections - click your connection in the appropriate tab and select edit -> go to the ip{4,6} settings tabs and set method to dhcp/automatic addresses only -> the dns server box ungreys and you can add them there. (I don't know how to configure network manager via CLI/conf files off the top of my head) |
i see... does anyone know why my default dns settings are not working on linux, though? seems strange to me
|
|
Quote:
I'm not sure - maybe check out the router config, ping those isp dns servers to verify they are all up, maybe reboot the router. Those dns servers are working OK on other setups? |
Quote:
|
Can you post the output of these as root?
traceroute 192.168.1.1 traceroute 68.238.0.14 nmap -sS 192.168.2.1-3 Try to mark the output with your mouse and then use the middle button to paste it in. |
Try making rc.networkmanager non-executable.
Code:
chmod -x /etc/rc.d/rc.networkmanager |
I don't know much about networkmanager but if you are back to using the stock DHCP options from netconfig then you will need to edit /etc/rc.d/rc.inet1.conf to add
Code:
DHCP_KEEPRESOLV[0]="yes" |
Quote:
i double checked everything 3x and the exact same DNS settings that my windows computers got from the router are what linux was set up to use too, but they just didn't want to work with linux. all i did was edit my resolv.conf file to use the google dns servers how it shows in the link above, and i locked the file with chattr +i /etc/resolv.conf and the internet is working beautifully. strange, but solution works. it does bother me a little that I can't get it to run with my own stock DNS nameservers but I CBF to work on this anymore |
All times are GMT -5. The time now is 04:54 AM. |