> On 1/8/2015 at 10:09 PM, "Tixy"  wrote:On Sat, 2015-08-01 at 
> 02:48 -0400, Gene Heskett wrote:
> [...]
[...]
> >
> > The only place you are getting an IPV4 address is ppp0. And to get
that
> > you are running pppoeconf. Are you equipt with some sort of a
phone
> > modem card in your machine?

> ppp0 will probably be the ADSL modem attached to eth0. It will be
> getting it's single IP address from the ISP over PPP. (PPPoE is
> Point-to-Point Protocol over Ethernet).

> I assume eth0 doesn't have an IP address because it's not connected
to a
> router or anything. I.e. the computer is a stand alone device
connected
> just to the ADSL modem. (Though I'm not sure about that hypothesis
as
> the OP talks about another computer that's not been upgraded still
> having network access).

> > I have a bag of those things but its been
> > 15 years since I last actually used one. In the above sampling, 2
> > things are dead wrong.
> >
> > 1. Mask is restricted to the exact address when the setting is
> > 255.255.255.255. Much more normal would be to zero the last
triplet.

> No, the mask is OK, the ISP will only be providing one IP address to
the
> user.

> I see nothing suspicious in the IP addresses and masks, assuming the
> computer really is only connected to an ADSL modem.

> First thing to narrow down is if the problem is routing or DNS
related.
> The command:

> ip route

> will show the route being used.

> And pinging a specific IP address would avoid needing a working DNS.
I
> was going to suggest:

> ping 8.8.8.8

> as that's easy to remember and is one Google uses for it's public
name
> server. However, I don't know if Google is blocked in the country
the OP
> lives. (The IP address of the ppp link shown above seems to be a
Hong
> Kong ISP so I believe Google won't be blocked).

> -- 
> Tixy

I don't have a phone modem card on my computers.

Tixy, you are right. I don't use a router. When I use a different
computer I
connect it to my ADSL modem by an ethernet cable.

Since ipv6 doesn't seem to cause the problem I removed the boot option
that disabled it.

When I ran "pon dsl-provider" and ifconfig I got
eth0      Link encap:Ethernet  HWaddr 10:c3:7b:9d:d0:d2  
          inet6 addr: fe80::12c3:7bff:fe9d:d0d2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:732 (732.0 B)  TX bytes:5182 (5.0 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:378 errors:0 dropped:0 overruns:0 frame:0
          TX packets:378 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:30580 (29.8 KiB)  TX bytes:30580 (29.8 KiB)

ppp0      Link encap:Point-to-Point Protocol  
          inet addr:218.102.187.173  P-t-P:203.218.189.254 
Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:3 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
          RX bytes:54 (54.0 B)  TX bytes:54 (54.0 B)

Running "ip route" gave

203.218.189.254 dev ppp0  proto kernel  scope link  src
218.102.187.173

I live in Hong Kong, so Google isn't blocked here, but I couldn't ping
 8.8.8.8. The error message was "connect: Network is unreachable".

Please help a non-techie.

NY

Reply via email to