Thanks for the feedback. Problem was not with the chip, problem was a managed switch to which the box was inadvertently connected. Replaced switch with hub, tried with both ElRepo and Realtek drivers, can see TCP packets now from other computers. Labelled data cables better so mistake won't happen again. Nice to know that the switch did exactly what it was supposed to do. Sorry for the unnecessary noise. benm _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: RealTek 8168B (Rev 02) NON Issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: RealTek 8168B (Rev 02) NON Issue
- From: "Ben Mohilef" <benm@xxxxxxxxxxxx>
- Date: Tue, 09 Jun 2009 09:31:49 -0700
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <4A2E6071.7040006@xxxxxxxxx>
- Priority: normal
- References: <4A2BEA88.24019.205026E@xxxxxxxxxxxxxxxxx>, <4A2CDF1C.28027.93A1E2@xxxxxxxxxxxxxxxxx>, <4A2E6071.7040006@xxxxxxxxx>
- References:
- RealTek 8168B (Rev 02) Issue
- From: Ben Mohilef
- Re: RealTek 8168B (Rev 02) Issue
- From: Ben Mohilef
- Re: RealTek 8168B (Rev 02) Issue
- From: Tosh
- RealTek 8168B (Rev 02) Issue
- Prev by Date: Re: PAE or use 64-bit?
- Next by Date: Public key for freetype-2.2.1-21.el5_3.i386.rpm is not installed
- Previous by thread: Re: RealTek 8168B (Rev 02) Issue
- Next by thread: Disabling IPv6 in CentOS 4.7
- Index(es):
 |