Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Gero Verma » Sun, 31 Oct 1999 04:00:00



Hi,

I'm trying to get Linux up and running on my machine and I'm having
some
trouble to get my connection to the internet up and running. I already
checked
several how-to's and these helped me to the accomplish the following:

At the moment I am able to dial in using ISDN at my ISP (xs4all) and
I'm able
to ping to xs4all machines. However when I try to ping non-xs4all
machines I
get the following response:

bash-2.02# ping www.omroep.nl
PING kwik.omroep.nl (145.58.30.2): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
--- kwik.omroep.nl ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss  

Ping to the xs4all server gives the following response:

bash-2.02# ping www.xs4all.nl
PING www.xs4all.nl (194.109.6.99): 56 data bytes
64 bytes from 194.109.6.99: icmp_seq=0 ttl=251 time=39.833 ms
64 bytes from 194.109.6.99: icmp_seq=1 ttl=251 time=40.589 ms
64 bytes from 194.109.6.99: icmp_seq=2 ttl=251 time=39.202 ms
--- www.xs4all.nl ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 39.202/39.874/40.589 ms                

Does anyone hav ean idea what is not configured correct on my system?

Some details:
- SuSE 6.1
- ISDN Teles card

/etc/hosts:
#################
127.0.0.1       localhost
127.0.0.2       gerodt.NLMIRD01         gerodt
194.109.6.66    xs4all.nl               xs4all
################

/etc/resolv.conf:
################
search xs4all.nl xs4all.be
nameserver 194.109.6.66
nameserver 194.109.9.99
################

route -n returns:
bash-2.02# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref
Use Iface
194.109.6.0     0.0.0.0         255.255.255.0   U     0      0
0 ippp0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
0 lo
bash-2.02#          

Any help is appreciated. If more info is required to figure out the
problem
let me know.

Thanks,

Gero Vermaas

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Clifford Ki » Sun, 31 Oct 1999 04:00:00



> route -n returns:
> bash-2.02# route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref
> Use Iface
> 194.109.6.0     0.0.0.0         255.255.255.0   U     0      0
> 0 ippp0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
> 0 lo

There's no default route through the PPP interface.  The pppd program
sets that route if you add the "defaultroute" option.  Whatever you
use for ISDN should have a similar option.

If not then

 /sbin/route add default ippp0

should work.

--

/* To extract lines:  View file with "vi -R".  Move cursor to first line.
   Press "v".  Move cursor to mark lines (Esc unmarks).  Write lines to
   fubar with ":w fubar <Enter>".  Exit with ":q <Enter>". */

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Robert Glove » Mon, 01 Nov 1999 03:00:00



> OK, I tried /sbin/route add default ippp0 but i steill get the same
> results when trying to ping to a machine that not os my ISP.

> route -n now includes the line
> 0.0.0.0                 0.0.0.0                 0.0.0.0         U
> 0        0      ippp0

> in addition to the lines below.

> Any other suggestions?

Shouldn't you specify a gateway (your ISP gateway) too with the default
route command or did I miss something?
 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Clifford Ki » Mon, 01 Nov 1999 03:00:00



> OK, I tried /sbin/route add default ippp0 but i steill get the same
> results when trying to ping to a machine that not os my ISP.
> route -n now includes the line
> 0.0.0.0            0.0.0.0                 0.0.0.0         U
> 0   0      ippp0
> in addition to the lines below.

This should work, provided you also have the network route for the PPP
interface that you originally showed and that it is *correct* for the
network on the other side of the PPP interface.  Is the error message
the same?

You have 194.109.6.66 as a nameserver in /etc/resolv.conf which is correct
but you also have it in hte hosts file and show "xs4all.nl as the primary
name and xs4all as the secondary.  The proper name is ns.xs4all.nl and
the name given it in hosts file may be causing a problem, although I'd
expect the error message for that to be "unknown host".

--

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Bill Unr » Mon, 01 Nov 1999 03:00:00



Quote:>OK, I tried /sbin/route add default ippp0 but i steill get the same
>results when trying to ping to a machine that not os my ISP.
>route -n now includes the line
>0.0.0.0             0.0.0.0                 0.0.0.0         U
>0    0      ippp0

This is useless. It says" If you do not know how to get to the machine
with a certain address, send the packet to your own computer to let it
try" Of course your own machine does not know how to get there so it is
not going to be of much help in getting the packet tot he address in
question.
It must be
0.0.0.0    x.x.x.x   ..... ppp0
where x.x.x.x is the IP address of your ISP's computer.

Quote:>> /sbin/route add default ippp0

You need a gateway machine to do your routing.
/sbin/route add default gw x.x.x.x ippp0
 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Clifford Ki » Mon, 01 Nov 1999 03:00:00




> >OK, I tried /sbin/route add default ippp0 but i steill get the same
> >results when trying to ping to a machine that not os my ISP.
> >route -n now includes the line
> >0.0.0.0                0.0.0.0                 0.0.0.0         U
> >0       0      ippp0
> This is useless. It says" If you do not know how to get to the machine
> with a certain address, send the packet to your own computer to let it
> try" Of course your own machine does not know how to get there so it is

Ah.. No, I don't think so.  In an asyncronous PPP connection I *know* it
dumps everything that's not specified more closely in the routing table to
the PPP interface and it then goes out to the other side of the link and
on to it's destination, provided the routing on the other side allows it.
It's hard to believe that such routing for syncronous PPP over an ISDN
line would behave differently than it does for asyncronous PPP.

Try it.  Establish a PPP link to an ISP and then remove all the routing
to that link with "route del ... ppp0"'s, with ... replaced by existing
PPP routes.  Then do "route add default ppp0", if the PPP interface is,
say, ppp0.  You'll have Internet access and everything will work as
it should.

You don't need a route with an IP address specific address to the PPP
interface, even though this is done by pppd, which then sets a default
route to the IP address (and thus the pppd interface) if the defaultroute
option is used.  And you also don't need a network specific route to
the PPP interface, as I mistakenly hinted earlier.

--

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Bill Unr » Tue, 02 Nov 1999 04:00:00




]> >OK, I tried /sbin/route add default ippp0 but i steill get the same
]> >results when trying to ping to a machine that not os my ISP.

]> >route -n now includes the line
]> >0.0.0.0               0.0.0.0                 0.0.0.0         U
]> >0      0      ippp0

]> This is useless. It says" If you do not know how to get to the machine

]Ah.. No, I don't think so.  In an asyncronous PPP connection I *know* it

You are right, I was wrong. I just tried it. So a simple
route add default ppp0
does work. You do not need a specific gateway at the othe end, at least
not if you  have a linux machine at the other end. Do not know if other
systems would demand a specific gateway that the packets get sent to.

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Gero Verma » Wed, 03 Nov 1999 04:00:00


Hi,

I tried all suggestions given, but still get the "network not
reachable" error when I try to ping a non xs4all machine.

PING kwik.omroep.nl (145.58.30.2): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
--- kwik.omroep.nl ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss  

What configuration information (hosts file, resolv.conf file,....)
should I post such that some can determine what the problem is?

Gero





>]> >OK, I tried /sbin/route add default ippp0 but i steill get the same
>]> >results when trying to ping to a machine that not os my ISP.

>]> >route -n now includes the line
>]> >0.0.0.0           0.0.0.0                 0.0.0.0         U
>]> >0  0      ippp0

>]> This is useless. It says" If you do not know how to get to the machine

>]Ah.. No, I don't think so.  In an asyncronous PPP connection I *know* it

>You are right, I was wrong. I just tried it. So a simple
>route add default ppp0
>does work. You do not need a specific gateway at the othe end, at least
>not if you  have a linux machine at the other end. Do not know if other
>systems would demand a specific gateway that the packets get sent to.

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Clifford Ki » Wed, 03 Nov 1999 04:00:00



> I tried all suggestions given, but still get the "network not
> reachable" error when I try to ping a non xs4all machine.
> PING kwik.omroep.nl (145.58.30.2): 56 data bytes
> ping: sendto: Network is unreachable
> ping: wrote kwik.omroep.nl 64 chars, ret=-1
> ping: sendto: Network is unreachable
> ping: wrote kwik.omroep.nl 64 chars, ret=-1
> ping: sendto: Network is unreachable
> ping: wrote kwik.omroep.nl 64 chars, ret=-1
> --- kwik.omroep.nl ping statistics ---
> 3 packets transmitted, 0 packets received, 100% packet loss  
> What configuration information (hosts file, resolv.conf file,....)
> should I post such that some can determine what the problem is?

You can ping any machine in the xs4all.nl domain but not outside that
domain.  You now have a default route, and you have the resolv.conf
configured with nameservers.  That doesn't seem to leave much else.

I thought that the default route would be all that you needed since with
the network-specific route in your first post the symptoms would be what
you describe.  In fact I deleted my default route and put up a network
route to hte ISP as a test and got exactly those symptoms.

Make sure that there's a default route.  Post exact copies (not
hand copies) of the route program output to get opinions if you're
not sure what's what.  Since things work within xs4all.nl the PPP link
itself must be solid so debug logs are not likely to be useful.

--

/* Microsoft is a great marketing organization.
 * It _has_ to be */

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Dumouchel Clermon » Wed, 03 Nov 1999 04:00:00


I'm not an expert,
Did you
ifconfig eth0 145.58.30.2 netmask 255.255.255.0 broadcast 145.58.30.255
then
route add -net 145.58.30.0 dev eth0

try to ping after that.

I did that with a 192.168.1.1 and it works.

DC

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Gero Verma » Thu, 04 Nov 1999 04:00:00


Thanks for the help so far, unfortunately....

....I still have the problem that I'm not able to reach machine other
then the machines of my ISP. I'll give the output I get and the
scripts executed below.
One of the script gives an "SIOCSIFMETRIC: Operation not supported"
error, I'm not sure if this error causes the problems. But maybe one
of you can answer that question.

A ping to non xs4all.nl machine results in (ping to www.xs4all.nl goes
fine):
#############################
bash-2.02# ping www.omroep.nl
PING kwik.omroep.nl (145.58.30.2): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
--- kwik.omroep.nl ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
bash-2.02#                              
#############################

route -n gives the following:
########################
bash-2.02# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref
Use Iface
194.109.6.0     0.0.0.0         255.255.255.0   U     0      0
0 ippp0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
0 lo  
########################

The hosts file contains:
###################
194.109.6.66    ns.xs4all.nl            xs4all
###################

resolf.conf contains:
######################
search ns.xs4all.nl ns2.xs4all.nl
nameserver 194.109.6.66
nameserver 194.109.9.99
######################

Here's what I do:

To initialize the ISDN stuff I use the script startisdn (see below).
Executing
this script results in the following output:

############### output of startisdn
bash-2.02# ./startisdn
Starting isdn4linux
Verbose-level set to 2.
ippp0 added
EAZ/MSN for ippp0 is 348482121
Hangup-Timeout for ippp0 is 180 sec.
Security for ippp0 is on
Layer-2-Protocol for ippp0 is hdlc
Layer-3-Protocol for ippp0 is trans
Encapsulation for ippp0 is syncppp
ippp0 bound to 0
333333333333
SIOCSIFMETRIC: Operation not supported
44444444444
Setting Dial-On-Demand  
bash-2.02#
############### EO output of startisdn

As you can see, there seems to be a problem in the line between
"33333333333"
and "44444444". To further investigate this, i'll include the contents
of some
scripts.

############## startisdn
/etc/rc.d/init.d/rc.isdn start
/sbin/route add default gw 194.109.6.66 ippp0
#############  EO startisdn

As you can see, this script call rc.isdn which has the following
content: (the
echo 3333 / echo 4444 are added to identify the line where a problem
might
occur.

###############/etc/rc.d/init.d/rc.isdn #!/bin/sh
# rc.isdn   This shell script boots up the ISDN subsystem.
# Comments to Jeroen van Pelt <y...@xs4all.nl>

case "$1" in
start)
      if [ ! -r /etc/i4l.conf ]
      then
        echo "cannot read /etc/i4l.conf"
      else
        . /etc/i4l.conf
        echo "Starting isdn4linux"

        # Loading Modules
        $MODPROBE hisax type=$TYPE \
          protocol=$PROTOCOL \
          io=$ISDN_IO \
          irq=$ISDN_IRQ

        $HISAXCTRL HiSax 1 0x3ff

        # Global
        $ISDNCTRL verbose 2

        # Check if we should start isdnlog
        if [ $STARTLOG = "YES" ]
        then
          $ISDNLOG -sS -v1 -w10 -m0x17d7 -l0x3d7 \
            -C /dev/console \
            -D /dev/isdnctrl
        fi

        # ISDN device drivers ippp0 (syncPPP)
        $ISDNCTRL addif      $IF0
        $ISDNCTRL addphone   $IF0 out $PROV1_MSN
        $ISDNCTRL eaz        $IF0 $MY_MSN
        $ISDNCTRL huptimeout $IF0 $HUPTO
        $ISDNCTRL secure     $IF0 $SECURE

        $ISDNCTRL l2_prot    $IF0 $L2_PROT
        $ISDNCTRL l3_prot    $IF0 $L3_PROT
        $ISDNCTRL encap      $IF0 $ENCAP
        $ISDNCTRL pppbind    $IF0 $BINDNAME

        # This line is necessary for the newest HiSax versions
        # Add this line by hand if you want to upgrade your scripts
        # from previous versions. Don't forget to add $DIALMODE to
        # /etc/i4l.conf
        $ISDNCTRL dialmode   $IF0 $DIALMODE

echo 333333333333
        $IFCONFIG $IF0 $MY_IP pointopoint $PROV1_IP metric 1
echo 44444444444
        $IFCONFIG $IF0 -arp -broadcast

        # Starting ipppd and checking for static IP
        if [ $DYN_IP = "YES" ]
        then
          $IPPPD remotename $REMNAME \
            user $NAME \
            ipcp-accept-local \
            ipcp-accept-remote \
            /dev/ippp0 &
        else
          $IPPPD remotename $REMNAME \
            user $NAME \
            $MY_IP:$PROV1_IP \
            /dev/ippp0 &
        fi

        # Configuring Dial-on-Demand
        # Not sure if this is still necessary. Please report any
problems
        if [ $DOD = "YES" ]
        then
          echo "Setting Dial-On-Demand"
          $ROUTE add default ippp0
        else
          echo "No support for Dial-on-Demand"
        fi    

      fi
      ;;

stop)
      echo "Shutting down isdn4linux..."
      if [ ! -r /etc/i4l.conf ]
      then
        echo "Cannot read /etc/i4l.conf"
      else
        . /etc/i4l.conf

        $IFCONFIG $IF0 down
        sleep 1
        $ISDNCTRL delif $IF0
        sleep 1
        killall ipppd

        # Check if isdnlog was started and then kill it
        if [ $STARTLOG = "YES" ]
        then
          echo "Killing isdnlog"
          killall isdnlog
        fi

      fi
      ;;

*)
      echo "Usage: $0 {start|stop}"
      exit 1
      ;;
############################ EO rc.isdn

The rc.isdn script uses i4l.conf, which has the following content:
########################### /etc/i4l.conf
#!/bin/sh
# i4l.conf      Configuration file for isdn subsystem
# Comments to Jeroen van Pelt <y...@xs4all.nl>

# File locations - Adjust to your situation
ISDNCTRL=/sbin/isdnctrl
IFCONFIG=/sbin/ifconfig
ROUTE=/sbin/route
IPPPD=/sbin/ipppd
MODPROBE=/sbin/modprobe
HISAXCTRL=/sbin/hisaxctrl
ISDNLOG=/sbin/isdnlog

# Card configuration
# Take a look at /usr/src/linux/Documentation/isdn/README.HiSax
TYPE=3                  # Type of ISDN card
PROTOCOL=2              # 2 for Euro ISDN (OK for Holland)
ISDN_IO=0xd80           # IO address of ISDN card
ISDN_IRQ=10             # IRQ of ISDN card

# Data for XS4ALL.NL
PROV1_MSN=0346553613    # Provider's MSN
PROV1_IP=194.109.6.66   # Provider's IP number
                        # Do not set this to 0.0.0.0 if you also have
a LAN
REMNAME=xs4all.nl       # Remote domain name

# Local configuration data
DYN_IP=YES              # Change to NO in case of static IP
MY_MSN=348482121        # Without leading zero
MY_IP=194.109.6.0       # If static IP change this to IP number
                        # Do not set this to 0.0.0.0 if you also have
a LAN
NAME=gero               # XS4ALL username
STARTLOG=YES            # Set to YES if you want to start isdnlog
DOD=YES                 # Change to YES if you want Dial-On-Demand
                        # Set $DIALMODE to 'auto' if you set this to
YES

# IPPP0 configuration - No need to change this!
IF0=ippp0               # Interface name
HUPTO=180               # Hang-up-timeout for $IF0
SECURE=on               # Security
L2_PROT=hdlc            # level 2 protocol
L3_PROT=trans           # level 3 protocol
ENCAP=syncppp           # syncppp or rawip (Leave this to syncppp for
XS4ALL)
BINDNAME=0              # Name to $IF0 is bound to
DIALMODE=auto           # Configures DialOnDemand
                        # 'manual' does NOT automaticly disconnect
                        # HUPTO won't do a thing
                        # When set to 'auto', set $DOD to 'YES'
########################### EO /etc/i4l.conf

Any help is really appreaciated.

Regards,

Gero Vermaas
g...@xs4all.nl

On 2 Nov 1999 09:01:07 -0600, kite@NoSpam.% inetport.com (Clifford

Kite) wrote:
>Gero Vermaas (g...@xs4all.nl) wrote:

>> I tried all suggestions given, but still get the "network not
>> reachable" error when I try to ping a non xs4all machine.

>> PING kwik.omroep.nl (145.58.30.2): 56 data bytes
>> ping: sendto: Network is unreachable
>> ping: wrote kwik.omroep.nl 64 chars, ret=-1
>> ping: sendto: Network is unreachable
>> ping: wrote kwik.omroep.nl 64 chars, ret=-1
>> ping: sendto: Network is unreachable
>> ping: wrote kwik.omroep.nl 64 chars, ret=-1
>> --- kwik.omroep.nl ping statistics ---
>> 3 packets transmitted, 0 packets received, 100% packet loss  

>> What configuration information (hosts file, resolv.conf file,....)
>> should I post such that some can determine what the problem is?

>You can ping any machine in the xs4all.nl domain but not outside that
>domain.  You now have a default route, and you have the resolv.conf
>configured with nameservers.  That doesn't seem to leave much else.

>I thought that the default route would be all that you needed since with
>the network-specific route in your first post the symptoms would be what
>you describe.  In fact I deleted my default route and put up a network
>route to hte ISP as a test and got exactly those symptoms.

>Make sure that there's a default route.  Post exact copies (not
>hand copies) of the route program output to get opinions if you're
>not sure what's what.  Since things work within xs4all.nl the PPP link
>itself must be solid so debug logs are not likely to be useful.

>--
>Clifford Kite <kite@inet% port.com>                    Not a guru. (tm)
>/* Microsoft is a great marketing organization.
> * It _has_ to be */

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Clifford Ki » Thu, 04 Nov 1999 04:00:00



> One of the script gives an "SIOCSIFMETRIC: Operation not supported"
> error, I'm not sure if this error causes the problems. But maybe one
> of you can answer that question.

OK.  I'm not experienced with ISDN but I did make a couple of tests here,
connecting with a regular asyncronous PPP  link.  I remove the interface
configuration with ifconfig and then did

  ifconfig ppp0 128.83.57.144 pointopoint 128.83.57.248 metric 1

which resulted in the error message

  SIOCSIFMETRIC: Operation not supported on transport endpoint

*but* it did reconfigure the ppp0 interface correctly.  Using ifconfig
without the "metric 1" also configures the interface correctly but
doesn't generate the error message.

So I'd guess that this isn't a problem.

What might be the problem is the "IP address" 194.109.6.0 that route -n
reports for the ippp0 interface.  This is really a class C network address
and I'd just supposed that it had been created by the IDSN configuration
scripts.  But it was possible to make a PPP connection here, tear down
the PPP interface configured by pppd, and then reconfigure the interface
with a network address here.

This was using
  ifconfig ppp0 xxx.xxx.xxx.yyy pointopoint xxx.xxx.xxx.0

After adding a default route there was apparently normal Internet access.
But the route that ifconfig automatically provided shows up as a host
route:

  Destination     Gateway    Genmask         Flags Metric Ref    Use Iface
  xxx.xxx.xxx.0      *       255.255.255.255 UH    0      0        0 ppp0

whereas your route -n shows a network route.

About all I can come up with is that perhaps you have the IP addresses
configured for MY_IP and PROV1_IP swapped.  That's easy to change and
test anyway.

[edited]

Quote:> resolf.conf contains:
> ######################
> search ns.xs4all.nl ns2.xs4all.nl
> nameserver 194.109.6.66
> nameserver 194.109.9.99
> ######################

The search argument should be just xs4all.nl.  "man 5 resolver" describes
how to configure /etc/resolv.conf .

[edited]

Quote:> # Data for XS4ALL.NL
> PROV1_MSN=0346553613       # Provider's MSN
> PROV1_IP=194.109.6.66      # Provider's IP number
>                         # Do not set this to 0.0.0.0 if you also have
> a LAN
> REMNAME=xs4all.nl  # Remote domain name
> # Local configuration data
> DYN_IP=YES         # Change to NO in case of static IP
> MY_MSN=348482121   # Without leading zero
> MY_IP=194.109.6.0          # If static IP change this to IP number
>                        # Do not set this to 0.0.0.0 if you also have

Since I don't know about some of the ISDN configuration you might check
to see whether anything else is not right, should it turn out that the
IPs are not swapped.

--

/* 97.3% of all statistics are made up. */

 
 
 

Linux PPP setup problem (SuSE6.1, "Network is unreachable")

Post by Gero Verma » Thu, 04 Nov 1999 04:00:00


Thanks for the help so far, unfortunately....

....I still have the problem that I'm not able to reach machine other
then the machines of my ISP. I'll give the output I get and the
scripts executed below.
One of the script gives an "SIOCSIFMETRIC: Operation not supported"
error, I'm not sure if this error causes the problems. But maybe one
of you can answer that question.

A ping to non xs4all.nl machine results in (ping to www.xs4all.nl goes
fine):
#############################
bash-2.02# ping www.omroep.nl
PING kwik.omroep.nl (145.58.30.2): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote kwik.omroep.nl 64 chars, ret=-1
--- kwik.omroep.nl ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
bash-2.02#                              
#############################

route -n gives the following:
########################
bash-2.02# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref
Use Iface
194.109.6.0     0.0.0.0         255.255.255.0   U     0      0
0 ippp0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
0 lo  
########################

The hosts file contains:
###################
194.109.6.66    ns.xs4all.nl            xs4all
###################

resolf.conf contains:
######################
search ns.xs4all.nl ns2.xs4all.nl
nameserver 194.109.6.66
nameserver 194.109.9.99
######################

Here's what I do:

To initialize the ISDN stuff I use the script startisdn (see below).
Executing
this script results in the following output:

############### output of startisdn
bash-2.02# ./startisdn
Starting isdn4linux
Verbose-level set to 2.
ippp0 added
EAZ/MSN for ippp0 is 348482121
Hangup-Timeout for ippp0 is 180 sec.
Security for ippp0 is on
Layer-2-Protocol for ippp0 is hdlc
Layer-3-Protocol for ippp0 is trans
Encapsulation for ippp0 is syncppp
ippp0 bound to 0
333333333333
SIOCSIFMETRIC: Operation not supported
44444444444
Setting Dial-On-Demand  
bash-2.02#
############### EO output of startisdn

As you can see, there seems to be a problem in the line between
"33333333333"
and "44444444". To further investigate this, i'll include the contents
of some
scripts.

############## startisdn
/etc/rc.d/init.d/rc.isdn start
/sbin/route add default gw 194.109.6.66 ippp0
#############  EO startisdn

As you can see, this script call rc.isdn which has the following
content: (the
echo 3333 / echo 4444 are added to identify the line where a problem
might
occur.

###############/etc/rc.d/init.d/rc.isdn #!/bin/sh
# rc.isdn   This shell script boots up the ISDN subsystem.
# Comments to Jeroen van Pelt <y...@xs4all.nl>

case "$1" in
start)
      if [ ! -r /etc/i4l.conf ]
      then
        echo "cannot read /etc/i4l.conf"
      else
        . /etc/i4l.conf
        echo "Starting isdn4linux"

        # Loading Modules
        $MODPROBE hisax type=$TYPE \
          protocol=$PROTOCOL \
          io=$ISDN_IO \
          irq=$ISDN_IRQ

        $HISAXCTRL HiSax 1 0x3ff

        # Global
        $ISDNCTRL verbose 2

        # Check if we should start isdnlog
        if [ $STARTLOG = "YES" ]
        then
          $ISDNLOG -sS -v1 -w10 -m0x17d7 -l0x3d7 \
            -C /dev/console \
            -D /dev/isdnctrl
        fi

        # ISDN device drivers ippp0 (syncPPP)
        $ISDNCTRL addif      $IF0
        $ISDNCTRL addphone   $IF0 out $PROV1_MSN
        $ISDNCTRL eaz        $IF0 $MY_MSN
        $ISDNCTRL huptimeout $IF0 $HUPTO
        $ISDNCTRL secure     $IF0 $SECURE

        $ISDNCTRL l2_prot    $IF0 $L2_PROT
        $ISDNCTRL l3_prot    $IF0 $L3_PROT
        $ISDNCTRL encap      $IF0 $ENCAP
        $ISDNCTRL pppbind    $IF0 $BINDNAME

        # This line is necessary for the newest HiSax versions
        # Add this line by hand if you want to upgrade your scripts
        # from previous versions. Don't forget to add $DIALMODE to
        # /etc/i4l.conf
        $ISDNCTRL dialmode   $IF0 $DIALMODE

echo 333333333333
        $IFCONFIG $IF0 $MY_IP pointopoint $PROV1_IP metric 1
echo 44444444444
        $IFCONFIG $IF0 -arp -broadcast

        # Starting ipppd and checking for static IP
        if [ $DYN_IP = "YES" ]
        then
          $IPPPD remotename $REMNAME \
            user $NAME \
            ipcp-accept-local \
            ipcp-accept-remote \
            /dev/ippp0 &
        else
          $IPPPD remotename $REMNAME \
            user $NAME \
            $MY_IP:$PROV1_IP \
            /dev/ippp0 &
        fi

        # Configuring Dial-on-Demand
        # Not sure if this is still necessary. Please report any
problems
        if [ $DOD = "YES" ]
        then
          echo "Setting Dial-On-Demand"
          $ROUTE add default ippp0
        else
          echo "No support for Dial-on-Demand"
        fi    

      fi
      ;;

stop)
      echo "Shutting down isdn4linux..."
      if [ ! -r /etc/i4l.conf ]
      then
        echo "Cannot read /etc/i4l.conf"
      else
        . /etc/i4l.conf

        $IFCONFIG $IF0 down
        sleep 1
        $ISDNCTRL delif $IF0
        sleep 1
        killall ipppd

        # Check if isdnlog was started and then kill it
        if [ $STARTLOG = "YES" ]
        then
          echo "Killing isdnlog"
          killall isdnlog
        fi

      fi
      ;;

*)
      echo "Usage: $0 {start|stop}"
      exit 1
      ;;
############################ EO rc.isdn

The rc.isdn script uses i4l.conf, which has the following content:
########################### /etc/i4l.conf
#!/bin/sh
# i4l.conf      Configuration file for isdn subsystem
# Comments to Jeroen van Pelt <y...@xs4all.nl>

# File locations - Adjust to your situation
ISDNCTRL=/sbin/isdnctrl
IFCONFIG=/sbin/ifconfig
ROUTE=/sbin/route
IPPPD=/sbin/ipppd
MODPROBE=/sbin/modprobe
HISAXCTRL=/sbin/hisaxctrl
ISDNLOG=/sbin/isdnlog

# Card configuration
# Take a look at /usr/src/linux/Documentation/isdn/README.HiSax
TYPE=3                  # Type of ISDN card
PROTOCOL=2              # 2 for Euro ISDN (OK for Holland)
ISDN_IO=0xd80           # IO address of ISDN card
ISDN_IRQ=10             # IRQ of ISDN card

# Data for XS4ALL.NL
PROV1_MSN=0346553613    # Provider's MSN
PROV1_IP=194.109.6.66   # Provider's IP number
                        # Do not set this to 0.0.0.0 if you also have
a LAN
REMNAME=xs4all.nl       # Remote domain name

# Local configuration data
DYN_IP=YES              # Change to NO in case of static IP
MY_MSN=348482121        # Without leading zero
MY_IP=194.109.6.0       # If static IP change this to IP number
                        # Do not set this to 0.0.0.0 if you also have
a LAN
NAME=gero               # XS4ALL username
STARTLOG=YES            # Set to YES if you want to start isdnlog
DOD=YES                 # Change to YES if you want Dial-On-Demand
                        # Set $DIALMODE to 'auto' if you set this to
YES

# IPPP0 configuration - No need to change this!
IF0=ippp0               # Interface name
HUPTO=180               # Hang-up-timeout for $IF0
SECURE=on               # Security
L2_PROT=hdlc            # level 2 protocol
L3_PROT=trans           # level 3 protocol
ENCAP=syncppp           # syncppp or rawip (Leave this to syncppp for
XS4ALL)
BINDNAME=0              # Name to $IF0 is bound to
DIALMODE=auto           # Configures DialOnDemand
                        # 'manual' does NOT automaticly disconnect
                        # HUPTO won't do a thing
                        # When set to 'auto', set $DOD to 'YES'
########################### EO /etc/i4l.conf

Any help is really appreaciated.

Regards,

Gero Vermaas
g...@xs4all.nl

On 2 Nov 1999 09:01:07 -0600, kite@NoSpam.% inetport.com (Clifford

Kite) wrote:
>Gero Vermaas (g...@xs4all.nl) wrote:

>> I tried all suggestions given, but still get the "network not
>> reachable" error when I try to ping a non xs4all machine.

>> PING kwik.omroep.nl (145.58.30.2): 56 data bytes
>> ping: sendto: Network is unreachable
>> ping: wrote kwik.omroep.nl 64 chars, ret=-1
>> ping: sendto: Network is unreachable
>> ping: wrote kwik.omroep.nl 64 chars, ret=-1
>> ping: sendto: Network is unreachable
>> ping: wrote kwik.omroep.nl 64 chars, ret=-1
>> --- kwik.omroep.nl ping statistics ---
>> 3 packets transmitted, 0 packets received, 100% packet loss  

>> What configuration information (hosts file, resolv.conf file,....)
>> should I post such that some can determine what the problem is?

>You can ping any machine in the xs4all.nl domain but not outside that
>domain.  You now have a default route, and you have the resolv.conf
>configured with nameservers.  That doesn't seem to leave much else.

>I thought that the default route would be all that you needed since with
>the network-specific route in your first post the symptoms would be what
>you describe.  In fact I deleted my default route and put up a network
>route to hte ISP as a test and got exactly those symptoms.

>Make sure that there's a default route.  Post exact copies (not
>hand copies) of the route program output to get opinions if you're
>not sure what's what.  Since things work within xs4all.nl the PPP link
>itself must be solid so debug logs are not likely to be useful.

>--
>Clifford Kite <kite@inet% port.com>                    Not a guru. (tm)
>/* Microsoft is a great marketing organization.
> * It _has_ to be */