SOLVED Cant connect to Truenas after changing router

[DigitalAngel]

hello guys, i have a problem connecting to my truenas DIY machine since i made a change in my network.

the NAS is an core i5 haswell based DIY build with onboard lan and mellanox 10gbit ethernet.

network was like this:

i switched out the switch (try saying it several times fast) with a TP Link Wifi Router because the Wifi of the cable companys router was always a nuisance.

it now looks like this:

Now, i can not open the trueNas webinterface, nor ping the NAS, nor connect to it, and the NAS itself does not connect to the internet as well.

i tried with automatic IP with dhcp and with manual setting it in the console. it sets an ip, i can also see that in the network overview of the router and the connection is made with 1gbit. but still no access. i also tried another PCI NIC and USB NIC. same problem. the cable is fine, my notebook connected first try.

All other devices in the network (notebook, TV, smartphones, workstation etc.) see each other and work fine. they just cant connect to the NAS.

Between Workstation and NAS there also was and is a 10gbit link with mellanox connectx-3 cards and static IPs wich still works fine and can transfer files and open the webinterface via that static ip.


i am clueless at this point. i guess its a software related truenas problem because all other devices work fine with the new router. does anyone have an idea?

Hardware:
Gigabyte H97M, 32GB, i5 4460, onboard NIC + mellanox connect-x 3, TP LINK Archer C6 Wifi Router

 

[DigitalAngel]

Out of curiosity i have thrown a cable from the onboard nic to the cable router directly (skipping the new tp-link router) and voila, connected and able to download updates from the web. so this works.

why does it not work with the tp-link router in between? do i need to set a gateway manually?

 

[sretalla]

What's probably important to understand is the network addresses of both routers and to know how you're setting the TrueNAS IP.

Are you using DHCP? some DHCP servers can supply default routes correctly to TrueNAS with the IP address, others seem to miss, so specifying it manually is needed.

It would also seem your new setup is potentially introducing double-NAT... look that up to see if you don't want it... you probably don't.

You may get better success by connecting your gbit cable to one of the LAN ports on the TP Link router (and turning off the DHCP server on the TP Link router... do that first).

 

[DigitalAngel]

i actually just found the problem, had the two networks (the whole gbit home network and the 10 gbit between the NAS and Workstation) in the same address space (192.1.xxx.xxx) which made one of them not work. i moved the 10gbit to 192.2. and now all is fine

 

[HoneyBadger]

Hopefully the address spaces are actually 192.168.1.x and 192.168.2.x as the other ranges (192.1.x.y and 192.2.x.y) are public IP spaces, and shouldn't be used on private networks unless you own them.

RFC 1918: Address Allocation for Private Internets

This document describes address allocation for private internets. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

datatracker.ietf.org

 

[DigitalAngel]

you are perfectly right and yes, they are 192.168.1.x and 192.168.2.x

Problem solved at this point.