I have an older computer with Suse 9.0 and a recent installed Suse 9.2 on another. The problem is that I cannot connect to internet with Suse 9.2. Both computers have identical AMD79c978 (Home PNA) cards. Suse 9.2 recognized the card and configured it with DHCP in the same way as in my older computer. There is nothing wrong with the card because it connects to internet with Windows 2000. Both cards are connected to each other so I can surf on internet simultaneously with my computers and later on build a local network.
Because I have the advantage to compare two similar systems I wrote the command: ip address list eth0 on both of them and this was what I got:

For the older computer with Suse 9.0 that works

linux:/ # ip address list eth0
2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:e0:7d:9b:57:63 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.15/24 brd 10.10.10.255 scope global eth0
inet6 fe80::2e0:7dff:fe9b:5763/64 scope link


And this for the newer one with Suse 9.2 that sucks ( it worked well with Red hat, which I had before )

linux:/ # ip address list eth0
2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:e0:7d:9b:57:67 brd ff:ff:ff:ff:ff:ff
inet6 fe80::2e0:7dff:fe9b:5767/64 scope link
valid_lft forever preferred_lft forever


As you can see a whole line is missing and what do that valid-lft forever stuff mean.

I hope no one else has the same problem, but if you can solve this for me I would be grateful.

i am not using suse 9.2 but what i see in your configuration is that your older system as an IPv4 address and your newer system an IPv6 address.
and i don't know if your router or medium wich shares the internet is compatible with IPv6...
can't tell for sure cause i am not familiar with IPv6

I got this from http://www.linuxforum.com/forums/ind...showtopic=3024 and made a comparision. It is something peculiar with all this. I mean why I have an internet connection whith an older version of Suse and not whith the new 9.2


“If its a network card or a modem (PCI/AMR/CNR), post the output of these commands:
CODE
9.0 9.2
#cat /proc/pci Responded no such file
#cat /etc/modules.conf Responded no response
#cat /proc/modules Responded Responded
#/sbin/ifconfig -a Responded Responded
#lsmod Responded Responded



Additionally, for routing problems with ethernet/LAN/wireless connections, post the output of:
CODE
#/sbin/route -en Responded Responded


Also, if there is a problem in resolving machine names, post the output of:
CODE
#cat /etc/resolv.conf Responded no response


If your ethernet/wireless is detected as eth0, then post the output of the file contents:
CODE

#cat /etc/sysconfig/network-scripts/ifcfg-eth0 file does'nt exist no such file

The device file will be named either eth0, eth1, eth2, wlan0... This file is present in /etc/sysconfig/network-scripts directory in most Linux distributions. In SuSE, it is present in /etc/sysconfig/network directory.

If you are not sure what the problem is, supply all of the above info. “

That was that, and I do not know how to analyze this output.

It is a little bit messy. What I mean whith "responded, no responce" is that the first means Suse 9.0 and the latter Suse 9.2

Have you checked SUSE's firewall 2 Setup from YasT?

Yes, I disabled the firewall but it did not help.