November 10, 20232 yr Hey everyone, I installed a Mellanox ConnectX-3 Pro Dual Port 10Gb SFP + card into my unraid server and now networking has disappeared. the IP was 192.168.0.2 and it still shows thats what the IP is, but i cant ping it, nor can i ping out from the server. I remember having this issue with another unraid server, and my solution at the time was to remove the fiber card and stick to 1gb ethernet. How can I make this work with the fiber card?
November 14, 20232 yr Author Diagnostics attached. Other details that might help: When I ifconfig i get the proper IP address in eth0 along with the proper subnet mask and gateway. When I ping myself I get a reply, but if I ping anywhere on the internet it times out. I Think that when I pinged my router at 192.168.1.1 I got a reply, if im remembering correctly. I can go back into the server room later today to confirm this. thank you for your help! monte3-diagnostics-20231114-1213.zip
November 14, 20232 yr Community Expert Have a look at the ethtool.txt file in the system directory of the Diagnostics file. eth0 through eth3 are 1Gb NIC's and eth4 and eth5 are 10Gb NIC's. Only the eth0 one has an active link. (But still you should still have a active LAN connection...) The IP address is 192.168.0.2 for eth0 as you indicated. You say you are ping'ing various places BUT you don't say from what devices! Please run ping tests from your PC and from the Unraid server. And tell us the results from both places.
November 15, 20232 yr Community Expert Like Frank mentioned there's no link on the 10GbE NICs, but you should still be able to access the server on the gigabit LAN.
November 15, 20232 yr Author Sorry for not giving more details. Here are the current settings when i ifconfig: br0:: ip: 192.168.0.2 gateway: 192.168.1.1 subnet mask: 255.255.252.0 broadcast 0:0:0:0 dns: 192.168.1.4 and 192.168.1.7 and eth0 shows: eth0 UP, broadcast,running, multicast but has no IP information Pinging from my laptop to 192.168.0.2 times out pinging from unraid to google.com times out pinging from unraid to 192.168.1.1 or any other LAN IP times out pinging 192.168.0.2 from itself pings back fine .... when I play with the network settings this is what i find........... when I enable another network card I am able to ping it but i still dont get internet when I change the static IP address to automatic on eth0 i get a 169. address when i change the IP settings of eth0 to automatic I get 192.168.1.x IP but I still cant ping out I really dont understand. Everything was working perfectly fine up until I installed the fiber card. I checked on my notes from 6 months ago on a different unraid server; I installed a fiber card into it and the networking stopped working. even after playing with it for several hours I was still unable to ping anything or get any internet, so I ended up taking out the fiber card, unfortunately. This was on a completely different server with all totally different hardware including a different fiber card. Is there some bug that occurs when installing a fiber card? It just odd that I get the exact same 2 results from installing a fiber card. Thank you for any and all help everyone is providing
November 16, 20232 yr Community Expert 13 hours ago, mtseymour said: ip: 192.168.0.2 gateway: 192.168.1.1 This doesn't look right, they should be on the same subnet, suggest deleting/renaming /boot/config/network.cfg and reboot, that will reset the LAN settings to default DHCP, then post new diags.
November 16, 20232 yr Author 8 hours ago, JorgeB said: This doesn't look right, they should be on the same subnet, suggest deleting/renaming /boot/config/network.cfg and reboot, that will reset the LAN settings to default DHCP, then post new diags. I will try this and report back
November 20, 20232 yr Author in an attempt to keep things simple, I have removed the fiber card. I really just need my old IP settings back. The IP was originally set to 192.168.0.2.. one of my dockers wont seam to run without eth0 being that IP When I try to set eth0 to 192.168.0.2 it says eth0 disconnected, check cable. Currently it is auto connected DHCP to 192.168.101.68 Diags attached monte3-diagnostics-20231120-1311.zip
November 21, 20232 yr Community Expert offered 192.168.101.68 from 192.168.100.1 I'm not a network specialist but again this is not normal, router is assigning IPs from a different subnet.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.