network unreachable

network unreachable

Post by Rami » Sat, 28 Oct 1995 04:00:00



Hi, I am installing linux for the first time from the
latest version of slackware. Linux is mounted on a PC
which has win95 on it already. It resides on a different
partition.
Linux seems to be up and running but I cannot get the
network to work. I have set all the IP addresses (machine's,
gateways, netmask, nameserver, etc...) using netconfig.
But I get the following errors at boot time

SIOCSIFADDR: No such device
SIOCSIFBRDADDR: No such device
SIOCSIFNETMASK: No such device
SIOCADDRT: Network is unreachable

I did 1-, 2- and 3- in the FAQ.TXT (below). Nothing happened. I don't have a
/boot/config.in but a /boot/config, the content of which I don't underestand.

Can anybody help me with that? Thanks.

BTW. On the same PC, win95 can reach the net so the problem is not hard.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
FAQ.TXT

A: There are a couple of possibilities. For most users, things work right out
   of the box. However, if you're running into this problem here are two
   workarounds you can try:

   1. Reverse the broadcast and netmask arguments (and their variables)
      in the call to ifconfig in /etc/rc.d/rc.inet1. Make sure you are
      not trying to route your own IP address - you shouldn't have to.

   2. Make sure /etc/networks is properly configured.

   3. You may want to try the 'netconfig' script (in the package netcfg.tgz).
      It's not perfect, but does a pretty good job.

   4. Make sure the kernel you're using supports your hardware.  Most of the
      kernels provided with Slackware include a /boot/config.in file where you
      can look up the compilation options.

 
 
 

network unreachable

Post by Stephen C. Dick » Tue, 31 Oct 1995 04:00:00


type ifconfig at the command prompt and see if you have any network
interfaces.  You should see eth0 as one of the interfaces.  If not
then Linux did not recognize your ethernet adapter.  Make sure that
there are no I/O or IRQ conflicts before proceeding.

Good luck...scd


>Hi, I am installing linux for the first time from the
>latest version of slackware. Linux is mounted on a PC
>which has win95 on it already. It resides on a different
>partition.
>Linux seems to be up and running but I cannot get the
>network to work. I have set all the IP addresses (machine's,
>gateways, netmask, nameserver, etc...) using netconfig.
>But I get the following errors at boot time
>SIOCSIFADDR: No such device
>SIOCSIFBRDADDR: No such device
>SIOCSIFNETMASK: No such device
>SIOCADDRT: Network is unreachable
>I did 1-, 2- and 3- in the FAQ.TXT (below). Nothing happened. I don't have a
>/boot/config.in but a /boot/config, the content of which I don't underestand.
>Can anybody help me with that? Thanks.
>BTW. On the same PC, win95 can reach the net so the problem is not hard.
>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>FAQ.TXT
>A: There are a couple of possibilities. For most users, things work right out
>   of the box. However, if you're running into this problem here are two
>   workarounds you can try:
>   1. Reverse the broadcast and netmask arguments (and their variables)
>      in the call to ifconfig in /etc/rc.d/rc.inet1. Make sure you are
>      not trying to route your own IP address - you shouldn't have to.
>   2. Make sure /etc/networks is properly configured.
>   3. You may want to try the 'netconfig' script (in the package netcfg.tgz).
>      It's not perfect, but does a pretty good job.
>   4. Make sure the kernel you're using supports your hardware.  Most of the
>      kernels provided with Slackware include a /boot/config.in file where you
>      can look up the compilation options.


 
 
 

network unreachable

Post by Rich Whi » Wed, 01 Nov 1995 04:00:00



Quote:

>Hi, I am installing linux for the first time from the
>latest version of slackware. Linux is mounted on a PC
>which has win95 on it already. It resides on a different
>partition.
>Linux seems to be up and running but I cannot get the
>network to work. I have set all the IP addresses (machine's,
>gateways, netmask, nameserver, etc...) using netconfig.
>But I get the following errors at boot time

>SIOCSIFADDR: No such device
>SIOCSIFBRDADDR: No such device
>SIOCSIFNETMASK: No such device
>SIOCADDRT: Network is unreachable

>I did 1-, 2- and 3- in the FAQ.TXT (below). Nothing happened. I don't have a
>/boot/config.in but a /boot/config, the content of which I don't underestand.

>Can anybody help me with that? Thanks.

>BTW. On the same PC, win95 can reach the net so the problem is not hard.

>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>FAQ.TXT

>A: There are a couple of possibilities. For most users, things work right out
>   of the box. However, if you're running into this problem here are two
>   workarounds you can try:

>   1. Reverse the broadcast and netmask arguments (and their variables)
>      in the call to ifconfig in /etc/rc.d/rc.inet1. Make sure you are
>      not trying to route your own IP address - you shouldn't have to.

>   2. Make sure /etc/networks is properly configured.

>   3. You may want to try the 'netconfig' script (in the package netcfg.tgz).
>      It's not perfect, but does a pretty good job.

>   4. Make sure the kernel you're using supports your hardware.  Most of the
>      kernels provided with Slackware include a /boot/config.in file where you
>      can look up the compilation options.

Hey there --

I'm having EXACTLY the same problem .... and I think the answer is found
in #4 of the FAQ.  Check to see if your kernel is compiled to support
network forwarding.  I'm getting the sense that if the /boot/config.in
file shows "n" as the option, then your kernel is not completely compiled
to support things like PPP routing through a server gateway.

BTW -- I hope someone who knows what he/she is doing reads this ... cuz
if I'm off base, I sure would appreciate the enlightenment.

Hope this helps.  Now I have to try to figure out how to fix the problem,
if this is the right direction!  Not there yet.

Rich White                              Better 1000 lies be told
Noise Party                              Than one truth silenced.
bbs:  908-295-2489
http://www.ios.com/~noise

 
 
 

network unreachable

Post by &Ma » Wed, 01 Nov 1995 04:00:00



>Hey there --

>I'm having EXACTLY the same problem .... and I think the answer is found

I'm having at least a similar problem.  I am running dip in PPP mode.  
Everything seems cool, I connect and can ping my own machine... ping time
is about 2 ms.. however, I cannot ping ANYTHING (anywhere?) else, I
always get the "network unreachable" msg.  It cannot be a problem with the
nameserver, because I also try pinging some dotted quad addresses which
should be OK, up and running, but each one gives "network unreachable."

I wonder if your guess, that the problem lies with no

Quote:

>network forwarding.  I'm getting the sense that if the /boot/config.in
>file shows "n" as the option, then your kernel is not completely compiled
>to support things like PPP routing through a server gateway.

is correct?

My config options also show that to be a "n", when the kernel is compiled.
One of the PPP docs states that this might be a problem [problem report:
"I have a default route, but still can't get anywhere else!"], but
discusses what to do in a confusing manner that does not make it clear
whether re-compiling one's own kernel to enable this option should do the
trick, or whether you need to bang your ISP over the head to enable it on
his/her end (unlikely, eh?)  I'd be interested to hear of any progress you
might report on this one...

Regards, Bob *
--
____________________________________________________________
Robert (&Mary) *        |"Please do not shoot the pianist.

510-527-1004            | Wilde, "Impressions of America"

 
 
 

network unreachable

Post by &Ma » Wed, 01 Nov 1995 04:00:00



>I'm having EXACTLY the same problem .... and I think the answer is found
>in #4 of the FAQ.  Check to see if your kernel is compiled to support
>network forwarding.  I'm getting the sense that if the /boot/config.in
>file shows "n" as the option, then your kernel is not completely compiled
>to support things like PPP routing through a server gateway.

Sorry, I just recompiled my kernel to include "IP forwarding" and at least
I still have the same problem, i.e., when pinging, everyone but myself is
on a "network unreachable."

So, it seems kernel support is not the problem... at least that's what I
find.

Regards, Bob *
--
____________________________________________________________
Robert (&Mary) *        |"Please do not shoot the pianist.

510-527-1004            | Wilde, "Impressions of America"

 
 
 

network unreachable

Post by Timothy C. Lo » Fri, 03 Nov 1995 04:00:00





>>Hey there --

>>I'm having EXACTLY the same problem .... and I think the answer is found
>>I'm having at least a similar problem.  I am running dip in PPP mode.  
>Everything seems cool, I connect and can ping my own machine... ping time
>is about 2 ms.. however, I cannot ping ANYTHING (anywhere?) else, I
>always get the "network unreachable" msg.  It cannot be a problem with the
>nameserver, because I also try pinging some dotted quad addresses which
>should be OK, up and running, but each one gives "network unreachable."

>I wonder if your guess, that the problem lies with no

>>network forwarding.  I'm getting the sense that if the /boot/config.in
>>file shows "n" as the option, then your kernel is not completely compiled
>>to support things like PPP routing through a server gateway.

>is correct?

>My config options also show that to be a "n", when the kernel is compiled.
>One of the PPP docs states that this might be a problem [problem report:
>"I have a default route, but still can't get anywhere else!"], but
>discusses what to do in a confusing manner that does not make it clear
>whether re-compiling one's own kernel to enable this option should do the
>trick, or whether you need to bang your ISP over the head to enable it on
>his/her end (unlikely, eh?)  I'd be interested to hear of any progress you
>might report on this one...

>Regards, Bob *

I am having a similar problem also. My boot up says PPP installed, and pppd
runs. I can ping myself and the IP address on the hos, but when I try to ping
anything else I get the "network inreachable" or "network unknown" errors. I
have put all the DNS and name servers in the /etc/resolv.conf file, but it
seems to ignore them.
Timothy C. (anxious to surf the net under linux) Loss

Fireflies are free to glow wherever they want.

------------------====### legal notice ###====-----------------------
Microsoft Network is prohibited from redistributing this work in any
form,in whole or in part.  License to distribute this post is available to Microsoft for $499.  Posting without permission constitutes an agreement to these terms.

 
 
 

network unreachable

Post by &Ma » Sat, 04 Nov 1995 04:00:00



Quote:>I am having a similar problem also. My boot up says PPP installed, and >pppd runs. I can ping myself and the IP address on the hos,=

 but when I >try to ping anything else I get the "network inreachable" or "network >unknown" errors. I have put all the DNS and name=
 servers in the >/etc/resolv.conf file, but it seems to ignore them.

I am beginning to believe that the problem lies in routing, not the
nameserver (since I use dotted quad's and still have the problem.)  
Several books I have say that the daemon "routed" is broken and one should
use "gated" instead... I'm going to look around the net for the gated
program, install it, and see if my problem is resolved..

Good luck, Bob *
--
____________________________________________________________
Robert (&Mary) *        |"Please do not shoot the pianist.

510-527-1004            | Wilde, "Impressions of America"

 
 
 

network unreachable

Post by Timothy C. Los » Sun, 05 Nov 1995 04:00:00


up says PPP installed, and >pppd runs. I can ping myself and the IP
address on the hos,= > > but when I >try to ping anything else I get the
"network inreachable" or "network >unknown" errors. I have put all the DNS
and name= > > servers in the >/etc/resolv.conf file, but it seems to
ignore them.

> Hello Guys,

>    Sorry that I don't have my linux running right now, but have you added
> the "ipdefaultroute" (i think) option to your "pppd" command?  Look in
> "man pppd" at the options.  I think the ipdefaultroute is used to say
> that all your routing goes through your PPPD link.

> Kurt C. Joseph


 Yes I added defaultroute to my pppd line and it works fine now. I can
use ftp, pine, telnet, and eve Netscape 1.22 unser X-Windows! Warning
Netscape 1.2B1 does not seem to work in Linux. Gives server unknown and
DNS errors, so I downloaded 1.22, and it works great.
Timothy C. Loss

 
 
 

network unreachable

Post by Robert Lync » Sun, 05 Nov 1995 04:00:00




>> blah, blah, blah..
[snip]
>Hello Guys,

>Sorry that I don't have my linux running right now, but have you added
>the "ipdefaultroute" (i think) option to your "pppd" command?  Look in
>"man pppd" at the options.  I think the ipdefaultroute is used to say
>that all your routing goes through your PPPD link.

Thanks for your reply... I will answer it only indirectly, since I got my
link up and running correctly yesterday by dumping the attempt to connect
using "dip" (with the switch -p PPP set), and going over to pppd instead.
 Using a pppd script posted on this newsgroup, I got things working in a
couple of hours.  I always thought I had all the routing correct; it is
just dip, which IHMO is not well suited for applications where there is
dynamic IP address allocation going on...

Thanks again for trying to help... Regards, Bob *
--
____________________________________________________________
Robert (&Mary) *        |"Please do not shoot the pianist.

510-527-1004            | Wilde, "Impressions of America"

 
 
 

network unreachable

Post by t.. » Mon, 06 Nov 1995 04:00:00



> Path: dircon!plug.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!chi-news.cic.net!uwm.edu!lll-winken.llnl.gov!enews.sgi.com!decwrl!ablecom!ns2.mainstreet.net!news.isp.net!newsadmin

> Newsgroups: comp.os.linux.networking,comp.os.linux.setup
> Subject: Re: network unreachable
> Date: 3 Nov 1995 00:09:12 GMT
> Lines: 20


> NNTP-Posting-Host: eb223.slip.net
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: quoted-printable
> X-Mailer: Mozilla 1.22 (Windows; U; 16bit)
> Xref: dircon comp.os.linux.networking:18394 comp.os.linux.setup:26097


> >I am having a similar problem also. My boot up says PPP installed, and >pppd runs. I can ping myself and the IP address on the hos,=
>  but when I >try to ping anything else I get the "network inreachable" or "network >unknown" errors. I have put all the DNS and name=
>  servers in the >/etc/resolv.conf file, but it seems to ignore them.

> I am beginning to believe that the problem lies in routing, not the
> nameserver (since I use dotted quad's and still have the problem.)  
> Several books I have say that the daemon "routed" is broken and one should
> use "gated" instead... I'm going to look around the net for the gated
> program, install it, and see if my problem is resolved..

> Good luck, Bob *
> --
> ____________________________________________________________
> Robert (&Mary) *   |"Please do not shoot the pianist.

> 510-527-1004               | Wilde, "Impressions of America"

There seems to be thousands of us with this same problem. Is someone having a
big laugh on us all?
 
 
 

network unreachable

Post by Robert Lync » Mon, 06 Nov 1995 04:00:00



>There seems to be thousands of us with this same problem. Is someone >having a big laugh on us all?

I got my problem fixed by dumping "dip" (which is supposed to work with a
ppp connection) and going to "pppd".  IMHO, pppd is much better esp.
perhaps when one has dynamically allocated IP addresses from one's ISP.  
At least it went this way for me: I worked and worked and worked and
tweaked and patched, etc. with dip, result: no go.  I used pppd (um, with
a very helpful boost from "Chris", who posted a pppd script to this
newsgroup, which I used as a base) and was up and running in a couple of
hours.

So maybe it's no joke but a lot of us are using the wrong tools?

Good luck with yer problems, Bob *
--
____________________________________________________________
Robert *            |"Please do not shoot the pianist.

510-527-1004            | Wilde, "Impressions of America"

 
 
 

network unreachable

Post by Greg Fausa » Tue, 07 Nov 1995 04:00:00




>> >I am having a similar problem also. My boot up says PPP installed, and >pppd runs. I can ping myself and the IP address on the hos,=
>>  but when I >try to ping anything else I get the "network inreachable" or "network >unknown" errors. I have put all the DNS and name=
>>  servers in the >/etc/resolv.conf file, but it seems to ignore them.

>> I am beginning to believe that the problem lies in routing, not the
>> nameserver (since I use dotted quad's and still have the problem.)  
>> Several books I have say that the daemon "routed" is broken and one should
>> use "gated" instead... I'm going to look around the net for the gated
>> program, install it, and see if my problem is resolved..

>> Good luck, Bob *
>> --
>> ____________________________________________________________
>> Robert (&Mary) *       |"Please do not shoot the pianist.

>> 510-527-1004           | Wilde, "Impressions of America"

>There seems to be thousands of us with this same problem. Is someone having a
>big laugh on us all?

I assume you are using the ppp that comes with Linux. Create the directory:
/etc/ppp (if it doesn't already exist). You will then need two files,
/etc/ppp/ip-up and /etc/ppp/ip-down. I actually create one file and link
it to the other. Here is the contents of that file:
--------------cut-----------------
#!/bin/sh
# ip-up         bring interface up
# ip-down       bring interface down
#       the ip-up process:
#               1) routes to the outside world.
#               2) reports via logger.
#       the ip-down process:
#               1) un-routes the outside world.
#               2) reports via logger.
#
#       interface-name          ppp0, ppp1, etc..
#       tty-device              /dev/cua0, /dev/cua1, etc..
#       speed                   38400 (really 115200)
#       local-IP-address        local (ccinc) ip address
#       remote-IP-address       remote ip address
#

interface="$1"
tty="$2"
speed="$3"
local="$4"
remote="$5"

mobil_gateway=123.244.34.101
onramp_gateway=199.1.11
iamerica_gateway=205.173.253.2
computek_gateway=204.96.11

case "$0" in
*ip-up)

        case "$remote" in
                $mobil_gateway*)
                        /sbin/route add mobil-net gw "$remote"
                        /sbin/route add mp-net gw "$remote"
                        /sbin/route add meni-net gw "$remote"
                ;;
                *)
                        /sbin/route add default gw "$remote"
                ;;
        esac
;;
*ip-down)

        case "$remote" in
                $mobil_gateway*)
                        /sbin/route del mobil-net
                        /sbin/route del mp-net
                        /sbin/route del meni-net
                ;;
                *)
                        /sbin/route del default
                ;;
        esac
;;
esac
exit 0
-----------------------end cut----------------------------------------

Once the link is created you must then route packets to it. The ppp process
runs the file ip-up automatically after the link is created. I think the
default routing is what you need.

---greg
--

 
 
 

network unreachable

Post by Rusty Water » Fri, 17 Nov 1995 04:00:00





>>Linux seems to be up and running but I cannot get the
>>network to work. I have set all the IP addresses (machine's,
>>gateways, netmask, nameserver, etc...) using netconfig.
>>But I get the following errors at boot time

>>SIOCSIFADDR: No such device
>>SIOCSIFBRDADDR: No such device
>>SIOCSIFNETMASK: No such device
>>SIOCADDRT: Network is unreachable

silly question, but, are you expecting to do your networking over an ethernet
device or a serial IP connection?

if youre trying to set up networking over ethernet, then you need to check
your system logs to see if the device is being detected. if the device isnt
being detected, then it will be unable to set up a route on the nonexistent
device.

if youre trying to set up serial IP networking, then you need to comment out
all the ethernet related commands in /etc/rc.d/rc.inet1. youll also probably
want to put in an "/sbin/ifconfig dummy" and an /sbin/route statement for your
machine's assigned IP address. youll need to set your default route in your
serial IP login script.

netconfig, perhaps arrogantly, assumes that youre configuring LAN attached
network devices.

-tom
--
Trust the Madness.

                        Dare to be <a href="http://www.xanthia.com/">bored</a>!

 
 
 

1. Network setup problem with Redhat 6.1 -- "network unreachable"

I am having a problem getting my linux computer networked with my other
computers on my small network. While my other computers can ping each
other through tcp/ip, the linux box cannot ping the ip addresses of the
other computers, nor can they ping the linux box.

Setup:
    2 PCs running Win98
    1 PC running Redhat Linux 6.1
    Linux PC using LINKSYS EtherPCI LAN
    1 LINKSYS 5 port Hub
    file: conf.modules reads "alias eth0 ne2k-pci" (setup by Redhat
software upon discovering new hardware)

Symptoms:
1. Linux PC can ping itself, and it appears that the network card my be
setup properly (no error messages on loading).
2. When the Linux PC attempts to ping the other computers, it reports
that the network is unreachable.
3. The other computers can ping each other, but not the Linux PC.

Question:
1. How can I confirm that the Linux PC network setup is working from the
Linux box?
2. Should any computer that is setup for tcp/ip on the hub be able to
ping the other?
3. What is a good simple setup for IP addresses, DNS, etc.,  for a local
network?

----
Thanks, in advance.

-Hal

2. Standards List

3. PCMCIA Network Card - Help! Network unreachable.

4. Latest pre 2.0 stable kernel ?

5. Network unreachable - REPOST - Cat deleted answer

6. 3C905-TX NIC

7. DIP..network unreachable!

8. Help need for Compaq XE 560 and #9GX

9. Network unreachable

10. SIOCADDRT: Network Unreachable

11. network unreachable