can't connect puppy to the internet thru ADSL
Hello All,
I have Puppy 4.1.2 installed on a USB stick (frugal) and I can't connect it to the internet. When I start it at work it detects the network card and the LAN, and goes out to the internet with no problem. At home I have ADSL modem and I am using "Roaring Penguin PPPOE", I am giving it all the information it asks for on the "setup" : * ISP username * eth0 * on demand - NO * DNS server address - tried with and without * ISP access password * Firewall - 0 * adjust configuration - y I then click on "start" and after few seconds it says it is connected, but I don't see any webpages on FireFox. While trying to identify DNS problem I typed the ip address on the url line on FireFox, but it didn't load any pages. I could not ping any ip addresses on the internet. I verified with my ISP that the addresses on resolv.conf ARE the correct DNS servers addresses. I didn't write them there. Puppy wrote these addresses. It writes them there even if I supply it with a wrong DNS server address during setup. There's no ping to these two DNS addresses on puppy, although I do get a ping from them on my Win XP installation on the same machine (Hard drive). Ping to the gateway is ok. There's no problem with this machine what so ever when I boot it to the Win XP Pro installation. Following are redirections of ifconfig -a , route -n , and cat resolv.conf . Any help appreciated, Babypeng ========================================== ifconfig -a eth0 Link encap:Ethernet HWaddr 00:18:F3:4C:C5:72 inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:77 errors:0 dropped:0 overruns:0 frame:0 TX packets:173 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6773 (6.6 KiB) TX bytes:15568 (15.2 KiB) Interrupt:23 Base address:0xa000 eth1 Link encap:Ethernet HWaddr 00:C0:DF:09:EF:90 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) Interrupt:16 Base address:0xe000 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:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:136 (136.0 B) TX bytes:136 (136.0 B) ppp0 Link encap:Point-to-Point Protocol inet addr:84.228.238.41 P-t-P:212.199.17.108 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:25 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1983 (1.9 KiB) TX bytes:901 (901.0 B) ========================================== route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 212.199.17.108 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 0.0.0.0 10.0.0.138 0.0.0.0 UG 0 0 0 eth0 ========================================= cat /etc/resolv.conf nameserver 80.179.52.100 nameserver 80.179.55.100 ========================================= |
Quote:
Another thing: if you deal with IP-adresses DNS doesn't matter. So if you cannot ping an ip-adress outside your network, there must be something wrong independent of your DNS-settings. Markus |
All times are GMT -5. The time now is 02:59 AM. |