Well this sounds to me like a configuration issue rather than a hardware/driver issue.
One thing that looks a bit odd to me is your list of nameservers (DNS).
nameserver 192.168.4.100
nameserver 192.168.8.100
These are local addresses on different subnets to your Suse box. I presume that one of these IPs belongs to your router or some other box handling DNS queries? Which is a bit odd as I would expect it to be on the same subnet as your Suse box (192.168.0)
If there is no route to these hosts, then that is likely why you cannot browse the web from your Suse box. Have you tried pinging them from your Suse box?
What I tend to do is use the DNS server my ISP gives me as the DNS server in Suse, ie using them in Suses network config. I find that if I put the actual IP address of my ISPs DNS servers in there, DNS lookups are much quicker than going via my router. Its worth a shot, but of course YMMV.