Re: dhcp-users Digest, Vol 133, Issue 6

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: dhcp-users Digest, Vol 133, Issue 6

Cayab, Jefrey E.
Charles,

Thank you for the suggestion which I did and the warning messages went away.
Unfortunately, this server serves large events wherein wifi users could get up to 60,000

Here's the log messages when I applied the changes:
[root@dhcp ~]# tail -f /var/log/messages
Nov 12 00:06:52 dhcp systemd: Stopping DHCPv4 Server Daemon...
Nov 12 00:06:52 dhcp systemd: Stopped DHCPv4 Server Daemon.
Nov 12 00:06:52 dhcp systemd: Starting DHCPv4 Server Daemon...
Nov 12 00:06:52 dhcp dhcpd: Internet Systems Consortium DHCP Server 4.2.5
Nov 12 00:06:52 dhcp dhcpd: Copyright 2004-2013 Internet Systems Consortium.
Nov 12 00:06:52 dhcp dhcpd: All rights reserved.
Nov 12 00:06:52 dhcp dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 12 00:07:08 dhcp dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Nov 12 00:07:08 dhcp dhcpd: Internet Systems Consortium DHCP Server 4.2.5
Nov 12 00:07:08 dhcp dhcpd: Copyright 2004-2013 Internet Systems Consortium.
Nov 12 00:07:08 dhcp dhcpd: All rights reserved.
Nov 12 00:07:08 dhcp dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 12 00:13:10 dhcp dhcpd: Wrote 0 class decls to leases file.
Nov 12 00:13:10 dhcp dhcpd: Wrote 0 deleted host decls to leases file.
Nov 12 00:13:10 dhcp dhcpd: Wrote 0 new dynamic host decls to leases file.
Nov 12 00:13:11 dhcp dhcpd: Wrote 77733 leases to leases file.
Nov 12 00:13:11 dhcp dhcpd: Listening on LPF/eth0/50:6b:8d:03:a8:b9/10.16.5.0/24
Nov 12 00:13:11 dhcp dhcpd: Sending on   LPF/eth0/50:6b:8d:03:a8:b9/10.16.5.0/24
Nov 12 00:13:11 dhcp dhcpd: Sending on   Socket/fallback/fallback-net
Nov 12 00:13:11 dhcp systemd: Started DHCPv4 Server Daemon.

Still 7 minutes :(


On Mon, Nov 11, 2019 at 9:40 PM <[hidden email]> wrote:
Send dhcp-users mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: [EXT] Re: dhcp-users Digest, Vol 133, Issue 4
      (Anderson, Charles R)


----------------------------------------------------------------------

Message: 1
Date: Mon, 11 Nov 2019 13:40:13 +0000
From: "Anderson, Charles R" <[hidden email]>
To: Users of ISC DHCP <[hidden email]>
Subject: Re: [EXT] Re: dhcp-users Digest, Vol 133, Issue 4
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="us-ascii"

On Mon, Nov 11, 2019 at 08:26:27PM +0800, Cayab, Jefrey E. wrote:
> Hi,
>
> # No service will be given on this subnet, but declaring it helps the
> # DHCP server to understand the network topology.
>
> subnet 0.0.0.0 netmask 0.0.0.0 {
> }
>
> It was taken from the comment above it; I thought I could just put anything
> - I'd appreciate if someone can give me what's the proper Subnet/Netmask to
> put there. Does the comment above means that if my dhcp server is in
> 10.16.5.0/24 - this is the subnet and netmask I need to put there?

Yes.  Your subnet statements must reflect reality and yes you do need a subnet for your dhcp server local interface.

The long loading time is because you have a HUGE number of IPs in ranges.  Added up, you have about 656,000 IP addresses the server has to keep track of.  Do you really need each subnet to handle 65534 dynamic IPs?




Move these group and host statements to global scope (not inside any subnet).


------------------------------

Subject: Digest Footer

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 133, Issue 6
******************************************

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: dhcp-users Digest, Vol 133, Issue 6

Andrew Bell
What kind of wifi controller are you using that can handle 65000+ users on a single subnet?!

On Mon, Nov 11, 2019 at 11:23 AM Cayab, Jefrey E. <[hidden email]> wrote:
Charles,

Thank you for the suggestion which I did and the warning messages went away.
Unfortunately, this server serves large events wherein wifi users could get up to 60,000

Here's the log messages when I applied the changes:
[root@dhcp ~]# tail -f /var/log/messages
Nov 12 00:06:52 dhcp systemd: Stopping DHCPv4 Server Daemon...
Nov 12 00:06:52 dhcp systemd: Stopped DHCPv4 Server Daemon.
Nov 12 00:06:52 dhcp systemd: Starting DHCPv4 Server Daemon...
Nov 12 00:06:52 dhcp dhcpd: Internet Systems Consortium DHCP Server 4.2.5
Nov 12 00:06:52 dhcp dhcpd: Copyright 2004-2013 Internet Systems Consortium.
Nov 12 00:06:52 dhcp dhcpd: All rights reserved.
Nov 12 00:06:52 dhcp dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 12 00:07:08 dhcp dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Nov 12 00:07:08 dhcp dhcpd: Internet Systems Consortium DHCP Server 4.2.5
Nov 12 00:07:08 dhcp dhcpd: Copyright 2004-2013 Internet Systems Consortium.
Nov 12 00:07:08 dhcp dhcpd: All rights reserved.
Nov 12 00:07:08 dhcp dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 12 00:13:10 dhcp dhcpd: Wrote 0 class decls to leases file.
Nov 12 00:13:10 dhcp dhcpd: Wrote 0 deleted host decls to leases file.
Nov 12 00:13:10 dhcp dhcpd: Wrote 0 new dynamic host decls to leases file.
Nov 12 00:13:11 dhcp dhcpd: Wrote 77733 leases to leases file.
Nov 12 00:13:11 dhcp dhcpd: Listening on LPF/eth0/50:6b:8d:03:a8:b9/10.16.5.0/24
Nov 12 00:13:11 dhcp dhcpd: Sending on   LPF/eth0/50:6b:8d:03:a8:b9/10.16.5.0/24
Nov 12 00:13:11 dhcp dhcpd: Sending on   Socket/fallback/fallback-net
Nov 12 00:13:11 dhcp systemd: Started DHCPv4 Server Daemon.

Still 7 minutes :(


On Mon, Nov 11, 2019 at 9:40 PM <[hidden email]> wrote:
Send dhcp-users mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: [EXT] Re: dhcp-users Digest, Vol 133, Issue 4
      (Anderson, Charles R)


----------------------------------------------------------------------

Message: 1
Date: Mon, 11 Nov 2019 13:40:13 +0000
From: "Anderson, Charles R" <[hidden email]>
To: Users of ISC DHCP <[hidden email]>
Subject: Re: [EXT] Re: dhcp-users Digest, Vol 133, Issue 4
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="us-ascii"

On Mon, Nov 11, 2019 at 08:26:27PM +0800, Cayab, Jefrey E. wrote:
> Hi,
>
> # No service will be given on this subnet, but declaring it helps the
> # DHCP server to understand the network topology.
>
> subnet 0.0.0.0 netmask 0.0.0.0 {
> }
>
> It was taken from the comment above it; I thought I could just put anything
> - I'd appreciate if someone can give me what's the proper Subnet/Netmask to
> put there. Does the comment above means that if my dhcp server is in
> 10.16.5.0/24 - this is the subnet and netmask I need to put there?

Yes.  Your subnet statements must reflect reality and yes you do need a subnet for your dhcp server local interface.

The long loading time is because you have a HUGE number of IPs in ranges.  Added up, you have about 656,000 IP addresses the server has to keep track of.  Do you really need each subnet to handle 65534 dynamic IPs?




Move these group and host statements to global scope (not inside any subnet).


------------------------------

Subject: Digest Footer

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 133, Issue 6
******************************************
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: [EXT] Re: dhcp-users Digest, Vol 133, Issue 6

Anderson, Charles R
> On Mon, Nov 11, 2019 at 11:23 AM Cayab, Jefrey E. <[hidden email]> wrote:
> > Thank you for the suggestion which I did and the warning messages went
> > away.
> > Unfortunately, this server serves large events wherein wifi users could
> > get up to 60,000

My calculation was off by an order of magnitude.  As Simon said, you have 6 MILLION addresses in all the pools/ranges added up.  That will take a long time to load the config.

On Mon, Nov 11, 2019 at 11:29:47AM -0500, Andrew Bell wrote:
> What kind of wifi controller are you using that can handle 65000+ users on
> a single subnet?!

Many kinds.  Wi-Fi is generally handled as one flat subnet on an entire campus/site with broadcast/multicast suppression so that you don't have roaming problems which would happen if you need to roam to a new subnet.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: [EXT] Re: dhcp-users Digest, Vol 133, Issue 6

Andrew Bell

On Mon, Nov 11, 2019 at 11:29:47AM -0500, Andrew Bell wrote:
> What kind of wifi controller are you using that can handle 65000+ users on
> a single subnet?!

Many kinds.  Wi-Fi is generally handled as one flat subnet on an entire campus/site with broadcast/multicast suppression so that you don't have roaming problems which would happen if you need to roam to a new subnet.


Actually, I've been using pooled /20 subnets for years, which was considered best practice for campus networks at the time it was implemented. Roaming to a new subnet never happens.

This made me go look up the current best practices though, and it appears that the pooled model is being deprecated in favour of bigger subnets. Good to know.



_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users