Jump to content

I can't wrap my head around the networking in my home...

Go to solution Solved by YoungBlade,
Just now, WereCat said:

@Needfuldoer @YoungBlade

well, after I did that I can access internet over the TP Link but now I can't acess NAS server connected to it or even the settings of the router.

Doing that would almost certainly change the IP address to both the router and the NAS.

 

Did you look in the ISP router settings for their current IP addresses?

Can you help me figure out what I need to do so that I can make my other devices connect to my Jellyfin running on TrueNAS? I have to connect to the TP-Link router to be able to use it but I can't connect half of the devices to this router and if I want to do ANYTHING that's on the NAS I have to be connected to the TP-Link.

 

This is my network setup at home.

image.thumb.png.845a987817410bfe19b541856dfdaca6.png

Link to post
Share on other sites

Are these two routers actually set up as full routers? That's usually not recommended unless you want two independent networks. Most home networks should only have a single router controlling all of the traffic. 

 

Any other router should be set up as simply a wireless access point (WAP) - most routers allow you to run them in this mode. It disables the routing functionality, but still gives the network access to its WiFi and network switch capabilities.

Link to post
Share on other sites

The TP-Link router shouldn't be acting as a router, only as an Ethernet switch and WiFi access point.

 

Having three routers means you've got three separate networks stuck together, so only PC2 and the devices on the TP-Link's WiFi can access TrueNAS.

 

EDIT: Make sure both the TP-Link and Asus routers are set to not be routers, whatever each one calls that setting.

Edited by Needfuldoer

I sold my soul for ProSupport.

Link to post
Share on other sites

8 minutes ago, YoungBlade said:

Are these two routers actually set up as full routers? That's usually not recommended unless you want two independent networks. Most home networks should only have a single router controlling all of the traffic. 

 

Any other router should be set up as simply a wireless access point (WAP) - most routers allow you to run them in this mode. It disables the routing functionality, but still gives the network access to its WiFi and network switch capabilities.

 

7 minutes ago, Needfuldoer said:

The TP-Link router shouldn't be acting as a router, only as an Ethernet switch and WiFi access point.

 

Having two routers means you've got two separate networks stuck together, so only PC2 and the devices on WiFi can access TrueNAS.

Thanks. Stupid mistake. ASUS is set as a WAP but TP-Link is as Router. I though I've set it up like WAP as well. I had to dig trough settings to find it now

image.png.b858089bc2c3ee58833cf2d9bed910a0.png

 

I'll try to change it and will let you know it that worked.

Link to post
Share on other sites

Just now, WereCat said:

@Needfuldoer @YoungBlade

well, after I did that I can access internet over the TP Link but now I can't acess NAS server connected to it or even the settings of the router.

Doing that would almost certainly change the IP address to both the router and the NAS.

 

Did you look in the ISP router settings for their current IP addresses?

Link to post
Share on other sites

5 minutes ago, WereCat said:

@Needfuldoer @YoungBlade

well, after I did that I can access internet over the TP Link but now I can't acess NAS server connected to it or even the settings of the router.

How did you have all the devices behind the TP-Link addressed? Was it a different subnet from the one your ISP router doles out? Is anything set with a static address, and particularly an address that conflicts with something else on the network?

 

I'd recommend at minimum renewing the DHCP lease on everything now that the ISP router is the only router. You can do that on Windows with an ipconfig /release followed by an ipconfig /renew, but a reboot may be easier.

I sold my soul for ProSupport.

Link to post
Share on other sites

19 minutes ago, Needfuldoer said:

How did you have all the devices behind the TP-Link addressed? Was it a different subnet from the one your ISP router doles out? Is anything set with a static address, and particularly an address that conflicts with something else on the network?

 

I'd recommend at minimum renewing the DHCP lease on everything now that the ISP router is the only router. You can do that on Windows with an ipconfig /release followed by an ipconfig /renew, but a reboot may be easier.

 

23 minutes ago, YoungBlade said:

Doing that would almost certainly change the IP address to both the router and the NAS.

 

Did you look in the ISP router settings for their current IP addresses?

I restarted the router couple of times and my PC and now I'm able to go back into the router settings.

I had static IP added to certain devices including NAS from within the TP-Link router settings

Now I'm trying the list of devices IPs in the Telekom router but there is a lot of devices and none of them seem to be the NAS server.

 

edit:

Had to bust out a monitor and calbe and try to get visual on the NAS. Yes, the IP has changed from 192.168.0.8 to 192.168.1.31 but it was not showing up in the devices list on the Telekom router. If I set the IP into browser I can connect to the NAS thogh.

 

I'm going to set it as a static IP for this device so that it stops changing and will try if I can now access Jellyfin via different router. Will update

Link to post
Share on other sites

@Needfuldoer @YoungBlade

Thanks for help a lot. You both deserve solved status but I can give only one 😕

 

Anyhow, thanks for curing my stupidity 😄 

 

Tested from all 3 routers and now I can connect to the NAS and Jellyfin.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×