Now i have to log in?

default_user8 · 2018-01-19, 06:03 PM

I had to get a new router and now that i am on the new router when i try to log into the web app it ask for me to log in. Anyone have any idea?

***sub*** · 2018-01-19, 06:51 PM

What IP address range are you using on your router?

It'll only make you log in if your client is one an IP address that is outside the standard ranges used for local area networks.

default_user8 · 2018-01-19, 09:25 PM

I did make a custom ip range, 20.33.XX.XX, is there a way to make this work or do i need to switch back to 192.168.1.XX?
And all devices are in the same range, and subnet.

mvallevand · 2018-01-19, 09:35 PM

It needs to be a private IP so technically it doesn't have to be class c so if you really need class a use 10. Instead of 20

Using a public IP doesn't make sense anyway.

Martin

default_user8 · 2018-01-19, 09:40 PM

Thanks, i don't know enough about ip adress ranges, i need to do more reasearch. I'm pretty tight with the IT guy at work and he mentioned i shouldn't use the stock ip adress so i used a random ip generator to make a custom range for my new router. Changing a 2 to a 1 shouldn't be a big deal.

***sub*** · 2018-01-20, 01:50 AM

default_user8 Wrote:I did make a custom ip range, 20.33.XX.XX

Yeah...don't do that. Use one of the standard ranges.

HarryH3 · 2018-01-20, 11:18 AM

The devices in your house now have the same IP range as someone elses public IP addresses. Not Good. Your IT friend didn't go far enough in his recommendation. You still need to use a private IP range behind a NAT router. You can choose from 192.168.X.X, 10.X.X.X or 172.16.0.0-172.31.255.255. For home use, it is often easiest to just change one octet in the 192.168.x.x range. Most SOHO routers are set to 192.168.1.x by default. This is fine for many users. However, keeping this scheme can cause problems if you want to use a VPN to access your network while away from home. If you're connected to another network that also uses the 192.168.1.x scheme, you run into routing problems when you try to reach your home network because when you try to connect to (for example) 192.168.1.12, the local router won't send your request outside of its local LAN because it is programmed to NOT route any packets addressed to 192.168.1.x segment out to the WAN. It will be looking for address only on its LAN. It's similar to why 2 houses can't have the same street address. Wink

So, I suggest that you keep it simple and just set your IP range to something not "stock", but still in a private address space, like 192.168.22.x (Change the 22 to whatever you like). Smile

If you're interested in details, there's more here: https://en.wikipedia.org/wiki/Private_network

default_user8 · 2018-01-20, 05:20 PM

Thanks for the help, i did do some reasearch and see where i had made my error now. I have everything back up and running smoothly. In a way this all happened at a good time, i have been extrememly busy latley with not time for TV. I didn't realize my epg grab from zap2it had stopped working, almost everything i watch is recorded i never have time to catch shows when they originally air. Thanks again to everyone for the help, nextpvr is the best option out there IMO.

johnsonx42 · 2018-01-21, 11:32 PM

as a simple convention for my customers I often set the third octet of the private IP address to the first two or three digits of the customer's street address. so a customer at 2746 Main Street gets 192.168.27.0 for their network address. Aside from giving them a likely non-conflicting IP range, it seems to help me load each customer's IP list into my brain when I'm working on their system and if I find a random IP written in a note or file, I automatically know which customer it's for.