[ILUG] suse network problem.. anyone comment.!

[Fred]

> > So I have suse 9.0 pro installed
> > Connection to IrishBB works in windows but not suse.
> > The hardware seems to be fine.
> > Should be a case of just putting in the IP add, subnet mask, gateway
> > and primary DNS and off we go.
> > the problem is also found with a bootable suse 9.1 cd.
> > YAST seems to handle the settings of IP add, subnet mask, gateway and
> > primary DNS.



And after a long session of rebooting and testing I'm back.



Some answers and I think I can see the problem but have not yet managed to
fix it with messing about.

(Name server settings!!)



>From YAST



IP address  = 62.231.60.201

Subnet Mask = 255.255.255.192



Host name and name server configuration

Host Name = linux

Domain Name = local



The Name Server and Domain Search settings are empty.



Routing configuration

Default Gateway = 62.231.60.193



DHCP Client Options

Nothing set here except default test in host name to send.

Host Name to send = AUTO



1) What is the default gateway address  62.231.60.193



2) Can you ping that address?



PING 62.231.60.193 (62.231.60.193) 56(84) bytes of data.

64 bytes from 62.231.60.193: icmp_seq=1 ttl=255 time=62.2 ms

64 bytes from 62.231.60.193: icmp_seq=2 ttl=255 time=2.40 ms

64 bytes from 62.231.60.193: icmp_seq=3 ttl=255 time=54.5 ms

it kept on going !!!



3) Is that address correctly configured as your default route?

looks like default gateway is set ok

linux:/home/Fred # netstat -rn

Kernel IP routing table

Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface

62.231.60.192   0.0.0.0         255.255.255.192 U         0 0          0
eth0

0.0.0.0         62.231.60.193   0.0.0.0         UG        0 0          0
eth0





4) Results of ping to linux.ie



linux:/home/Fred # ping 193.1.31.98

PING 193.1.31.98 (193.1.31.98) 56(84) bytes of data.

64 bytes from 193.1.31.98: icmp_seq=1 ttl=55 time=235 ms

64 bytes from 193.1.31.98: icmp_seq=2 ttl=55 time=18.4 ms

64 bytes from 193.1.31.98: icmp_seq=3 ttl=55 time=42.2 ms

it kept on going !!!



5) How are your name servers set up? Do  'cat /etc/resolv.conf'

there is no resolv.conf file in the /etc/  folder

cat/etc/resolv.conf has no file



Looks like I need to set up some name server settings

But what settings to use? Shuld it be like the Secondary DNS Server or
something

Thanks.



PS. Niall I think U should keep this and use it from time to time as an
after signature thingy. lol
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
 P.S. The next time I am accused me of being short with neophytes I will
 have this email carved in ogham on an oak stick and will beat the
 accuser with said stick.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>


From: "Niall O Broin" <niall at magicgoeshere.com>
To: "Fred" <woodfrederick at hotmail.com>
Cc: "ilug" <ilug at linux.ie>
Sent: Tuesday, November 09, 2004 12:12 AM
Subject: Re: [ILUG] suse network problem.. anyone comment.!


> On 8 Nov 2004, at 23:22, Fred wrote:
>
> > Ok... I do see the point being made though it is through my a misted
> > eyes of
> > hours on the suse site and other places.
> > I did try ilug before but have had to put it on hold and restarting to
> > test
> > things is so .... errr how to put it.. mouth-wateringly teeeeeedious.
> > But I'll not let it get to me before its solved. there has to be
> > another way
> > other than M/S.
> >
> > So I have suse 9.0 pro installed
> > Connection to IrishBB works in windows but not suse.
> > The hardware seems to be fine. Have tried three network cards and one
> > was
> > not picked up.
> > Should be a case of just putting in the IP add, subnet mask, gateway
> > and
> > primary DNS and off we go.
> > the problem is also found with a bootable suse 9.1 cd.
> > YAST seems to handle the settings of IP add, subnet mask, gateway and
> > primary DNS.
>
> Yes, Yast will set those things - based on information from you. But we
> don't know are they set correctly. Some of the previoulsy mentioned
> further questions:
>
> Note - lacking a better means of emphasis, commands which you should
> type e.g. in a konsole session are enclosed in 'quotes like this' The
> 'quotes' should not be typed - just what is between them.
>
>
> 1) What is the default gateway address?  [For this discussion, we'll
> assume it's a.b.c.d]
>
> 2) Can you ping that address? i.e. what happens when you do  'ping
> a.b.c.d' ? If all is in order, you should get something like:
>
> PING a.b.c.d (a.b.c.d) 56(84) bytes of data.
> 64 bytes from a.b.c.d: icmp_seq=1 ttl=64 time=50.198 ms
> 64 bytes from a.b.c.d: icmp_seq=2 ttl=64 time=49.878 ms
>
> 3) Is that address correctly configured as your default route? i.e. if
> you do  'netstat -rn' do you get a line of output resembling this
>
> 0.0.0.0 a.b.c.d 0.0.0.0 UG 0 0 0 eth0
>
> 4) If 2) and 3) are as they should be, you should now get a positive
> response to  'ping 193.1.31.98' which is the IP address of www.linux.ie
> (fingers crossed it won't change sometime very shortly)
>
> 5) How are your name servers set up? Do  'cat /etc/resolv.conf' and you
> should see at least one, preferrably two or three lines beginning
> nameserver and followed by an IP address e.g.
>
> nameserver e.f.g.h
> nameserver i.j.k.l
>
> You should be able to ping as in 2) both of these addresses i.e. 'ping
> e.f.g.h' and 'ping i.j.k.l'
>
>
> If all of the above provide positive responses, then your networking is
> correctly setup, and you should now be able to access the Internet by
> name  e.g.   ping www.linux.ie . I suspect from what you have said that
> this is NOT the case. If I'm correct, do let us know where things
> failed in the above trail.
>
>
>
> Niall
>

>
>