ppp connection OK, but can't access web or ssh

Hi,

I am using wvdial to access my ISP. System logs show the PAP
authentication
succeeds and I can "ping" and ssh to both the primary and secondary DNS
machines.

I cannot ssh to any other machine, or access the web.

I am using FC5 with the firewall disabled. Any ideas what the problem
might be?

cheers
steve

(E-Mail Removed) writes:

>Hi,

>I am using wvdial to access my ISP. System logs show the PAP
>authentication
>succeeds and I can "ping" and ssh to both the primary and secondary DNS
>machines.

>I cannot ssh to any other machine, or access the web.

>I am using FC5 with the firewall disabled. Any ideas what the problem
>might be?

No Not enough information. If you can ping the dns machine it is NOT a ppp
problem. It is probably a routing problem
route -n
should show you what the routes are.
the line starting with
0.0.0.0 and ending with ppp0 should have the ip address of the machine at
the other end of the ppp link as the second entry.
For example you might also have an ethernet card on your system and you
have set it up to have a default route. (0.0.0.0 with eth0 at the end of
the line) ppp will NOT change that default route.
Get rid of the eth0 default route
route del default eth0
before running ppp



>cheers
>steve

Hi Unruh,

> No Not enough information. If you can ping the dns machine it is NOT a ppp
> problem. It is probably a routing problem
> route -n
> should show you what the routes are.
> the line starting with
> 0.0.0.0 and ending with ppp0 should have the ip address of the machine at
> the other end of the ppp link as the second entry.
> For example you might also have an ethernet card on your system and you
> have set it up to have a default route. (0.0.0.0 with eth0 at the end of
> the line) ppp will NOT change that default route.

The machine does have an ethernet card, but is not connected to
a network, hence my need to dialin.

eth0 was not running, but "lo" was:

> /sbin/route -n -v
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
lo

I stopped "lo" and dialled in to my ISP using wvdial. After the PPP
connection is established:


> /sbin/route -n -v -e
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
172.21.128.164 0.0.0.0 255.255.255.255 UH 0 0
0 ppp0
0.0.0.0 172.21.128.164 0.0.0.0 UG 0 0
0 ppp0


I can ping both the primary and secondary DNS machines, and the
two machines having IP addresses shown above in the IP routing table.
I still cannot access the outside world:


> ssh remote.maths.uq.edu.au
ssh: remote.maths.uq.edu.au: Temporary failure in name resolution
> telnet altix16.hpcu.uq.edu.au
altix16.hpcu.uq.edu.au/telnet: Temporary failure in name resolution

Traceroute and netstat shown below:

> traceroute 130.102.2.15
traceroute to 130.102.2.15 (130.102.2.15), 30 hops max, 40 byte packets
1 172.21.128.164 (172.21.128.164) 213.172 ms 263.965 ms 263.581
ms
2 203.15.34.69 (203.15.34.69) 264.126 ms 299.951 ms 299.981 ms
3 203.15.34.42 (203.15.34.42) 304.021 ms 307.978 ms 339.891 ms
4 130.102.1.81 (130.102.1.81) 340.112 ms 344.019 ms 343.975 ms
5 130.102.2.15 (130.102.2.15) 391.877 ms 392.042 ms 392.028 ms


> netstat -i -a -v -e
Kernel Interface table
eth0 Link encap:Ethernet HWaddr 00:00:E2:78:B7:29
BROADCAST 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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:2403 errors:0 dropped:0 overruns:0 frame:0
TX packets:2403 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2555177 (2.4 MiB) TX bytes:2555177 (2.4 MiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:172.22.19.182 P-t-P:172.21.128.164
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:64 (64.0 b) TX bytes:94 (94.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Any ideas?

cheers
steve


Unruh wrote:
> (E-Mail Removed) writes:
>
> >Hi,
>
> >I am using wvdial to access my ISP. System logs show the PAP
> >authentication
> >succeeds and I can "ping" and ssh to both the primary and secondary DNS
> >machines.
>
> >I cannot ssh to any other machine, or access the web.
>
> >I am using FC5 with the firewall disabled. Any ideas what the problem
> >might be?
>
> No Not enough information. If you can ping the dns machine it is NOT a ppp
> problem. It is probably a routing problem
> route -n
> should show you what the routes are.
> the line starting with
> 0.0.0.0 and ending with ppp0 should have the ip address of the machine at
> the other end of the ppp link as the second entry.
> For example you might also have an ethernet card on your system and you
> have set it up to have a default route. (0.0.0.0 with eth0 at the end of
> the line) ppp will NOT change that default route.
> Get rid of the eth0 default route
> route del default eth0
> before running ppp
>
>
>
> >cheers
> >steve

(E-Mail Removed) wrote:
....

> I can ping both the primary and secondary DNS machines, and the
> two machines having IP addresses shown above in the IP routing table.

Can you ping by name?

>> ssh remote.maths.uq.edu.au
> ssh: remote.maths.uq.edu.au: Temporary failure in name resolution
>> telnet altix16.hpcu.uq.edu.au
> altix16.hpcu.uq.edu.au/telnet: Temporary failure in name resolution

So maybe DNS is missing? Do you have any nameserver entries in
/etc/resolv.conf?

Jarek P.

PS:

(E-Mail Removed) wrote:
....

> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> lo

This route is not proper.

> I stopped "lo" and dialled in to my ISP using wvdial.

Don't stop lo.

Jarek P.

Hi Jarek,

> > I can ping both the primary and secondary DNS machines, and the
> > two machines having IP addresses shown above in the IP routing table.
>
> Can you ping by name?

I don't know the names of those machines, only the numerical IP
addresses.

> >> ssh remote.maths.uq.edu.au
> > ssh: remote.maths.uq.edu.au: Temporary failure in name resolution
> >> telnet altix16.hpcu.uq.edu.au
> > altix16.hpcu.uq.edu.au/telnet: Temporary failure in name resolution
>
> So maybe DNS is missing? Do you have any nameserver entries in
> /etc/resolv.conf?

/etc/resolv.conf is empty. What should be in there?

cheers
steve

Jarek,

> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> > lo
>
> This route is not proper.

Can you tell me what is wrong with it?

cheers
steve

>>> I can ping both the primary and secondary DNS machines, and the
>>> two machines having IP addresses shown above in the IP routing table.
>>>> ssh remote.maths.uq.edu.au
>>> ssh: remote.maths.uq.edu.au: Temporary failure in name resolution
>> So maybe DNS is missing? Do you have any nameserver entries in
>> /etc/resolv.conf?
> /etc/resolv.conf is empty. What should be in there?

At the very least, something like

nameserver XXX.XXX.XXX.XXX

If you want/need any sort of default domain, see the man page for details.

(E-Mail Removed) wrote:
> Jarek,
>
>>> Kernel IP routing table
>>> Destination Gateway Genmask Flags Metric Ref Use
>>> Iface
>>> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
>>> lo
>> This route is not proper.
>
> Can you tell me what is wrong with it?

According to:

http://www.ietf.org/rfc/rfc3330.txt

"169.254.0.0/16 - This is the "link local" block. It is
allocated for communication between hosts on a single link.
Hosts obtain these addresses by auto-configuration, such as when
a DHCP server may not be found."

Some distros (and MS Windows) use it when you configure network
but don't define any IP address and dhcp server couldn't be
found. So it is intended for communicating for example beetwen
your notebook and desktop. But it is destined to be applied to
real network interfaces like eth0 - not lo.

Jarek P.