IP Addressesess

From: ANT_THOMAS11 Jul 2016 11:31
To: ALL1 of 11
My current IP range at home is 192.168.1.xxx

If I set some devices with a manual IP of 192.168.2.xxx should they still be able to communicate with all the 1.xxx devices?
From: ANT_THOMAS11 Jul 2016 11:45
To: ALL2 of 11
Or do I need to change my subnet to 255.255.254.0?
From: ANT_THOMAS11 Jul 2016 11:58
To: ALL3 of 11
Or does that open up 0.xxx?

With 255.255.252.0 giving access to - 192.168.0.0 - 192.168.3.255?

I think my dd-wrt router should be able to do that.
From: ANT_THOMAS11 Jul 2016 12:02
To: ALL4 of 11
But I can access the Virgin router in modem mode at 192.168.100.1 without any subnet changes.
From: Serg (NUKKLEAR)11 Jul 2016 12:35
To: ANT_THOMAS 5 of 11
You can access your VM SuperHub at 192.168.100.1 because your default route is out through it (well, kind of, but effectively that's why).

If you're currently using 192.168.1.0/24 (255.255.255.0) and you want to also use 192.168.2.x, then you would indeed need to use a subnet mask of 255.255.252.0 which would give you a usable range of 192.168.0.0 - 192.168.3.0 (noted as 192.168.0.0/22).

Because of how subnetting works, in this case you can use:
192.168.0.0 - 192.168.1.255 with a netmask of 255.255.254.0
and
192.168.2.0 - 192.168.3.255 with a netmask of 255.255.254.0
(and you'll need to route between those two on your local router, and therefore have two IPs on its internal interface, one from each subnet)
or
192.168.0.0 - 192.168.3.255 with a netmask of 255.255.252.0

Does that make sense..?
From: ANT_THOMAS11 Jul 2016 12:37
To: Serg (NUKKLEAR) 6 of 11
I think so, if I change the subnet to 255.255.252.0 on the router I'll get 0-3?

That's fine by me, didn't need to specifically just be 2.xxx
From: Serg (NUKKLEAR)11 Jul 2016 12:43
To: ANT_THOMAS 7 of 11
Correct, that'll give you 192.168.0.0 - 192.168.3.255 . Just make sure you then change the netmask on all the existing devices as well, otherwise they won't see the new ones properly, and vice versa. Windows has its caring tendency to automatically fill it in as 255.255.255.0, which is nice, but potentially annoying.

You won't need to change your router's IP (I'm guessing 192.168.1.1 or .254?), that'll keep working just fine with the new subnet.
From: ANT_THOMAS11 Jul 2016 12:47
To: Serg (NUKKLEAR) 8 of 11
Thanks. Yeah, I'll just power cycle everything that needs it and tweak a few static IPs. I /think/ most are dished out as static by the router itself defined my MACs, but I'm sure I've got a few that a proper manual.
From: graphitone11 Jul 2016 14:53
To: ANT_THOMAS 9 of 11
Do you have that many RPis now, that you need more than a /24 network?!
From: ANT_THOMAS11 Jul 2016 14:58
To: graphitone 10 of 11
Yes/No/Maybe :$

It's mainly because I'm going to making use of a number of ESP8266 devices and it would be nice to have them organised together in a separate range.

I'll hopefully be removing one RPi from my setup and replacing it with an ESP8266 at some point once I paint my desk and get my "office" back in working order.
From: CHYRON (DSMITHHFX)11 Jul 2016 15:10
To: ANT_THOMAS 11 of 11
Dunno if this helps, but my wifi router does 192.168.2.x, and my tablet can see local webserver @ 192.168.1.x (wifi & server both to same wired router)