TrueNAS LAGG/VLAN Problem

[VioletDragon]

Hi,

There is a problem with the networking in TrueNAS I upgraded from FreeNAS to TrueNAS and im having problems with LAGG/VLAN issues. Cross VLAN is the problem, V80 Media and V103 Storage issues is connection just times out transfers starts but times out. This never use to happen in FreeNAS. If i create a VLAN80 on TrueNAS and access it on another machine in VLAN80 it works fine. I know this isnt a problem with networking side of things as it works on Ubuntu Server and Ubuntu Desktop so the issue relies on TrueNAS itself.

Any ideas?

Thanks.

Jack.

 

[Patrick M. Hausen]

Please provide a network diagram and post screenshots of your network interface configuration.

 

[VioletDragon]

Please provide a network diagram and post screenshots of your network interface configuration.

VLAN103 Storage,
VLAN102 LAN,
VLAN101 WIFI,
VLAN80 Media Network, Raspberry Pi, DAB Radio etc

When copying from VLAN103 to VLAN102 the transfer drops out, when transferring to VLAN103 it also drops out and times out.

Copying from and too VLAN101 works

VLAN80 works but when it wants too.

issue is with TrueNAS

 

[Patrick M. Hausen]

Are you using the TrueNAS as your router?

Did you disable hardware offloading for all physical interfaces?

 

[VioletDragon]

Are you using the TrueNAS as your router?

Did you disable hardware offloading for all physical interfaces?

Pfsense is the firewall. And no I haven't disabled that. Im using a Intel Quad 4 Port Lan Card. It's just TrueNAS I'm having a issue with.

 

[Patrick M. Hausen]

Please disable hardware offloading for all physical interfaces and try again. It is really not helpful to parrot that this is a TrueNAS issue. I got it already. Disable hardware offloading as a first measure to fix the issue.

 

[VioletDragon]

Are you using the TrueNAS as your router?

Did you disable hardware offloading for all physical interfaces?

If this helps. I can still ping the Server by command line but NFS and SMB just times out when started to transfer files.

 

[VioletDragon]

Please disable hardware offloading for all physical interfaces and try again. It is really not helpful to parrot that this is a TrueNAS issue. I got it already. Disable hardware offloading as a first measure to fix the issue.

OK I will try that.

 

[VioletDragon]

Please disable hardware offloading for all physical interfaces and try again. It is really not helpful to parrot that this is a TrueNAS issue. I got it already. Disable hardware offloading as a first measure to fix the issue.

Disabling hardware offloading makes the whole server become not accessible.

 

[VioletDragon]

Please disable hardware offloading for all physical interfaces and try again. It is really not helpful to parrot that this is a TrueNAS issue. I got it already. Disable hardware offloading as a first measure to fix the issue.

Had to reboot. But got the same problem as before connection just times out when starting to transfer. I give up on this TrueNAS.

Might be time to migrate over to something else as this wont work.

 

[VioletDragon]

this is all i get

 

[VioletDragon]

I also have no way of getting my DATA back on the Storage Pool neither as in this new version of TrueNAS it refuses to import! great 8 and half TB of data lost! i hate upgrading

I have a backup but thats going to take days all because of a poxy upgrade that has broke the Server!

 

[Patrick M. Hausen]

Might be time to migrate over to something else as this wont work.

Rest assured that it does work - with complex network topologies including VLANs. What is the VLAN and IP address of the client that is throwing the "timeout" error message?

I also have no way of getting my DATA back on the Storage Pool neither as in this new version of TrueNAS it refuses to import! great 8 and half TB of data lost!

What are you trying to do? What is the expected result? What happens instead? Details please. "Doesn't work" is not a problem report. My crystal ball is at the shop at the moment.

 

[VioletDragon]

VLAN103 is the Storage Network. 192.168.103
The machine has a IP of 192.168.1.9 that is throwing a Timeout error.

Machine in VLAN102 has a IP of 192.168.102.9

The Raspberry Pi in VLAN80 has a IP of 192.168.80
4

Everything times out to the TrueNAS server when VLANs are used

LAGG Interface has a IP of 192.168.1.1 same subnet of my workstation which works.

Going to VLAN 80, VLAN102 to VLAN103 all times out whether its copying or transferring using NFS or SMB. Can still ping.

If you have VLAN80 on truenas it works with the Pi. But going cross subnet it doesn't. Linux works as I tried it in a VM on a hypervisor and a dedicated machine.

 

[Patrick M. Hausen]

VLAN103 is the Storage Network. 192.168.103
The machine has a IP of 192.168.1.9 that is throwing a Timeout error.

OK. So you are trying to access the TrueNAS share on an IP in 192.168.103.0/24 from a client that is in 192.168.1.0/24 and has got an IP address of 192.168.1.9?

That traffic goes through your pfSense, which is the router for all of these VLANs, right?

Does the TrueNAS have interfaces in more than one VLAN or only in the storage network 192.168.103.0/24? What is the default gateway of the TrueNAS?

You still have not provided a network diagram and you expect me to guess your topology from random addresses and VLAN IDs you throw at me. This is not how support works. I need all available information about your precise network setup to diagnose this problem.

Anyway, I'm resident in Germany and off to bed, now.

Come back with more information and I will do the best I can tomorrow.

Kind regards,
Patrick

 

[VioletDragon]

OK. So you are trying to access the TrueNAS share on an IP in 192.168.103.0/24 from a client that is in 192.168.1.0/24 and has got an IP address of 192.168.1.9?

That traffic goes through your pfSense, which is the router for all of these VLANs, right?

Does the TrueNAS have interfaces in more than one VLAN or only in the storage network 192.168.103.0/24? What is the default gateway of the TrueNAS?

You still have not provided a network diagram and you expect me to guess your topology from random addresses and VLAN IDs you throw at me. This is not how support works. I need all available information about your precise network setup to diagnose this problem.

Anyway, I'm resident in Germany and off to bed, now.

Come back with more information and I will do the best I can tomorrow.

Kind regards,
Patrick

Hi,

I have fixed the problem. It seemed to be a issue with the way the VLAN was configured on the Cisco Switch. All VLANs can now copy files from and too the Storage Network. Weird problem tho although the VLAN was still pingable. I am also seeing speeds that i wasn't expecting. This new Server ive upgraded too is pretty fast.

Cheers for your help.

 

[Patrick M. Hausen]

It seemed to be a issue with the way the VLAN was configured on the Cisco Switch.

But it was a TrueNAS issue - sure.

What precisely was wrong with the configuration of your switch? If you report back what the problem was, others may profit from this thread. This is a community forum, not a company support channel.

Kind regards,
Patrick

 

[VioletDragon]

But it was a TrueNAS issue - sure.

What precisely was wrong with the configuration of your switch? If you report back what the problem was, others may profit from this thread. This is a community forum, not a company support channel.

Kind regards,
Patrick

Hi,

Problem was with the way the VLAN was implemented on the Switch. I have two SG500 that are stacked due to having two Hypvervisors, but on the Switch there is Ports to VLAN and VLAN Port Members. When using Ports to VLAN instead of VLAN Port Members it causes TrueNAS VLANs to not work. It only affected TrueNAS which is why i said its a TrueNAS issue. Ubuntu Server was fine with a Bond0 with 4 Ports using VLAN103 but not with TrueNAS.