On 10/01/11 05:41, Rudi Ahlers wrote:
On Sun, Jan 9, 2011 at 11:13 PM, Robert Spangler
mli...@zoominternet.net wrote:
On Sunday 09 January 2011 13:33, Rudi Ahlers wrote:
Our intranet's WAN interface just stopped working yesterday, and I
can't figure it out.
Look in
On Mon, Jan 10, 2011 at 10:05 AM, David Sommerseth
d...@users.sourceforge.net wrote:
On 10/01/11 05:41, Rudi Ahlers wrote:
On Sun, Jan 9, 2011 at 11:13 PM, Robert Spangler
mli...@zoominternet.net wrote:
On Sunday 09 January 2011 13:33, Rudi Ahlers wrote:
Our intranet's WAN interface just
I love realtek - the resources they use tend not to conflict with other
cards or hardware, they don't use much cpu time, the drivers are mature, and
they don't cost much. What could be better? There does seem to be at least
one onboard realtek chipset that can have driver issues, but I use the
On Mon, Jan 10, 2011 at 11:49 AM, compdoc comp...@hotrodpc.com wrote:
I love realtek - the resources they use tend not to conflict with other
cards or hardware, they don't use much cpu time, the drivers are mature, and
they don't cost much. What could be better? There does seem to be at least
On Mon, Jan 10, 2011 at 12:08 PM, Rudi Ahlers r...@softdux.com wrote:
On Mon, Jan 10, 2011 at 11:49 AM, compdoc comp...@hotrodpc.com wrote:
I love realtek - the resources they use tend not to conflict with other
cards or hardware, they don't use much cpu time, the drivers are mature, and
they
I like your analogy David... rock is too small to be turned around now I
think you put it in the right context. It is always a good idea to check on
dmesg upon boot and make sure those modules are loaded as David mentioned. Try
to start from the beginning to troubleshoot the problem. Tow cents.
Thank you for the discrimination, but it's not appreciated. This is
not a multi-million dollar enterprise cluster, so please don't see it
as such. It's an in-house development server and really doesn't
justify thousands of dollars' worth of hardware. The NIC was working
fine for about 2 years
Rudi,
Sounds like a module conflict/misconfiguration, but anyway glad its working
back. have you upgrade this system with the latest kernel build. I am guessing
both onboard NICs are the same brand, take a look at messages and see if the
card give me problems in the future. make sure you look
On 1/10/11 3:12 AM, Rudi Ahlers wrote:
My immediate hunch is ... and I'm sorry to say it ... but your NIC is
often referred to as Realcrap NICs - unfortunately that's not without a
reason.
Thank you for the discrimination, but it's not appreciated. This is
not a multi-million dollar
Hey,
If it happens again, or maybe it might show in /var/log/messages, if there was
a MAC address conflict in the ifcfg files. I've seen where eth0 won't come on
as the MAC address set in the cfg file wasnt matching. Some times it fails
with a message on an ifdown ifup, sometimes it doesn't.
Tommy,
I think your scenario only pertain to those of us that clone macs with
different prefixes, we are assuming that rudi is using the original MAC from
the actual device. Not two macs are equal unless you change the physical device
parameters via mac-changer/modification. Let's hope he is
On Mon, Jan 10, 2011 at 8:58 AM, Lisandro Grullon
lgrul...@citytech.cuny.edu wrote:
Tommy,
I think your scenario only pertain to those of us that clone macs with
different prefixes, we are assuming that rudi is using the original MAC from
the actual device. Not two macs are equal unless you
(Don't *GET* me goiing devices changing from /dev/hda to /dev/sda[] ...)
[]
In centos, you can at least mount your storage drives like this:
[r...@yourpc ~]# blkid
/dev/sdb1: LABEL=sixtb UUID=f5ef20af-fd54-4f5e-8fce-2d4f262fcfbf
TYPE=ext4
Then add this at the bottom of fstab: (using your own
Hi all,
Our intranet's WAN interface just stopped working yesterday, and I
can't figure it out.
The machine has a Gigabyte motherboard, with on-board
RTL-8110SC/8169SC Gigabit Ethernet and D-Link PCI NIC for the LAN
side. I can get into the LAN side without an issue, but can't see the
WAN side
On Sunday 09 January 2011 13:33, Rudi Ahlers wrote:
Our intranet's WAN interface just stopped working yesterday, and I
can't figure it out.
Look in /etc/sysconfig/network-scripts. There you should see ifcfg-eth# If
ifcfg-eth0 isn't there copy ifcfg-eth1 to ifccfg-eth0 and then configure
On Sun, Jan 9, 2011 at 11:13 PM, Robert Spangler
mli...@zoominternet.net wrote:
On Sunday 09 January 2011 13:33, Rudi Ahlers wrote:
Our intranet's WAN interface just stopped working yesterday, and I
can't figure it out.
Look in /etc/sysconfig/network-scripts. There you should see
16 matches
Mail list logo
