iB::Topic::DNS problem

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » DNS problem

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (2) </ [1] 2 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: DNS problem, Everything looks fine but ....can't conn

< Next Oldest | Next Newest >

tito

Group: Members
Posts: 4
Joined: Mar. 2006

Posted: Mar. 16 2006,08:20

Hi everyone,

I have installed DSL on a 256mb USB stick and after some sweating it works fine (terrific I'd say), except that I can't connect to the internet.

I get the connection to my ISP right away, I run PPPoE, I am allocated a dynamic IP address, the nameservers are registered in resolv.conf, I can ping my own IP and that of the ISP, but then .... the browser tells me ... "cannot resolve DNS address". I cannot ping external sites by IP number either, so it's probably not a nameserver problem. I have Suse linux on the same machine and it connects fine.

Pasted below is the ifconfig output for DSL and for Suse. I then raise some questions and I'll be grateful for any feedback.

DSL ifconfig:
eth0 Link encap:Ethernet HWaddr 00:08:A1:80:1B:7B
inet addr:192.168.1.28 Bcast:255.255.255.255 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:375 errors:0 dropped:0 overruns:0 frame:0
TX packets:368 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30340 (29.6 KiB) TX bytes:31020 (30.2 KiB)
Interrupt:10 Base address:0x9000

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:100 (100.0 B) TX bytes:100 (100.0 B)

ppp0 Link encap:Point-Point Protocol
inet addr:82.54.82.135 P-t-P:192.168.100.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:336 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:18808 (18.3 KiB) TX bytes:97 (97.0 B)

Suse ifconfig:

dsl0 Link encap:Point-to-Point Protocol
inet addr:82.56.19.233 P-t-P:192.168.100.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:192 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:10881 (10.6 Kb) TX bytes:54 (54.0 b)

eth0 Link encap:Ethernet HWaddr 00:08:A1:80:1B:7B
inet addr:192.168.1.28 Bcast:255.255.255.255 Mask:255.255.255.224
inet6 addr: fe80::208:a1ff:fe80:1b7b/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:220 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17414 (17.0 Kb) TX bytes:2460 (2.4 Kb)
Interrupt:10 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: fe80::208:a1ff:fe80:1b7b/64 Scope:Link
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)

The only difference I can spot is the line

inet6 addr: fe80::208:a1ff:fe80:1b7b/64 Scope:Link

in the Suse eth0 output.

My questions are:
Is it relevant to my problem?
I believe it is.
How do I tell DSL to do the same Suse is doing?

Thanks a lot for any feedback.

tito

pr0f3550r

Group: Members
Posts: 378
Joined: Dec. 2005

Posted: Mar. 16 2006,12:08

DSL ifconfig:
eth0 Link encap:Ethernet HWaddr 00:08:A1:80:1B:7B
inet addr:192.168.1.28

192.xxx is not a public address, hence no internet connection.
How do you connect to the provider? Modem or router?
It looks like a problem with dhcp

--------------
THE QEMU FORUM: http://qemu.dad-answers.com/index.php

QEMU ON WINDOWS: http://www.h7.dion.ne.jp/~qemu-win/

How to use floppy, CD-ROM and hard disk - http://www.h7.dion.ne.jp/~qemu-win/HowToFloppyCdrom-en.html

How to use network - http://www.h7.dion.ne.jp/~qemu-win/HowToNetwork-en.html

tito

Group: Members
Posts: 4
Joined: Mar. 2006

Posted: Mar. 16 2006,13:24

Quote

I have a DSL modem which is always on. Note that the inet address 192.168.1.28 is there in Suse ifconfig log too, which corresponds to a working connection. Imu, 192.168.1.28 is the ISP server, on whose private network my comp lives. Actually the ISP allocates my dynamic IP address that changes every time I connect and is the 82.54.82.135 in DSL ppp0. My guess now that the source of the problem is authentication. I am connected to the ISP, otherwise I would not get a dynamic address everytime, but maybe authentication failure in DSL prevents me from accessing the net.

Thanks for this and further feedback,

t

tito

Group: Members
Posts: 4
Joined: Mar. 2006

Posted: Mar. 16 2006,14:50

Problem solved!

System->Net Setup->netcardconfig-> No DHCP -> Input manually the eth0 parameters from ifconfig Suse->send this message from DSL-Netscape.

Cheers,

tito

nihil75

Group: Members
Posts: 7
Joined: Mar. 2006

Posted: Mar. 18 2006,10:32

WOW!!!
10X man!!
i'v been braking my had at this for a month!!! i use wireless rt2500 pcmcia and
it didnt ping anything but my router and google ( a weird one...) ,
everything was ok according to resolve.conf, ifconfig etc...
u saved me with this workaround... i ow u tito

5 replies since Mar. 16 2006,08:20

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (2) </ [1] 2 >/

Damn Small Linux Board » Damn Small Linux » Networking » DNS problem