Hi,
I've just installed Fedora Linux Core 2 on a 2.6Mhz, 512Mb box, dual boot
with Windows XP. But I am unable to connect to the net.

The modem is a D-Link DFM-560E external. I've configured it with KPPP -
dev/ttyS0 - and it connects to my ISP. I've pinged the ISP ip address and
it responds. I checked with netstat -a and found no tcp listed under
Proto, so I put domain and nameserver details in /etc/resolv.conf and on
rerunning netstat -a got tcp listed.

I did all this using the old Linux Unleashed reference, I'm a newcomer to
Linux, I guess this is obvious, tho my background in Windows OSs is fairly
broad. Despite all this when I try to access a remote site, the web
browser returns a not found error message.

My problem is that I have run out of ideas on which way to go now. Any
help would be much appreciated

Roy

Roy Stannard wrote:

> Hi,
> I've just installed Fedora Linux Core 2 on a 2.6Mhz, 512Mb box, dual boot
> with Windows XP. But I am unable to connect to the net.
>
> The modem is a D-Link DFM-560E external. I've configured it with KPPP -
> dev/ttyS0 - and it connects to my ISP. I've pinged the ISP ip address and
> it responds. I checked with netstat -a and found no tcp listed under
> Proto, so I put domain and nameserver details in /etc/resolv.conf and on
> rerunning netstat -a got tcp listed.
>
> I did all this using the old Linux Unleashed reference, I'm a newcomer to
> Linux, I guess this is obvious, tho my background in Windows OSs is fairly
> broad. Despite all this when I try to access a remote site, the web
> browser returns a not found error message.

1. Ping your ISP's name server. Get a response?
2. Post the contents of /etc/resolv.conf. Is the name server listed there,
if so in what way?

--
Paul Lutus
http://www.arachnoid.com

On Fri, 20 Aug 2004 22:35:40 -0700, Paul Lutus <nospam@nosite.zzz> wrote:

> Roy Stannard wrote:
>
>> Hi,
>> I've just installed Fedora Linux Core 2 on a 2.6Mhz, 512Mb box, dual
>> boot
>> with Windows XP. But I am unable to connect to the net.
>>
>> The modem is a D-Link DFM-560E external. I've configured it with KPPP -
>> dev/ttyS0 - and it connects to my ISP. I've pinged the ISP ip address
>> and
>> it responds. I checked with netstat -a and found no tcp listed under
>> Proto, so I put domain and nameserver details in /etc/resolv.conf and on
>> rerunning netstat -a got tcp listed.
>>
>> I did all this using the old Linux Unleashed reference, I'm a newcomer
>> to
>> Linux, I guess this is obvious, tho my background in Windows OSs is
>> fairly
>> broad. Despite all this when I try to access a remote site, the web
>> browser returns a not found error message.
>
> 1. Ping your ISP's name server. Get a response?


I pinged the remote address that was in the KPPP statistics dialog box,
203.55.231.88 and got:
64 bytes from 203.55.231.88 icmp_seq 0 tty255 time 110 msec
and so on until a break command. After this, a listing of number of
packets sent and received

Am I pinging the name server?

> 2. Post the contents of /etc/resolv.conf. Is the name server listed
> there,
> if so in what way?

Here are the contents of /etc/resolv.conf
#/etc/resolv.conf
domain www.ihug.com.au
name server 203.55.231.88

I entered these values assuming them to be referring to the name server.

thanks

Roy Stannard wrote:

> On Fri, 20 Aug 2004 22:35:40 -0700, Paul Lutus <nospam@nosite.zzz> wrote:
>
>> Roy Stannard wrote:
>>
>>> Hi,
>>> I've just installed Fedora Linux Core 2 on a 2.6Mhz, 512Mb box, dual
>>> boot
>>> with Windows XP. But I am unable to connect to the net.
>>>
>>> The modem is a D-Link DFM-560E external. I've configured it with KPPP -
>>> dev/ttyS0 - and it connects to my ISP. I've pinged the ISP ip address
>>> and
>>> it responds. I checked with netstat -a and found no tcp listed under
>>> Proto, so I put domain and nameserver details in /etc/resolv.conf and on
>>> rerunning netstat -a got tcp listed.
>>>
>>> I did all this using the old Linux Unleashed reference, I'm a newcomer
>>> to
>>> Linux, I guess this is obvious, tho my background in Windows OSs is
>>> fairly
>>> broad. Despite all this when I try to access a remote site, the web
>>> browser returns a not found error message.
>>
>> 1. Ping your ISP's name server. Get a response?
>
>
> I pinged the remote address that was in the KPPP statistics dialog box,
> 203.55.231.88 and got:
> 64 bytes from 203.55.231.88 icmp_seq 0 tty255 time 110 msec
> and so on until a break command. After this, a listing of number of
> packets sent and received
>
> Am I pinging the name server?
>
>> 2. Post the contents of /etc/resolv.conf. Is the name server listed
>> there,
>> if so in what way?
>
> Here are the contents of /etc/resolv.conf
> #/etc/resolv.conf
> domain www.ihug.com.au
> name server 203.55.231.88

There's the problem. "nameserver" must be one word.

> I entered these values assuming them to be referring to the name server.

You are clearly literate, knowing as you do that "nameserver" isn't really a
single word, but computers may be more literal (or arbtrary) than you
expect.

Also, I forgot to mention that the next test after you correct
/etc/resolv.conf is to start pinging by name rather than IP. It's always a
good idea to do these tests incrementally -- it uncovers errors with a
better focus.

--
Paul Lutus
http://www.arachnoid.com

> You are clearly literate, knowing as you do that "nameserver" isn't
> really a
> single word, but computers may be more literal (or arbtrary) than you
> expect.

Actually that was email typo, in etc/resolv.conf it appeared as
"nameserver". Sorry for the red herring.

>
> Also, I forgot to mention that the next test after you correct
> /etc/resolv.conf is to start pinging by name rather than IP. It's always
> a
> good idea to do these tests incrementally -- it uncovers errors with a
> better focus.
>
pinging www.ihug.com.au produces the following:
ping: unknown host www.ihug.com.au

I also tried setting up a dummy interface (as recommended in Linux
Unleashed) and placed the following code in etc/hosts:

ifconfig lo 127.0.0.1
route add 127.0.0.1

But still unable to get online. I also tried netstat -a. The tcp protocols
all have local addresses.

regards

Roy

Roy Stannard <roystannard@ihug.com.au> wrote in message news:<opsc51usmfla921z@news.ihug.com.au>...
[snip]
> pinging www.ihug.com.au produces the following:
> ping: unknown host www.ihug.com.au
>
> I also tried setting up a dummy interface (as recommended in Linux
> Unleashed) and placed the following code in etc/hosts:
>
> ifconfig lo 127.0.0.1
> route add 127.0.0.1

these are commands -- /etc/hosts is a list of ... hosts ;-0

> But still unable to get online. I also tried netstat -a. The tcp protocols
> all have local addresses.
>
> regards
>
> Roy

If you are running in some desktop/X environment use an X console (I'm
in KDE using Konsole) and copy the commandline and output like this:

[pbrain]$ ping -c4 203.55.231.88
PING 203.55.231.88 (203.55.231.88) from 24.204.x.x : 56(84) bytes of
data.
64 bytes from 203.55.231.88: icmp_seq=1 ttl=238 time=325 ms
64 bytes from 203.55.231.88: icmp_seq=2 ttl=238 time=296 ms
64 bytes from 203.55.231.88: icmp_seq=3 ttl=238 time=310 ms
64 bytes from 203.55.231.88: icmp_seq=4 ttl=238 time=310 ms

--- 203.55.231.88 ping statistics ---
4 packets transmitted, 4 received, 0% loss, time 3034ms
rtt min/avg/max/mdev = 296.300/310.739/325.156/10.202 ms

[pbrain]$ ping -c4 ihug.com.au
PING ihug.com.au (203.109.250.50) from 24.204.x.x : 56(84) bytes of
data.
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=1
ttl=47 tim e=261 ms
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=2
ttl=47 tim e=270 ms
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=3
ttl=47 tim e=261 ms
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=4
ttl=47 tim e=277 ms

--- ihug.com.au ping statistics ---
4 packets transmitted, 4 received, 0% loss, time 3023ms
rtt min/avg/max/mdev = 261.204/267.693/277.674/6.937 ms

[pbrain]$ ping -c4 www.ihug.com.au
PING www.ihug.com.au (203.109.250.50) from 24.204.x.x : 56(84) bytes
of data.
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=1
ttl=47 time=274 ms
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=2
ttl=47 time=269 ms
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=3
ttl=47 time=258 ms
64 bytes from tig-aus-syd-ns-50.ihug.net (203.109.250.50): icmp_seq=4
ttl=47 time=278 ms

--- www.ihug.com.au ping statistics ---
4 packets transmitted, 4 received, 0% loss, time 3023ms
rtt min/avg/max/mdev = 258.640/270.322/278.638/7.425 ms

Note the -c4 switch -- if you get no response after a few seconds,
then you can ^c. Without the -cX you're sending a non-stop string pf
pings -- no nice ;-)

Also output from:
ifconfig
netstat -nr or route -n
and netstat -ts is a bit less cluttered than netstat -a

In above, you will note that the domain www.ihug.com.au
(203.109.250.50) is _not_ the same as your nameserver (203.55.231.88)
which usually have no DNS listing.

When you say you can ping your ISP what exactly was the commandline?
The output?

This may help:
http://www.iinet.net.au/support/linux/index.html
tells how to set up ppp dial-up on Redhat but looks pretty generic --
give it a try ;-)

hth,
prg
email above disabled

In article <opsc51usmfla921z@news.ihug.com.au>, Roy Stannard wrote:
>pinging www.ihug.com.au produces the following:
>ping: unknown host www.ihug.com.au

What is the output of the command '/sbin/route -n' ?

>I also tried setting up a dummy interface (as recommended in Linux
>Unleashed)

Not needed.

>and placed the following code in etc/hosts:
>
>ifconfig lo 127.0.0.1
>route add 127.0.0.1

In /etc/hosts ???!!!??? Oh, my, no that's not supposed to be there.
/etc/hosts is meant to contain IP addresses and hostnames only. Red Hat
uses something like

127.0.0.1 localhost.localdomain localhost
192.168.1.1 columbia.phx.az.us columbia

while other people suggest that it should look like this:

127.0.0.1 localhost
127.0.0.2 localhost.localdomain
192.168.1.1 columbia.phx.az.us columbia

As far as Red Hat installations are concerned, it really doesn't make a
difference - they've been doing that for more than 8 years.

>But still unable to get online.

The fact that you can 'ping' the peer says that you are connecting. The
question is if you can see beyond the peer. Unfortunetly, 'ping' has
been abused so much that many people are configuring their systems to
ignore incoming pings.

>I also tried netstat -a. The tcp protocols all have local addresses.

/bin/netstat -nr (which provides nearly identical information to
the /sbin/route -n output) would be more interesting.

[compton ~]$ /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
12.22.195.11 0.0.0.0 255.255.255.255 UH 0 0 1 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 4198 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 20 lo
0.0.0.0 12.22.195.11 0.0.0.0 UG 0 0 5 ppp0
[compton ~]$

That's what you want to see - _two_ routes using the ppp0 interface. If
your installation doesn't have a local network, the line ending with eth0
would not be there.

[compton ~]$ /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
12.22.195.11 0.0.0.0 255.255.255.255 UH 0 0 1 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 4198 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 20 lo
[compton ~]$

Not like this - which only tells the kernel how to reach the peer, the
local network, and the loopback. How can you reach google? You can't
because there is no route to 0.0.0.0 with a mask of 0.0.0.0, which
translates to "everywhere".

Also, make sure the route to 0.0.0.0 with a mask of 0.0.0.0 is not trying
to use a host on the local network, like (in this example) 192.168.1.254.
That's an old problem with Red Hat since version 2.1. The installation
tool is overly helpful sometimes.

Old guy

Moe Trin wrote:

/ ...

> while other people suggest that it should look like this:
>
> 127.0.0.1 localhost
> 127.0.0.2 localhost.localdomain

No, no. These must both be 127.0.0.1, and they ordinarily appear on the same
line. "localhost" and "localhost.localdomain" are supposed to be aliases,
both mapped to 127.0.0.1.

The classic symptom, if this is not just so, is an indefinite wait on
boot-up for sendmail to try to resolve the host name and localhost.

--
Paul Lutus
http://www.arachnoid.com

Hi,

The output to route -n is


[root@localhost root]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
203.55.231.88 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 lo
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 203.55.231.88 0.0.0.0 UG 0 0 0 ppp0

To my innocent eyes that looks OK.

I contacted the ISP and they suggested putting the following in
etc/resolv.conf

search iinet.net.au
nameserver 203.0.178.191
nameserver 203.109.250.50

This was sufficient to get an internet connection up and running.
Fantastic!

Thanks Paul and Moe, your help is very much appreciated by this Linux
newbie. I feel I've just gone thru a rite of passage

Roy