[tlug] Onboard ethernet weirdness

["Jonathan Q" <jq@example.com>]

Here's a good one.

I recently got a new motherboard that has onboard Intel EEPro 100 ethernet.
 After hooking
everything up, I installed RH's Null beta and found that I could:

* Ping and traceroute
* Do DNS lookups

But could do nothing else, not even on my local LAN.  In other words, no
TCP connectivity.
I had a correct default route and could ping anywhere.

Figuring it was a problem with the beta, I put RH 7.3 in its place and
nearly fell off my chair
when it exhibited the exact same behavior.

After thinking about this for a long time after eliminating any firewall
suspects (by 
turning off all firewalling) I popped a NIC into a PCI slot and configured
it as eth1 on a
different address.  Bingo, full connectivity.

I can duplicate it over and over.  If only the onboard ether is up, no joy.
 If eth1 is up, it works.

Anybody ever seen this with before with onboard ether?  If so, what did you
do about it, besides popping in another network card?

Tx,

Jonathan

P.S.  I still have various small bits left, like scsi cables (internal and
external, IDE cables,
and various ayashii disks :-)  ) - also still have my dual PPro 180 box. 
Full tower.  It's free. Think of it as getting a TNT2 and a 2940UW for free
with a computer wrapped around 
them :-)

Jonathan

GPG key: DF12B4EF (5399 C834 3ABB C3AF 610C  5345 D5D6 E6EA DF12 B4EF)
gpg --keyserver pgp.mit.edu --recv-keys  DF12B4EF