Pfsense
-
@scottalanmiller said in Pfsense:
I actually made a video on LAN sizes just the other day. I'm waiting on it to be edited.
I'm finally going through and watching all your videos.
Remember to like and subscribe
-
@scottalanmiller said in Pfsense:
@scottalanmiller said in Pfsense:
I actually made a video on LAN sizes just the other day. I'm waiting on it to be edited.
I'm finally going through and watching all your videos.
Remember to like and subscribe
Yeah I subscribed. Be prepared for me to come to you with questions and things..
-
i still don;t understand subnetting the way I should. At least I know it though.
-
@scottalanmiller said in Pfsense:
@scottalanmiller said in Pfsense:
@scottalanmiller said in Pfsense:
a /23 (the smallest recommended these days)
Really? I never heard of that.. Where is this recommended? (truly curious)
Pretty much anywhere it’s discussed
It’s been the standard in the enterprise since the rise of switching.
Right.. well I feel like you're from a different world or something as you're always saying things that seem very different than what's commonly heard of. That being said, we actually have a /23 network where I work but I've had numerous people comment on it as being a "weird setup". I just assumed they had little knowledge of networking and are used to the very common /24 setups on a lot of home routers and things.
I'd say that /23 and /22 are the norms for good networks. Smaller than that is super common - artefacts of the fact that almost all SMBs are totally out of touch and work off of myths and rumours instead of facts and research.
Remember, in IT (and most things in life) if most people do it, it's probably not a good idea and something to avoid. Best practices and good rules of thumb are never things followed by the majority.
The research bit is the problem I have here. It's not like there is a definitive guide (book) to good networking, at least not that I know of.
When I reading my MSCE books in the mid to late 90's /24 was the common thing. Now with understanding, etc I see the use of /22 and /23 and the advantages - but again, are their general networking books that everyone should be reading that we simply aren't?
-
@dashrender said in Pfsense:
When I reading my MSCE books in the mid to late 90's /24 was the common thing. Now with understanding, etc I see the use of /22 and /23 and the advantages - but again, are their general networking books that everyone should be reading that we simply aren't?
Even the MS stuff in the 1990s told WHY /24 was used, so in reality they explained why it is too small today. Yes, /24 was common then, just like RAID 5, but since MS was clear as to why those were chosen and what factors were used, I'd say that they were pretty clear on why that is no longer true by the early 2000s.
-
A /24 is a silly thing on almost any SMB network. With the number of devices per user on a modern network you will smack that limit quick.
-
@jaredbusch said in Pfsense:
A /24 is a silly thing on almost any SMB network. With the number of devices per user on a modern network you will smack that limit quick.
Even at home it's not hard to hit it quickly these days. I mean, not going to happen often. But between routers, switches, access points, mobile phones, VoIP devices, IoT devices, sensors, laptops, desktops, gaming machines, visitors, etc. and if you have a home lab with tons of VMs or containers, it adds up fast.
-
-
@scottalanmiller said in Pfsense:
@jaredbusch said in Pfsense:
A /24 is a silly thing on almost any SMB network. With the number of devices per user on a modern network you will smack that limit quick.
Even at home it's not hard to hit it quickly these days. I mean, not going to happen often. But between routers, switches, access points, mobile phones, VoIP devices, IoT devices, sensors, laptops, desktops, gaming machines, visitors, etc. and if you have a home lab with tons of VMs or containers, it adds up fast.
Yeah, its possible if every device is static and the lease time is unlimited.
-
@black3dynamite said in Pfsense:
@scottalanmiller said in Pfsense:
@jaredbusch said in Pfsense:
A /24 is a silly thing on almost any SMB network. With the number of devices per user on a modern network you will smack that limit quick.
Even at home it's not hard to hit it quickly these days. I mean, not going to happen often. But between routers, switches, access points, mobile phones, VoIP devices, IoT devices, sensors, laptops, desktops, gaming machines, visitors, etc. and if you have a home lab with tons of VMs or containers, it adds up fast.
Yeah, its possible if every device is static and the lease time is unlimited.
Or they are just all on within a reasonable amount of time.
-
Plus you can have NAS, SAN and other storage things like that at home. Monitory, logging, etc.
-
What's the default lease duration in UBNT routers? I know Windows DHCP is limited to 8 days.
-
@black3dynamite said in Pfsense:
What's the default lease duration in UBNT routers? I know Windows DHCP is limited to 8 days.
24 hours. I rarely leave it default though. I like 8 hours. If shit is going to break, I want to know about it sooner rather than later.
-
Here is my ELR config at home.
jbusch@jared:~$ show configuration commands service | grep dhcp-server set service dhcp-server disabled false set service dhcp-server hostfile-update enable set service dhcp-server shared-network-name LAN authoritative disable set service dhcp-server shared-network-name LAN description 'LAN eth1' set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 bootfile-name settings/snom.htm set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 default-router 10.254.103.1 set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 dns-server 10.254.103.1 set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 lease 28800 set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 ntp-server 10.254.103.1 set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 start 10.254.103.31 stop 10.254.103.254 set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 time-server 10.254.103.1 set service dhcp-server shared-network-name LAN subnet 10.254.103.0/24 unifi-controller 207.244.223.13 set service dhcp-server use-dnsmasq disable
