Very Computer

First I wish to thank everyone for their suggestions on my earlier post
that has gotten me this far.

Unfortunately I still can't ping my ISP after my kPPP dialer (in KDE
desktop) connects.  Nor can I ping 127.0.0.1 (I'm assuming the loopback
configuration is already there).

This is my setup.  Maybe you will find something wrong with it:

My ISP is IBM.net
My /etc/resolv.conf looks like this;
     domain ibm.net
     nameserver 165.87.13.129
     nameserver 165.87.201.244

My kPPP dialer setup (I'm only showing some of the settings here);
     DNS entries : 165.87.13.129
                             165.87.201.244
     Gateway          set to dynamic (IBM says I don't need a gateway IP
so I left it set to dynamic)

I know I have something missing in the DNS setup but I can't figure it
out.  I've contacted IBM.net.  They can't figure it out either.   I was
hoping someone here is using the kPPP dialer to connected to IBM so I
could compare some notes.

Thanks again for helping out.
Dave

Hi!

  I don't have a solution to your problem but I do have some questions
that may point you in the right direction.  

  You should be able to ping anyone, irrespective of your DNS setup, if
you use the IP addresses.  Are you sure the loopback is setup?  You

'ifconfig' give you?  When I do it (connected to my ISP) I get:

eth0      Link encap:Ethernet  HWaddr 00:45:54:3D:A9:77
          inet addr:192.168.10.3  Bcast:192.168.10.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:10 Base address:0xe400

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:17836 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17836 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

ppp0      Link encap:Point-to-Point Protocol
          inet addr:205.205.217.91  P-t-P:205.205.217.63
Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1514  Metric:1
          RX packets:1410 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1132 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10        

  The ppp0 interface will disappear when you disconect and the ethx
interfaces will only show up if you have configured any NICs you have.
However, lo should always look something like above.  Can you use the
loopback addr. to do other stuff (like 'telnet 127.0.0.1')?  You may
also want to take a look at the ouput from 'route'.  Still connected to
my ISP, 'route' gives:

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
205.205.217.63  *               255.255.255.255 UH    0      0        0
ppp0
192.168.10.0    *               255.255.255.0   U     0      0        0
eth0
127.0.0.0       *               255.0.0.0       U     0      0        0
lo
default         205.205.217.63  0.0.0.0         UG    0      0        0
ppp0

  Once again, you should at least have the 127.0.0.0 entry.

  Hope it helps
CZ

That's okay CZ.  Everyone's questions are helping me dig deeper than I ever
could ever do on my own.

Quote:

>   You should be able to ping anyone, irrespective of your DNS setup, if
> you use the IP addresses.  Are you sure the loopback is setup?  You

Crud!  My ifconfig says nothing.  (It does nothing too when I run it).  What
could be wrong here?

Quote:

> eth0      Link encap:Ethernet  HWaddr 00:45:54:3D:A9:77
>           inet addr:192.168.10.3  Bcast:192.168.10.255
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:10 Base address:0xe400

> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:17836 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:17836 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0

> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:205.205.217.91  P-t-P:205.205.217.63
> Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1514  Metric:1
>           RX packets:1410 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1132 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10

>   The ppp0 interface will disappear when you disconect and the ethx
> interfaces will only show up if you have configured any NICs you have.

Just supplying more info; I'm not running a NIC in this machine - modem a
only.

Quote:

> However, lo should always look something like above.  Can you use the
> loopback addr. to do other stuff (like 'telnet 127.0.0.1')?  You may
> also want to take a look at the ouput from 'route'.  Still connected to
> my ISP, 'route' gives:

> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 205.205.217.63  *               255.255.255.255 UH    0      0        0
> ppp0
> 192.168.10.0    *               255.255.255.0   U     0      0        0
> eth0
> 127.0.0.0       *               255.0.0.0       U     0      0        0
> lo
> default         205.205.217.63  0.0.0.0         UG    0      0        0
> ppp0

>   Once again, you should at least have the 127.0.0.0 entry.

Nope - I don't get any of this stuff.  Could it be that my TCP/IP stuff isn't
really configured?  Is there any way of checking?

Quote:>   Hope it helps

Yes, it helps a lot.  Thanks for your comments CZ.
Dave

Did you recompile your kernel with no support for networking?
To see if your kernel supports networking, do:
  cd /proc/net
  awk -F : '{print $1}' dev
The directory should exist and the second command should include a
line:
  lo
for the loopback device.

Maybe you removed the network startup services fro the initscripts?
Essentially, Linux is a networked OS, to the extent that it
is practically never run without a network (even if it is only
the loopback interface at 127.0.0.1).

To see whether the network service startup is enabled, see if the
files in /etc/rc.d/rc<x>.d/ (where <x> is your default runlevel, 3
if you run in text mode only, or 5 if you use X) include S*network
and S*inet files (with a number in place of *).

If you have the startup scripts, it is still possible that they are
not doing anything (they require some configuration files to run).
If you have the S*network file, try executing it as root and see what
it outputs. BTW, what distribution yre you using?

Regards,
---------------------------------------------------------------------
Artur Swietanowski                         http://swietano.spedia.net
Institut fr Statistik,  Operations Research  und  Computerverfahren,
Universit?t Wien,     Universit?tsstr. 5,    A-1010 Wien,     Austria
tel. +43 (1) 427 738 620                     fax  +43 (1) 427 738 629
---------------------------------------------------------------------