Networking :: Gigabit Network Card For CentOS 5.4 Server
Feb 11, 2010
I am looking for a gigabit network card for my centos 5.4 server. I am looking for something known to work well with linux. I have been on the bestbuy site and I found a DLink (DGE-530T) card with support for linux from the vendor but after reading feedback from users with that card I am not so sure it is linux friendly. I am now thinking of buying online.
I've just set up a PC with CentOS 5.3 runing on near identical hardware to an existing 5.2 machine. Motherboard is Asus M2A-VM which I discover by chance generally works very well with CentOS. Ethernet is on board Nvidia.The older machine just did run gigabit speed without any intervention at all, rather to my surprise. The newer machine insists on running at 100 Mbit which is annoying as it is connected to a NAS through a gigabit dumb switch.
The obvious difference between the two is that ethtool on the older machine says that supported ports are TP, and so the port is TP. Whereas the newer machine says that supported ports are TP or MII and insists on running MII. I cannot change this with ethtool -s eth0 port tp. Perhaps not too surprisingly, mii-tool says that the supported speeds range up to 100 Mbit.
I have been trawling the web looking to see how to get my broadcom nic working on my Dell optiplex 380 with fedora 12. Basically it shows up when I run lspci but no where else, unfortunately I have no linux experience. Other things that I have tried were to check the blacklist driver file, which had no reference to the nic.
NIC: Intel 82574L Gigabit mobo network card Issue: After the server has been up for a random amount of time, the network connection is lost. Attaching a console and looking at ifconfig I see a large number of dropped packets and collisions.
use; Code: lspci -vxx to list the make manufacture of NIC and the device driver it is using.
In this case: Intel 82574L, e1000e Look in var/log/messages to get the version of the driver, in this case 1.0.2 Download .gz file with source code, follow instructions to install newest driver (e1000e.ko), in my case version 1.2.10. [URL]
I have a dual boot system (Suse 10.0 and Windows XP Pro) in my notebook. My notebook is toshiba m358, which has a Marvell Yukon Gigabit Ethernet Network Card (Marvell 88E8072) on it. My problem is this: in Windows XP Pro, the network card works well, but in openSUSE, the light on the network card does not turn on. I believe that there is no driver for the network card. I have tried several ways to solve this problem:
1. Download Marvell 88E8072's driver from "[URL]", whose name is "install_v10.85.3.3.tar.bz2", and then install it with following commands:
Code: # tar xfvj install_v10.85.3.3.tar.bz2 # cd DriverInstall # ./install.sh .....
Code: # modprobe sk98lin # WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. After I reboot the openSUSE, the light of network card is still off.
2. Follow "[URL]" to configure the Marvell 88E8072. It also does not work.
I recently swapped out my old network switch (10/100) for a Netgear GS105 gigabit switch. With the exception of my Fedora 10 laptop all the rest successfully connect at gigabit speeds. But my laptop (with an Intel Corporation 82566MM Gigabit Network Connection (rev 03)) will only connect at 100Mbps. If I look in the logs for my network card here is what I get:
I just upgraded from Ubuntu 9.04 64-bit, to CentOS 5.5 64-bit and my RT-73 USB network card doesn't seem to want to function. It always worked fine in Ubuntu by default (plug and play). Is there some setting I need to make to get this working?Even BT-3 (which is quite old) recognizes the RT-73.
I am running CentOS 5.3.The NIC on my motherboard does not support gigabit, so I bought a gigabit network card. I installed the network card and configured it via system-config-network. Everything seems to work fine as long as I keep a cable plugged into the original NIC. The original NIC works just fine if it is the only one with a network connection, but as soon as I uplug the original NIC I can no longer ping nor connect to the server via the gigabit NIC.
The original NIC is eth0, the new NIC is eth1. Is there something I need to do to tell the system that eth0 is not required or something? I've never encountered an issue like this before...
We have an old Zonet 10/100 switch in our home network that locks up whenever there's a power glitch longer than about a microsecond. (OK. It's not that bad but if the lights flicker, I usually end up going down to the basement to see if the switch is hung.) None of the computers or peripherals are affected by the glitches, BTW. Power-cycle the switch and everything starts working again. After putting up with this for months I finally picked up a Netgear 8-port 10/100/1000 switch to replace the Zonet. Unfortunately, when the Netgear switch is in the network, everything slows to a crawl before completely freezing up. Pinging other systems barely worksname would not work.Pinging another system by its IP address worked a little but packet losses of 70%-80% were the best I saw. At first. Then it gets to where the loss is 100%.
All systems were rebooted after the Netgear switch was inserted into the network. The systems that were capable of gigabit connections autosensed the new switch and set their port speed accordingly. And that's about all that works when the Netgear switch is present. (The Zonet is back in the network now.)One thing I have not tried is forcing the port speed on the gigabit-capable systems to 100Mb and re-inserting the Netgear switch into the network to see if the problem if due to running some of the ports at 1000Mb.The systems on the network are running various versions of Linux (with different kernel versions, of course). Most are due for upgrades to get them current but I was planning on hitting the systems that had gigabit-capable ethernet interfaces thinking that a.) 100Mb speeds have been around forever and no problems have been seen when everything was running at 100Mb in the past and b.) the gigabit support for the older kernels should be better (one system only supports an MTA of 1500 max at 1000Mb).
I just kickstarted this box - I used eth0 and had no issues. After booting - eth0 is not available/present. This was not an issue in 5.2. This is a dell 4600 - both the 100mb intel and gig broadcom are onboard. I am about to try a different kernel. This is not a show stopper - it's plugged into 100m switch and I can just use eth1 - but I am curious as to what is different and why this no longer works.
I have a Netgear GA311 PCI Gigabit Adapter. Any chance it might work with CentOS? It is not one of the cards listed when I do "NEW" Ethernet Adapter from the System Network menu. Maybe there is compatible choice?
I can't get wake up on lan (wol) to work on my network card.The strange thing is that before I had it working with the exact same hardware. But I was on Centos 5.4 then. Now I am on Centos 5.5.Am I correct in concluding that the sky2 driver does not support wake up on lan?
I had installed a Centos 5 server, with one network interface card and work find. Now I want to install ADSL (PPPOE) dial-up for internet in this server, so need to add a 2nd network interface card (RTL8139D or other) . After plug the network card, what I need to do in Centos to find this new card and config it?
I have a Broadcom Corporation NetXtreme BCM5721 network card on my server at work.Everything works fine for a few weeks, then randomly the network connection on the server will stop working. After it stops working, I will try to reconnect with the network manager, it shows a wired connection available, it shows the "connection in progress"animation, then the "connection disabled" icon.
I uninstalled the network manager and used manual configuration, but do you think the network manager was the issue? I can't have the server disconnecting randomly every few weeks with no way to know what the real problem is. Was there an issue with the network manager with 10.04?
I have just installed CentOS and it is working fine!I made a masquerade with the document there: I didn't used the script, because right now, I do not completely understand it, and obviously I am not modifying anything by leaving it like that.I was using Mandriva before and I am used to graphical tools My questions are:I add the following lines in my iptables:
[root@localhost ~]# service iptables stop [root@localhost ~]# iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE [root@localhost ~]# service iptables save
Suppose that it is not convenient to go behind a machine to have a look.So I want to use a command to show whether the cable is plugged into network card. (Media connected or not)Can ifconfig do this? Or another one?
Cost effective (the people want cheap) solution to increase server storage space with as little impact on throughput (what I want) as possible. I have a server that sends instructions to 20 clients to perform certain tasks. The clients send gigs of data back to the server for storage.
BACKGROUND INFORMATION Network: Gigabit Ethernet Clients: (20) HP, Solaris, Linux Linux Server: Dell R805 PowerEdge (QUAD Core Athlons 16 gigs of ram, 4 gigabit ports.
Selected directories are mounted (NFS) by clients. One directory to be mounted by the clients contains executable files. Mount commands are sent from the server (rsh) to the clients. Yes I know (ssh) but this is how the software was originally written so let's go with it.
The clients then receive commands to execute the binaries contained within the mounted directory. The binaries basically create an image of the clients filesystem including special applications. The client then sends the files and directories to the server which stores this �image�. This process can be reversed to restore a client to the initial baseline image.
In a nut shell, 20 clients are sending gigs of data to the server for storage. I need to attach a NAS (gigabit) to extend the storage capability of the server. The server would mount (NFS) to the hard drives on the NAS. The NAS, configured as a �direct attached storage� device (DAS), means the storage device is connected directly to the server and not the network (which makes it a DAS). This would provide direct storage expansion for the server. However, this configuration cannot be a bottleneck that significantly hinders performance.
I'm setting up an LTSP server using Ubuntu 10.4 64bit, and PXE connecting with thin clients using Atheros cards. The ltsp environment is 32bit.
Unfortunately I get an error message with "No interfaces found! Aborting..." and a kernel panic early during PXE boot.
After an enormous amount of investigation, I've narrowed it down to (probably) being the fact that the ltsp chroot environment doesn't have the correct driver for my network card (I believe it's atl1c). The correct driver IS available in Ubuntu, though, as I can successfully boot the thin client from both 64bit and 32bit live CDs and bring up the network interface.
how can I install the correct driver in the PXE environment?
I have a couple of servers which runs CentOS 5.5 and CentOS 5.4. We have decided to buy a UPS and we choose Eaton EX RT 11 plus eaton network management card minislot. I have read on the site of Eaton that they have two applications which could gracefully shutdown my servers - LanSafe and NetWatch. My experience with UPS and those applications is zero so I`m here for some advises? Do you prefer NetWatch over LanSafe?
I'm giving up trying to install Lenny as a server. The netinstall won't recognise my realtek 8139 chipset on the PCI ethernet NIC. I've googled so much i'm freakin loosing it. The install fails while getting an IP adress via DHCP. So a new networkcard is in order. Why not go for gigabit lan then. Which PCI gigabit LAN card is 100% guaranteed to work with Lenny net install cd?
I installed ubuntu server 9.10. During the install the onboard 10/100 land card was automatically installed and was used for updating packages. I just put in a DGE-530T gigabit ethernet card. I can see it recognized under lspci.01:07.0 Ethernet controller: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) (rev 11). It does not show up under ifconfig. The CD came with linux drivers. The readme talked about recompiling the kernel and a whole bunch of other stuff. Google was equally confusing. What do I do?