FreeNAS 11.1 unable to get 10G network card hooked directly to another PC working + email issue

[K4sum1]

I recently built a NAS and I initially went with the latest TrueNAS 13, however after discovering that the connection slows to a crawl because 13 has a RAM leak problem that the devs haven't bothered to fix since 12, I went to 11.1 since I remembered it being pretty good, and having a better UI.

I configured my 10G card the same as I did with TrueNAS 13, 192.168.0.197, netmask 16/255.255.0.0, and it just doesn't work. I either get timed out errors or a white screen with infinite loading in my browser. It's going from my 10G card, the SFN5161T, through a 25ft CAT6 cable, to my main PC with an AQC107.

Another smaller issue that I don't care as much about is that I didn't even need to configure email for TrueNAS 13, but it just doesn't work with 11.1 even giving it an external server to use.

My NAS is:
ASRock Z97 Killer
Intel Core i7 4790K
16GB RAM
Samsung 830 128GB (boot drive)
wack combination of 2x6TB HGST Ultrastar 7K6000 and 2x4TB HGST MegaScale DC 4000.B in a 12TB RAID Z1 (I will replace with a 4x6TB eventually)
Solarflare SFN5161T

 

[jgreco]

Please provide some details about your network configuration.

If you have a direct connection between the two hosts, are both of them able to ping each other? What path do you envision is being used to reach the e-mail server?

 

[K4sum1]

The stock Killer E2200 LAN from the Z97 is going to my router (Linksys WRT1900ACv2 with OpenWRT), which my main PC is connected to as well with it's integrated I211 LAN. I can access the NAS through the I211 LAN, without any issues.

The SFN5161T is going directly to the also integrated AQC107 LAN in my PC, and that doesn't work with 11.1. I tried pinging the server through the 10G LAN (192.168.0.197) from my PC, and this is what I get.


For the email, I'm guessing it would go through the router to my modem to the interwebs. I've tried two different email services (gmx.com and cock.li), and they don't work. I just tried it and got a "Your test email could not be sent: [EFAULT] Failed to send email: [Errno 65] No route to host", which I don't think is what happened before. I wanna say I got a different error before, and it took a while instead of this error which is immediate.

 

[jgreco]

Why don't you provide us with some of the networking configuration, such as IP addresses on interfaces, default gateways, etc. This is typically interrelated.

 

[K4sum1]

E2200/I211 is auto/DHCP so no use showing it

 

[jgreco]

E2200/I211 is auto/DHCP so no use showing it

That's not true. Especially if it happened to be making assignments out of 192.168.0.0/24. One of the big reasons I asked is because it is a common error to let DHCP make assignments but then have a conflicting network with static assignments. As I previously said, this is often interrelated.

 

[K4sum1]

That's not true. Especially if it happened to be making assignments out of 192.168.0.0/24. One of the big reasons I asked is because it is a common error to let DHCP make assignments but then have a conflicting network with static assignments. As I previously said, this is often interrelated.

It's 192.168.1.x/24.

 

[jgreco]

So that's obviously a major problem for you. Your other network is 192.168.0.0/16, which is a superset of 192.168.1.0/24. Your netmask for all hosts on the 192.168.0.0/16 network probably needs to be /24 instead of /16 -- even if it is just those two pointopoint hosts.

 

[K4sum1]

I did try a netmask of 25 since the 192.168.1.x network is 24, to get it working I also lowered the IP for the NAS to fit into a netmask of 25, but I got the same thing.

 

[jgreco]

It shouldn't have been necessary to use a /25 netmask. Mmm.

So let's establish what works and what doesn't.

From the console of your NAS, please try to do the following pings. Use control-C to stop the command once done.

ping 192.168.1.189
ping 8.8.8.8
ping 192.168.1.1 (guessing this is your gateway)

From the PC, try

ping 192.168.0.197
ping 192.168.1.197

 

[K4sum1]

So first command on the NAS hung, but I think I know why

Other two sent fine

PC pings work fine as well

 

[jgreco]

So it seems like your PC and your NAS are communicating, what happens when you try more complex things such as accessing the administrative interface, or mounting a fileshare?

 

[K4sum1]

So I decided to try 192.168.0.197 with SMB, and it kinda works? I can copy files to it, but when I try to read from the drive the copy dialog took a while to appear and it was stuck at 0%.

 

[jgreco]

You're using several questionable items in your network. The Marvell 10G card is known to be rather garbage (though theoretically it should work). I'm a little concerned seeing it on the same group as a VMware software bridge, though.

I'm also unclear on the Solarflare SFN5161T. In theory the Solarflare cards should work, but 10GBase-T is really a crappy technology and not well-tested, so from my perspective you're using two dodgy cards and a dodgy connection technology. Any chance you can stick a 1GbE switch in the 10GbE path just to see if THAT works?

 

[K4sum1]

I don't have a 1G switch, but I do have an old router, will see if I can configure it for the current setup and see what happens.

 

[K4sum1]

hmm

 

[jgreco]

So were you expecting Internet access?

 

[K4sum1]

No, I didn't hook it to the internet, the gateway doesn't load, which appears to be the same problem I'm having with the NAS. I can send data, but receive data at a very slow rate.

 

[K4sum1]

It's been a while but I think the AQC107 died. It says network cable unplugged, even though I haven't touched the cable. I've also tried various driver releases and still get the same problem.

Edit so it doesn't get bumped: I forgot to give an update, I reinstalled Windows later on and it just worked, but making a new thread since I have a weird issue now that could(?) be related.