Re: Network Problem configuration on SUSE 10.2

On Jun 7, 7:05 am, bonchi.mass...@xxxxxxxxx wrote:
Problem of network configuration

Help me please,

I have installed the OpenSuSe 10.2, all seem right but I'm not able to
connected to any devices in my network space and I'm not able too to
going out to internet.

I have follow the same procedure of configuration for SUSE 9.3, where
all worked fine without any problems.

After I have finished to install the new Open SUSE 10.2 I'm not able
to connect to the web space.

I give some details about my configuration:

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:A1:05:86:D8
inet addr:192.168.0.14 Bcast:192.168.0.255 Mask:
255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:904 errors:421 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:72631 (70.9 Kb) TX bytes:510 (510.0 b)
Interrupt:209 Base address:0xe800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:59 errors:0 dropped:0 overruns:0 frame:0
TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4156 (4.0 Kb) TX bytes:4156 (4.0 Kb)

I have used an IP static address, with traditional method ifup
selected in the YaST utility.

I do the ifdown of eth0, my network device.

# ifdown eth0
eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 31)
eth0 configuration: eth-id-00:08:a1:05:86:d8

I do an ifup command:

# ifup eth0
eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 31)
eth0 configuration: eth-id-00:08:a1:05:86:d8

And the end look the status:

# ifstatus eth0
eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 31)
eth0 configuration: eth-id-00:08:a1:05:86:d8
eth0 is up
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
qlen 1000
link/ether 00:08:a1:05:86:d8 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.14/24 brd 192.168.0.255 scope global eth0
eth0 IP address: 192.168.0.14/24
Configured routes for interface eth0:
default 192.168.0.1 - -
169.254.0.0 - 255.255.0.0 eth0
Active routes for interface eth0:
192.168.0.0/24 proto kernel scope link src 192.168.0.14
169.254.0.0/16 scope link
default via 192.168.0.1
1 of 2 configured routes for interface eth0 up

My router is IP:192.168.0.1 and work fine in window and old version of
SUSE with the same configuration !!! The roting table is:

# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
169.254.0.0 0.0.0.0 255.255.0.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 192.168.0.1 0.0.0.0 UG 0 0
0 eth0

I have tried to disable the IPV6 but it's the same.

When I try to do a ping :

# ping 192.168.0.14
PING 192.168.0.14 (192.168.0.14) 56(84) bytes of data.
64 bytes from 192.168.0.14: icmp_seq=1 ttl=64 time=0.069 ms
64 bytes from 192.168.0.14: icmp_seq=2 ttl=64 time=0.055 ms
...

Ok, to ping itself work !!!

When I try to ping my router:

# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.>From 192.168.0.14: icmp_seq=1 Destination Host Unreachable
From 192.168.0.14 icmp_seq=1 Destination Host Unreachable
From 192.168.0.14 icmp_seq=2 Destination Host Unreachable
From 192.168.0.14 icmp_seq=3 Destination Host Unreachable

...

The same thing happen when I try to ping every other machines present
on my network place.

If I try to ping it from another machines, seem not present on the
network.

Well, hope the somebody can help me to resolve this problem, thank you
very much..

Massimo

Massimo -- i just got the same thing you did -- at first i thought it
was the cable, and when i switched it to another port on the switch it
pinged locally and yahoo.com fine. Then after doing some more (local)
work -- copying the CDs to a local directory -- i am again cut off and
decided to google this.

Must be the NIC, because i have used same CDs for two other stations
over the last two weeks and all went like greased lightning.

Now i'm going to learn how to use YaST to replace a NIC(!) -- that is
unless you or anyone has found a fix?

br, -craig


.

Relevant Pages