cancel
Showing results for 
Search instead for 
Did you mean: 

subnet connectivity after ignite gateway implemented

bluebeard
I've Been Here Awhile

Full transparency --- I consider networking a black art 

 

Recently implemented the new Ignite Gateway and noticed IP addresses are now 10.0.0.xx    instead of 192.168.0.xxx  so not understanding why ?

 

I am having problems accessing various devices  including a raspberry Pi / Volumio headless device that previously i could access from any other device on my home subnet via any browser using the 192.168.0.xx IP address ?

 

Also, other computers that I could access via remote apps or via Browser with IP are also no longer accessable

 

Seeking explanation and solution...    @rogershelps  sent me here ???

 

*** Edited Labels ***

1 ACCEPTED SOLUTION

Accepted Solutions

Re: subnet connectivity after ignite gateway implemented

-G-
Resident Expert
Resident Expert

@bluebeard  Remember that after doing this, you will need to use http://192.168.0.1 to connect to your gateway.

 

One you can access your devices again, I would still reprogram them to use DHCP and assign those devices static leases in your gateway.  That will also make it easier for you to revert back to using 10.0.0.x IP addressing if you should ever choose to do so.



View solution in original post

6 REPLIES 6

Re: subnet connectivity after ignite gateway implemented

-G-
Resident Expert
Resident Expert

@bluebeard  The Ignite gateway is made by a different company than your old Hitron gateway, and different manufacturers pick different defaults for the IP address spaces on the local network.

 

If you have devices that have been configured with static 192.168.0.x IP addresses, you can reprogram them with 10.0.0.x IP addresses, or better yet, configure your devices to use DHCP and assign them static leases so that they always get the same IP address when they connect to the network.

 

You should also be able to reprogram the Ignite gateway to use 192.168.0.x IP addresses, and everything should then work as it did before.  To do this, go to http://10.0.0.1 and log into your Ignite gateway, go to "Gateway > Connection > Status", Edit the settings for your Local IP Network, and change the gateway's IP address to 192.168.0.1.  However, if you do this, you may at some point confuse folks that provide you with tech support, who may assume that you are using a standard, default configuration and the standard, default IP addressing scheme.



Re: subnet connectivity after ignite gateway implemented

bluebeard
I've Been Here Awhile

Gonna try this thank you

 

 

.  To do this, go to http://10.0.0.1 and log into your Ignite gateway, go to "Gateway > Connection > Status", Edit the settings for your Local IP Network, and change the gateway's IP address to 192.168.0.1.

Re: subnet connectivity after ignite gateway implemented

-G-
Resident Expert
Resident Expert

@bluebeard  Remember that after doing this, you will need to use http://192.168.0.1 to connect to your gateway.

 

One you can access your devices again, I would still reprogram them to use DHCP and assign those devices static leases in your gateway.  That will also make it easier for you to revert back to using 10.0.0.x IP addressing if you should ever choose to do so.



View solution in original post

Re: subnet connectivity after ignite gateway implemented

bluebeard
I've Been Here Awhile
Will Do --- appreciate your help

Re: subnet connectivity after ignite gateway implemented

@bluebeard the other possibility here is to simply restart all of the connected equipment.  Sometime, when you leave a connected device up and running, and change the modem's IP range or reboot the modem, the device will not change its assigned IP address as it should.  Usually a device reboot will result in the device changing over to its correct IP address. 



Re: subnet connectivity after ignite gateway implemented

bluebeard
I've Been Here Awhile

this solution worked fine for me  =  "  To do this, go to http://10.0.0.1 and log into your Ignite gateway, go to "Gateway > Connection > Status", Edit the settings for your Local IP Network, and change the gateway's IP address to 192.168.0.1 " 

Topic Stats
  • 6 replies
  • 516 views
  • 6 Likes
  • 3 in conversation