I'm currently using .5 on my home network, how does that make you feel ?

😉

In reply to a post by andynormancx:

I'm currently using .5 on my home network, how does that make you feel ?

😉

Bit much, I'll stick to /22 in my core network.

I don't really need a /24 to be honest, I am currently working on moving the IP ranges in the DHCP server and those that are reserved. I'm still researching how to best setup my VPN server as the IP ranges overlap (unintentionally).

All my static / reserved is between 10.0.0.2-10.0.0.60 the first 30 is for switches (even if some switches are no longer in use they still are static as some required java (these switches are for emergencies only due to security)) / network AP's and printers 2 are for NAS as they were assigned an IP a long time ago and it would mean remapping drives on some machines that are offsite and use a VPN for local network storage access. If anyone has any advice on the best way to set up a VPN that only shares mapped drives and doesn't transfer all network internet traffic i'm all ears. I use a Synology DS920+ for L2TP VPN and Storage at the moment.

In reply to a post by RR_The_IT_Guy:

I'll stick to /22 in my core network.

I don't really need a /24 to be honest

Ryan

When you say core network I thought you lived with your parents and had not long left colleague and was looking for a job at Openreach.

Have things changed?

Edited by deleted (Sun 13-Mar-22 22:37:12)

In reply to a post by RR_The_IT_Guy:

Bit much, I'll stick to /22 in my core network.

I don't really need a /24 to be honest
...

You may mean the other way around
/22 is 1024 addresses and a /24 is 256

In reply to a post by Woolwich:

Playing with a new router which does DHCP. In default setup its DHCP pool is from 192.168.1.38 to 192.168.1.243.

Why?!

Is there an RFC or some other rules suggesting where a pool starts and stops? Why not start at 1 and go to 254?

If its to 'protect' fixed addresses for routers or other devices, how come the suggested default client IP pool for VPN users runs from 240 to 249? Or is this just a misconfiguration on my part? Should I drop the DHCP pool back down to 239? Or increase it to 249?

That looks as though it was a choice made by the previous owner or software designer (if the router has been reset)

Anyway you can use any of the private IP ranges https://www.arin.net/reference/research/statistics/a...

In reply to a post by jabuzzard:

In reply to a post by Pheasant:

Btw typically the gateway is .1 so the pool would start from .2 on most setups.

Heretic. All right thinking people and in my experience the vast majority of networks have the gateway set as the last IP address in the network range. So typically .254 unless you are subnetting on none byte boundaries

I have my gateway set to 1 too and the third octet set to my house number for the sheer hell of it

(playfully thumbs nose at jabuzzard)

In reply to a post by dect:

In reply to a post by RR_The_IT_Guy:

I'll stick to /22 in my core network.

I don't really need a /24 to be honest

Ryan

When you say core network I thought you lived with your parents and had not long left colleague and was looking for a job at Openreach.

Have things changed?

First part hasn't changed, but I didn't mention that a few family members have companies who I do some IT for, I won't go into detail because it will turn into a 5 page list of things, put it this way we have a ticket system with set SLA's and they are kept to, (80% of the time).

I think you inferred the last bit, I haven't looked at jobs at openreach, they aren't quite what i'm looking for long term. I have a job at a Cyber Security Contractor, as an IT service desk and delivery team technician. I'm also currently looking at degree apprenticeships across the UK for even longer prospects into various IT roles.

I just referred to core network as various bits are shared and end up linked, for various reasons, one being that its easier to have a internal shared site between family and friends hosted with failover across multiple NAS drives one in Cambridgeshire, Nord Pas Calais (France), Barnet (London), and one in Northampton. It just means we can share storage and information easily without needing to all buy onedrive or online storage subscriptions. (I know I have the biggest amount of storage across my NAS's, 12TB in the raid i use on one and 12 on the other.

Account's are mapped and accessed through explorer like this

Network drives across the whole configuration are set up something like this, please note I have some extra drives mapped as I manage it, the users only have 3 or 4 depending on the access they require

Obviously everything is encrypted as thats standard practice.

In reply to a post by Pheasant:

In reply to a post by RR_The_IT_Guy:

Bit much, I'll stick to /22 in my core network.

I don't really need a /24 to be honest
...

You may mean the other way around
/22 is 1024 addresses and a /24 is 256

Ops, you got me, been a busy day, been prepping powerpoints on DNS and DNS resolution for a job interview at an MSP on Friday.

In reply to a post by RR_The_IT_Guy:

I haven't looked at jobs at openreach

Sorry I meant BT but typed Openreach

In reply to a post by RR_The_IT_Guy:

In reply to a post by dsergeant:

has anybody actually seen what the actual price increases are?Can't see anything on the BT website

They do have a page on it as I saw it when I was applying to a job there

Edited by deleted (Mon 14-Mar-22 09:23:03)

In reply to a post by nemeth782:

Personally, I use 192.168.2.0/23 as a subnet on my home network, I.e. 192.168.2.0-192.168.3.255.

I then have my router on 192.168.2.1, all my static things on 2.x, and 3.x is my DHCP pool.

VPN clients are on their own subnet.

OK, I'm using /24 because I don't know enough about networking but (after reading a bit) also because I have four VPN connections between sites and each of those needs to ne on lits own subnet. As far as I understand. So if I ran a 192.168.1.0/23 LAN here I couldn't have the the office which uses 192.168.2.0 VPN in.

So VPN on their own subnet but I want to have access to file shares on the office LANs. If I come in on a different subnet I won't be able to access them.

Jings, this seemed simple and the original answer was. Now we're down on of them rabbit holes...