Swapped Modem and Router and now security system is jacked

[minimalist]

On 10/17/2017 at 4:54 AM, Levisallanon said:

Did you try this already?

No.  Friday is my day to actually sit down and do this myself with a few hours of free time.  I'll be back to ask for help on Friday 1,000% because I made a little progress but hit some road bumps and had to call it quits since I had work in the morning. 

[bcguru9384]

50 minutes ago, minimalist said:

No.  Friday is my day to actually sit down and do this myself with a few hours of free time.  I'll be back to ask for help on Friday 1,000% because I made a little progress but hit some road bumps and had to call it quits since I had work in the morning. 

go to dvr box

does it have menu button?

press it then browse to network settings

tell to reset

also try unplugging dvr for 30 secs then plugging back in as this should force a dhcp request for available ip address

[minimalist]

Okay guys so here is where I'm at, but before that, I really appreciate all of the willingness to help, so thank you!

 

I plugged a monitor into my dvd and hooked up a mouse and saw I can adjust network settings there.  I've attached a photo of what I can change on there.  

 

Also, I've attached a photo of the google wifi port forwarding screen which has me thoroughly confused.  Any help again, is greatly appreciated!

 

Does anyone know why google would make me create an ip with 198.168.68.(i pick this), but why the .68.?

 

[Lurick]

8 hours ago, minimalist said:

-snip-

You'll need to change the IPv4 address to 192.168.68.92, default gateway to 192.168.68.1

Then you can adjust your port forwarding rules to point to 192.168.68.92

[minimalist]

2 hours ago, Lurick said:

You'll need to change the IPv4 address to 192.168.68.92, default gateway to 192.168.68.1

Then you can adjust your port forwarding rules to point to 192.168.68.92

Does it matter what number is at the end of the 192.168.68.?? For the ipv4 address because I believe I created my own on my Google WiFi?  

 

Also in my OP I mentioned which numbers were given to me for port  forwarding and on the Google WiFi app it's making me enter internal AND external ports which has me a little confused.  Do you know what would go there as well as if it should be tcp and udp?

[Lurick]

3 minutes ago, minimalist said:

Does it matter what number is at the end of the 192.168.68.?? For the ipv4 address because I believe I created my own on my Google WiFi?  

 

Also in my OP I mentioned which numbers were given to me for port  forwarding and on the Google WiFi app it's making me enter internal AND external ports which has me a little confused.  Do you know what would go there as well as if it should be tcp and udp?

So long as you remember what the last octect (set of numbers) is, then it doesn't really matter. You'll just need to make sure you point to that new address for port forwarding.

For the ports themselves you'll specify the internal and external ports as the same. So if you're forwarding 5000, then it will be 5000 for the internal and external port. I know 8080 will be tcp, for the 8000 and 8554, I would do one rule for TCP and another for UDP, so 5 rules in total (1 for 8080, and 2 each for the other two ports)

[minimalist]

9 minutes ago, Lurick said:

So long as you remember what the last octect (set of numbers) is, then it doesn't really matter. You'll just need to make sure you point to that new address for port forwarding.

For the ports themselves you'll specify the internal and external ports as the same. So if you're forwarding 5000, then it will be 5000 for the internal and external port. I know 8080 will be tcp, for the 8000 and 8554, I would do one rule for TCP and another for UDP, so 5 rules in total (1 for 8080, and 2 each for the other two ports)

Look good?  I don't need to hide that ip on there correct when asking questions and what not right?

[Lurick]

Just now, minimalist said:

Look good?  I don't need to hide that ip on there correct when asking questions and what not right?

-snip-

Yah, looks good to me  

Correct, 192.168.x.x is internal and not usable over the public internet. 95% of all home users have 192.168.x.x something for their internal network.

[minimalist]

6 minutes ago, Lurick said:

Yah, looks good to me  

Correct, 192.168.x.x is internal and not usable over the public internet. 95% of all home users have 192.168.x.x something for their internal network.

This is the other screen when trying to set things up on the Google WiFi.  Doea the default gateway on this need to match the ipv4 default gateway on the DVR?  Also, it says it address, what am I putting there and for subnet?

[Lurick]

7 minutes ago, minimalist said:

This is the other screen when trying to set things up on the Google WiFi.  Doea the default gateway on this need to match the ipv4 default gateway on the DVR?  Also, it says it address, what am I putting there and for subnet?

-snip-

That part is for the WAN address, that should be DHCP.

The default gateway on the DVR will point to the address of the Google Wifi router and then the Wifi router will know to send traffic leaving the network out.

[minimalist]

11 minutes ago, Lurick said:

That part is for the WAN address, that should be DHCP.

The default gateway on the DVR will point to the address of the Google Wifi router and then the Wifi router will know to send traffic leaving the network out.

Hmm, it's still not working.  This is what the guy who installed it said to do:

 

 

[mynameisjuan]

34 minutes ago, Lurick said:

95% of all home users have 192.168.x.x something for their internal network.

I have 172.16.x.x because I am a barbarian

 

13 minutes ago, minimalist said:

Hmm, it's still not working.  This is what the guy who installed it said to do:

 

 

I think I know what system you are using. I see it often and the DHCP, quick change it to static trick is what the techs use. In the DVR make the static 192.168.86.100 for more of a guarantee that its not going to interfere with the DHCP pool. .26 is quite low and will give you problems sometimes. But that would also mean you have to redo port forwarding. 

[minimalist]

6 minutes ago, mynameisjuan said:

I have 172.16.x.x because I am a barbarian

 

I think I know what system you are using. I see it often and the DHCP, quick change it to static trick is what the techs use. In the DVR make the static 192.168.86.100 for more of a guarantee that its not going to interfere with the DHCP pool. .26 is quite low and will give you problems sometimes. But that would also mean you have to redo port forwarding. 

Yeah I just did what the email said and it changed the default gateway to have an .86. in it.  But what kind of issues can arise with the 26 in it?  I'm still not getting anything working.

[minimalist]

Should the ipv4 address of my router match the ipv4 address of the DVR?

[Lurick]

2 minutes ago, minimalist said:

Should the ipv4 address of my router match the ipv4 address of the DVR?

The first three sets of numbers should match, the last number needs to be unique.

[minimalist]

1 minute ago, Lurick said:

The first three sets of numbers should match, the last number needs to be unique.

Damn.  So that's correct.  I'm stuck.  Everything seems to align.  The only thing I can think of is the port forwarding now.  

[Lurick]

Just now, minimalist said:

Damn.  So that's correct.  I'm stuck.  Everything seems to align.  The only thing I can think of is the port forwarding now.  

How are you testing the port forwarding?

[mynameisjuan]

7 minutes ago, minimalist said:

Yeah I just did what the email said and it changed the default gateway to have an .86. in it.  But what kind of issues can arise with the 26 in it?  I'm still not getting anything working.

With such a low IP in the pool sometimes devices can get assigned that lease even though its taken. I usually see this when devices just have the static in the device and not the router. Its rare but it happens enough for me to recommend .100 as a minimum. 

 

Ok so I just looked through the thread and noticed some things. First was the 192.168.68.x vs 192.168.86.x which was a typo it looks like. So you have 192.168.86.26 port forwarded. However, earlier in your post you mention 192.168.68.x was the subnet Google gave you.

 

So make sure you DVR has

IP: 192.168.68.26

Sub:255.255.255.0

Gateway:192.168.68.1

 

Port forwarding should also be 192.168.68.26       8080--->8080 etc....

[minimalist]

5 minutes ago, mynameisjuan said:

With such a low IP in the pool sometimes devices can get assigned that lease even though its taken. I usually see this when devices just have the static in the device and not the router. Its rare but it happens enough for me to recommend .100 as a minimum. 

 

Ok so I just looked through the thread and noticed some things. First was the 192.168.68.x vs 192.168.86.x which was a typo it looks like. So you have 192.168.86.26 port forwarded. However, earlier in your post you mention 192.168.68.x was the subnet Google gave you.

 

So make sure you DVR has

IP: 192.168.68.26

Sub:255.255.255.0

Gateway:192.168.68.1

 

Port forwarding should also be 192.168.68.26       8080--->8080 etc....

Good catch!  It's 86.  68 was a typo.  

 

All of that is correct on my end.  Minus the 68.  It's 86 

[minimalist]

6 minutes ago, Lurick said:

How are you testing the port forwarding?

How do you recommend doing that?

[mynameisjuan]

2 minutes ago, minimalist said:

How do you recommend doing that?

Test over cellular on your phone. Google "whats my ip", then copy that address. In your browser go to "xxx.xxx.xxx.xxx:8080".....Replace the Xs with your IP. 

 

You have to do this off network because some firewalls dont allow a loopback, AKA allow to connect with itself. 

 

 

[minimalist]

3 minutes ago, mynameisjuan said:

Test over cellular on your phone. Google "whats my ip", then copy that address. In your browser go to "xxx.xxx.xxx.xxx:8080".....Replace the Xs with your IP. 

 

You have to do this off network because some firewalls dont allow a loopback, AKA allow to connect with itself. 

 

 

When I turned off WiFi on my phone and went to the 8080 port it worked.  

[mynameisjuan]

Just now, minimalist said:

When I turned off WiFi on my phone and went to the 8080 port it worked.  

Sweet! Thats good news.

[minimalist]

1 minute ago, mynameisjuan said:

Sweet! Thats good news.

The other 2 did not.  But I'm not sure you can check with those. 

[mynameisjuan]

Just now, minimalist said:

The other 2 did not.  But I'm not sure you can check with those. 

8080 is typically for remote access such as viewing the cameras. Other ports are for integration with software, updates, etc...You should be all set to go dude.