[SOLVED] SuSE 10 & 11 network issue. SuSE 7 OK.

[N5SBP]

On install my Win XP and SuSE 7.3 recognized and configured my LAN with no problem. I could even get on the Internet immediately. But with the 10.3 and 11.0 SuSE I cannot even PING my default router (a Linksys WRT54G; hard wired NOT wireless). Configuring with Yast did not work so I've resorted to manual configs.

Attached please find the scenerio I went through to provide documentation (suse11.txt). I can summarize it by saying: (1) after configuring an IP address and default router, (2) I try a ping to the router which fails, (3) I unplug/plug the ETH cable in the router and in a few seconds, (4) the pings begin to work until, (5) after 52 good pings, it fails again.

I've attached a second file containing several log files (LogCfg.txt). I can see a "deadly SIGTERM" and some firewall rejects but don't understand the significance. Network cfg files included...most params are null.

Any suggestions would be appreciated,
Jim

[N5SBP]

How do you diagnose errors on your LAN connection that you see in a "ifconfig eth0" display? I'm getting tons of errors and good communications to the LAN/Internet break after 30-40 seconds and maybe just 50-60 datagrams.

Firewall is OFF, IPV6 is OFF, Network Mgr is OFF.

Is there a trace or log that will tell me what these errors are? /var/log/messages sometimes gets a TERMKILL but sometimes not. DHCP or static fail the same way.

thx,
Jim

[N5SBP]

I probably should have listed the HW I was using with the SuSE 10.x and 11.0 My machine is an older Dell which means it has a cheapie (I guess) Davicom DM9102 eth card in it. According to some Googling and some other forums, this card is notorious for being very flaky with the tulip driver that SuSE 10 & 11 is so proud of! So proud, they even blacklisted the dmfe driver in favor of the tulip driver. Well for the Davicom eth card this is just backwards!