George ,
1 . Are the cards sharing the same IRQs ? PCI cards should not worry about
that , but sometimes it becomes an issue
2. Have you checked your tty10 for errors concerning TX failures etc , etc
(You could get a hint or two)
3. Connect the outside interface to a switch first rather than directrly to
the ISP equipment and try a ping. My guess would be something to do with
the Duplex settings of the card , mii-tool would help , though it might
work for your cards
4. Forget about 9.1 and go back to a more stable version like 8.2 . ( I
failed to configure my Monitor and Display card . {Dell Optiplex GX270})
Kind Regards
Fred.
Quoting Lule George William <[EMAIL PROTECTED]>:
> Hello Guys,
> I am dying to say (read type) some very, very, very nasty things about
> SuSE 9.1 but let me hold them back and just put across the source of my
> frustration.
> Last Friday (I am typing this mail at the end of Wednesday) I made a
> clean install of SuSE 9.1 on a new machine with specs: HP Compaq, Intel
> Xeon Processor 2.4 GHZ, 1 GB RAM, 2 x 40GB HDD. Since among its other
> intended functions, it also going to be our proxy, I added a 2nd n/w
> card on top of its onboard gigabit ethernet card and then embarked on
> the installation.
> It detected my network cards O.K and using YAST, I I.P addressed them
> and after which I did the proverbial ping test. I had configured the
> onboard to face our internal network and the other card to face the
> internet. The onboard returned the ping from all the internal machines
> O.K, but the second card gave me a network unreachable error. Re-check
> the values, re-enter them all O.K but still network unreachable errors.
> As a test, at this point, I decided to configure the onboard instead to
> face the internet and the second card to face the internal network. The
> ping responded form all the machines on the internal network but got
> network unreachable errors from the onboard card. That confirmed both
> cards to be O.K.
> When I switched the onboard to face the internal n/w again, BOTH cards
> returned network unreachable errors!!!!!! I got two other WORKING cards
> placed them into the machine, spent my saturday, my sunday, monday,
> tuesday, googled my (oops no nasty words!!) off and the circus
> continued, ping from inside, network unreachable errors from outside.
> In between, I configured BIND which returns a succesfull dig @localhost
> but no remote servers found error when I try to dig anything else. I
> think its because of the other problem. I installed and configured
> squid which is also dying with a DNS name lookup tests failed error. I
> still think it is the other problem. I have configured and reconfigured
> SuSEfirewall2 a million times but still no luck. I have disabled ipv6,
> set static routes, checked all files in /etc/sysconfig/network against
> recommended ones and so many other things but still no luck.
> Can someone out there save my sanity?? Honest!! This thing is driving
> me mad!!!!
>
> ************************************************************************
> Lule George William (Mr)
> Network and Systems Administrator
> Uganda Martyrs University, Nkozi
> P.O. Box 5498 Kampala
> Uganda
>
>
> ---------------------------------------------
> This service is hosted on the Infocom network
> http://www.infocom.co.ug
>
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
---------------------------------------------
This service is hosted on the Infocom network
http://www.infocom.co.ug
