On Tue, 18 Feb 2003 01:42:49 -0800 (PST) Ron Bouwhuis
<[EMAIL PROTECTED]> wrote:

> All,
> 
> Using MDK 9.0 and trying to get internet connection
> going through an ADSL USB modem.  Using eciadsl
> package and seems to work OK - to a point.  Something
> very screwy is happening.  I can ping, but only sort
> of.  
> 
> For example, I seem to be ablt to ping to xx.yy.zz.aa
> type addresses, though sometimes get .  However, with
> written addresses, it SOMETIMES works, but often not. 
> Here's an example:
> 
> [root@Auckland etc]# ping www.rosenet.ne.jp
> ping: unknown host www.rosenet.ne.jp
> [root@Auckland etc]# ping www.rosenet.ne.jp
> PING catv01.rosenet.ne.jp (210.230.70.2) from
> 203.173.243.231 : 56(84) bytes of data.
> 64 bytes from catv01.rosenet.ne.jp (210.230.70.2):
> icmp_seq=1 ttl=239 time=266 ms
> 64 bytes from catv01.rosenet.ne.jp (210.230.70.2):
> icmp_seq=2 ttl=239 time=260 ms
> 64 bytes from catv01.rosenet.ne.jp (210.230.70.2):
> icmp_seq=3 ttl=239 time=259 ms
> 64 bytes from catv01.rosenet.ne.jp (210.230.70.2):
> icmp_seq=4 ttl=239 time=259 ms
> 64 bytes from catv01.rosenet.ne.jp (210.230.70.2):
> icmp_seq=5 ttl=239 time=259 ms
> 
> --- catv01.rosenet.ne.jp ping statistics ---
> 5 packets transmitted, 5 received, 0% loss, time
> 5056ms
> rtt min/avg/max/mdev = 259.161/260.746/266.239/2.511
> ms
> 
> You can see the first two times I got unknown host,
> but the third time it worked.  Nothing was done
> between attempts other than up arrow and enter in
> bash!  All three attempts within 1 minute.  Why work
> the third time???
> 
> Here's the contents of host.conf and resolv.conf:
> 
> [root@Auckland etc]# cat host.conf
> order hosts,bind
> multi on
> [root@Auckland etc]# cat resolv.conf
> # ppp temp entry
> nameserver 203.109.252.42 # ppp temp entry
> nameserver 203.109.252.43 # ppp temp entry
> 
> I don't know if they are right, but I do know that the
> entries in resolv.conf are the DNS servers supplied by
> my ISP through DHCP.
> 
> My route table looked odd at first, until I figured
> that the hyphenated IP address was probably just the
> name.  Here are two views of the route table that show
> what I mean:
> 
> 
> [root@Auckland etc]# route -e
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags 
>  MSS Window  irtt Iface
> 203-173-243-254 *               255.255.255.255 UH    
>   40 0          0 ppp0
> 192.168.0.0     *               255.255.255.0   U     
>   40 0          0 eth0
> 127.0.0.0       *               255.0.0.0       U     
>   40 0          0 lo
> default         203-173-243-254 0.0.0.0         UG    
>   40 0          0 ppp0
> [root@Auckland etc]# route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags
> Metric Ref    Use Iface
> 203.173.243.254 0.0.0.0         255.255.255.255 UH   
> 0      0        0 ppp0
> 192.168.0.0     0.0.0.0         255.255.255.0   U    
> 0      0        0 eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U    
> 0      0        0 lo
> 0.0.0.0         203.173.243.254 0.0.0.0         UG   
> 0      0        0 ppp0
> 
> Not sure what the UH and UG flags mean.  Actually,
> don't know much about routing at all, so if anything
> looks odd, please tell me.
> 
> Finally, here's the output from ifconfig.  Not sure if
> the 255.255.255.255 netmask is correct for ppp0, but
> that's what set up by DHCP from the ISP.  It's the
> same in Windows that that seems to work OK.  
> 
> [root@Auckland etc]# ifconfig
> eth0      Link encap:Ethernet  HWaddr
> 00:90:CC:12:D2:64
>           inet addr:192.168.0.2  Bcast:192.168.0.255 
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500 
> Metric:1
>           RX packets:32926 errors:0 dropped:0
> overruns:0 frame:0
>           TX packets:38633 errors:0 dropped:0
> overruns:0 carrier:0
>           collisions:29 txqueuelen:100
>           RX bytes:16790046 (16.0 Mb)  TX
> bytes:6766294 (6.4 Mb)
>           Interrupt:3 Base address:0x300
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:5910 errors:0 dropped:0
> overruns:0 frame:0
>           TX packets:5910 errors:0 dropped:0
> overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1949959 (1.8 Mb)  TX bytes:1949959
> (1.8 Mb)
> 
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:203.173.243.231 
> P-t-P:203.173.243.254  Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST 
> MTU:1500  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)
> 
> 
> Please help - this is driving me crazy and I can't
> figure out why ping and DNS lookup SOMETIMES work.  Of
> course, from a web browser I can't connect to anything
> at all - just get a host timeout error.  I've been
> forced to use W2K as my internet connection sharing
> box - and I'm convinced I've already been subject to
> attack from the big bad web the very first day!!!
> 
> Regards and sorry for the long post,
> Ron.

Suspect DNS problems...
Try:
dig @203.109.252.42 www.rosenet.ne.jp
dig @203.109.252.43 www.rosenet.ne.jp
which currently return:
;; ANSWER SECTION:
www.rosenet.ne.jp.      86400   IN      CNAME   catv01.rosenet.ne.jp.
catv01.rosenet.ne.jp.   65992   IN      A       210.230.70.2
when you are experiencing the problem...  everything else seems OK; though
the PPP stats (RX bytes:54 (54.0 b)  TX bytes:54 (54.0 b)) are indicative
that very little has gone over the link so far (just established?), and
TX==RX _might_ be suspicious (possible loopback; though highly
unusual/unlikely) if one was grasping at straws -- although, suspect that
if the counters climb yet remain identical.

Pierre

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to