You are not logged in.
Had an old Dell desktop in which the motherboard failed (capacitors leaked), but was able to move the HD into another Dell with a similar architecture (Dell Optiplex GX270 ->Dell Dimension 8400). Everything seems to work fine except the wired internet.
When I boot up ip link shows the eth0 as "DOWN". Performing a
ip link set eth0 upseems to correct this except when I run
dhcpcd(or dhclient) "DISCOVER" packets are sent out with no response (dhcpcd keeps sending out discover packets until it times out).
lsmodshows that the correct module is loaded. Which is tg3 according to lspci -v which states the model as a
Broadcom NetXtreme BCM5751 PCIExpress
I've played around with the configurations in dhcpcd.conf, with unplugging and re-pluging the ethernet cable, unloading and reloading the kernel module, and any other possibly related suggestions I could find in the forums (which I've speant a few days search through).
Any advice?
EDIT: Since I've had this problem I've disabled the dhcpcd@eth0.service from systemctl (which was how I origionally was autoconnecting in the old computer) and have just been trying to connect manually.
SOLUTION: needed to register the new MAC address with the IT administrators of the network in order to be whitelisted.
Last edited by punk_physicist (2014-05-06 19:39:27)
Offline
Anything in dmesg? Maybe you need a firmware, but these are not usually with wired ethernet.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
dmesg|grep ethgives
[ 11.175315] tg3 0000:02:00.0 eth0: Tigon3 [partno(BCM95751) rev 4001] (PCI Express) MAC address 00:11:11:eb:db:03
[ 11.175325] tg3 0000:02:00.0 eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[ 11.175331] tg3 0000:02:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[ 11.175336] tg3 0000:02:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
[ 157.193110] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 158.886100] tg3 0000:02:00.0 eth0: Link is up at 100 Mbps, full duplex
[ 158.886117] tg3 0000:02:00.0 eth0: Flow control is on for TX and on for RX
[ 158.886150] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
EDIT: I believe that everything after 157 above is after I give the 'ip link set eth0 up' command.
Last edited by punk_physicist (2014-05-05 23:00:21)
Offline
All you should have to do is dhclient/dhcpcd. Have you tried static IP? Switching the HD shouldn't have any effect either.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
This is a network at my work where I have no access to routers etc... Can I use a static IP in this situation? If so, how do I decide what is a good/available address?
Offline
Maybe your dhcp server is ignoring the MAC address of your network card?
Offline
Maybe your dhcp server is ignoring the MAC address of your network card?
ip link gives my mac address as
link/ether 00:11:11:eb:db:03 brd ff:ff:ff:ff:ff:ff
dhclient says
Listening on LPF/eth0/00:11:11:eb:db:03
Sending on LPF/eth0/00:11:11:eb:db:03
dhcpcd says
eth0: ClientID 01:11:11:eb:db:03
but if I run
dhcpcd -I 00:11:11:eb:db:03 -v eth0I get
eth0: ClientID 00:11:11:eb:db:03
In all these cases the connection tries to connect (sending discover packets) and finally times out.
Offline
The dhcp server in your network might have a whitelist of MAC addresses and might be ignoring others. If you knew the address of the network card of your previous desktop, you could spoof it (unless you use the same network card). Or you could just ask whoever is responsible for the dhcp server.
Offline
The dhcp server in your network might have a whitelist of MAC addresses and might be ignoring others. If you knew the address of the network card of your previous desktop, you could spoof it (unless you use the same network card). Or you could just ask whoever is responsible for the dhcp server.
That seems to make sense, because now it's another motherboard with a different MAC address.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
The dhcp server in your network might have a whitelist of MAC addresses and might be ignoring others. If you knew the address of the network card of your previous desktop, you could spoof it (unless you use the same network card). Or you could just ask whoever is responsible for the dhcp server.
This was the problem.
Spoofing another computer on the network worked. I thought the IT had it set up so that you could get onto the local network in order to register your device/MAC address (which they also have), but it turns out IT requires you to fill out a form for any new device/MAC address for the network.
Marking the topic as solved.
Offline