mrmad1966
asked on
Ubuntu NIC Realtek - Not Working..
Hi all
I have a Ubuntu 8.04 server and am wanting to upgrade my network to 1Gb. The PCI network card I purchased was advertised as being compatible with linux. It has the RTL 8169 chipset but after inserting the card into the machine.
It fails to work so far I have done the following:-
typed dsmesg|grep eth
typed lsmod|grep r819
Please see screenshot for results - I really am stumped here if anyone can help I would be very grateful..Wish I could offer a 1000 points here !!!
I have a Ubuntu 8.04 server and am wanting to upgrade my network to 1Gb. The PCI network card I purchased was advertised as being compatible with linux. It has the RTL 8169 chipset but after inserting the card into the machine.
It fails to work so far I have done the following:-
typed dsmesg|grep eth
typed lsmod|grep r819
Please see screenshot for results - I really am stumped here if anyone can help I would be very grateful..Wish I could offer a 1000 points here !!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Results of earlier commands..Sorry about not attaching earlier
NicProblem.png
NicProblem.png
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ifconfig -a
ifconfig.png
ifconfig.png
ASKER
/etc/network/interfaces
interfaces.png
interfaces.png
Looks like the interface is there - just not configured/connected
You'd need to set the interface up either using the Gui (is the screenshot from the box with the NIC or is it ssh'd into another box?).
If you connect the network cable into the interface and type
sudo ifconfig eth2 192.168.1.253/24
(This will only hold the settings until the interface is restarted - to make this permanent you would need to add something along the lines of:
iface eth2 inet static
address 192.168.1.253
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
to the /etc/network/interfaces file)
you should be able to ping other devices on the lan (and ifconfig will show both interfaces). You should also be able to view interface status and statistics using
sudo mii-tool
Obviously replace the network settings with your own.
Hope this helps
You'd need to set the interface up either using the Gui (is the screenshot from the box with the NIC or is it ssh'd into another box?).
If you connect the network cable into the interface and type
sudo ifconfig eth2 192.168.1.253/24
(This will only hold the settings until the interface is restarted - to make this permanent you would need to add something along the lines of:
iface eth2 inet static
address 192.168.1.253
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
to the /etc/network/interfaces file)
you should be able to ping other devices on the lan (and ifconfig will show both interfaces). You should also be able to view interface status and statistics using
sudo mii-tool
Obviously replace the network settings with your own.
Hope this helps
Sorry - was posting that as you posted the /etc/network/interfaces.
This should be fine - you'd need to restart networking for this to take effect
sudo /etc/init.d/networking restart
This should be fine - you'd need to restart networking for this to take effect
sudo /etc/init.d/networking restart
ASKER
OK guys...getting there.. Turns out I had a faulty cable. I have replaced the cable and now the NIC is connected at Gb speed BUT, after a reboot when I type ifconfig -a it appears that the static ip address I want to use has been lost..
Any other ideas ?
Any other ideas ?
you need to add
auto eth2
to your /etc/network/interfaces
Otherwise your networkcard will not get the address assigned.
auto eth2
to your /etc/network/interfaces
Otherwise your networkcard will not get the address assigned.
yes - auto brings up the interface when the network startup script is run - alternatively you can manually run
sudo ifconfig eth2 up
sudo ifconfig eth2 up
ASKER
This is going to be the main NIC in this file server so it needs to be static and not assigned by dhcp. If you have a look at the /etc/network/interfaces screenshot above I am under the impression that those settings should be correct ....
ASKER
should the current /etc/network/interfaces not bring the NIC online ? Running sudo ifconfig eth2 up manually is not really an option everytime the server is rebooted......The current eth0 has worked faultlessly for the last couple of years......
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You should assign a netmask of 255.255.255.32 to one of the both cards, because both nics are connected to the same network and one of them should not answer to broadcasts.
I assume that you are going to use eth2 as your primary card for the server. So assign the .32 netmask to eth0
I assume that you are going to use eth2 as your primary card for the server. So assign the .32 netmask to eth0
ASKER
ok...all sorted but 1 final query for you two heros..........
natoka - you assumed correct eth2 is my primary card. So I had assumed that I could leave the original eth0 in the computer (but just leave it disconnected) but at the same time assign a different IP address..And then change the eth2 card to the same IP address as the old eth0 (so clients were unaffected).. But why after a reboot could no clients access this machine ? It was only when I physically removed the original eth0 that all worked fine ? I tried pinging from the clients with no reply.. I also tried pinging from the server, it could not see any clients and the ping reply said it was from the eth0 IP address that was disconnected .....Bizzare but Im hoping you can educate me !!!!
Thanks Again
natoka - you assumed correct eth2 is my primary card. So I had assumed that I could leave the original eth0 in the computer (but just leave it disconnected) but at the same time assign a different IP address..And then change the eth2 card to the same IP address as the old eth0 (so clients were unaffected).. But why after a reboot could no clients access this machine ? It was only when I physically removed the original eth0 that all worked fine ? I tried pinging from the clients with no reply.. I also tried pinging from the server, it could not see any clients and the ping reply said it was from the eth0 IP address that was disconnected .....Bizzare but Im hoping you can educate me !!!!
Thanks Again
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great people.....Thanks to you both...
ASKER
lspci.png