Hi,
I got a lot of modems in bridge mode. So customers behind those modems get an ip from our dhcp servers.
Sometimes people connect their own modem and in that case the customers behind those modems should get an ip-address etc from another pool, so we can send them to a webpage explaining them to connect the modem we supplied and not a custom modem.
How can I set up our dhcp server like that? Can someone show me an example dhcpd.conf for isc-dhcpd?
Thanks a lot.
We dont bother with a web page redirection
We just have a static reservation for every provisioned modem
And then have a dynamic pool for non-provisioned modems. For this pool associate a CM config file which has NetworkAccess 0. This way we can see these modems, but the user will not have internet access. The CM lights flash in a distinctive pattern which makes troubleshooting pretty easy for our helpdesk should the user ring up.
When you have static reservation from CM, and another pool (dynamic) to non-provisioned modem, you must have multiple DHCP server, one per CM, another per CPE, MTA
If you must have only one DHCP server to all clients (CPE,MTA,CM) try filter only cable modem to pool non-provisioned modem:
Use vsi:
option space vsi;
option vsi.version code 6 = string;
option vsi.model code 9 = string;
option vsi.model_other code 201 = string;
option vsi.version_other code 202 = string;
option vsi-pkt code 43 = encapsulate vsi;
and include file with CM definitions like that:
class "tcm390" {
match if option vsi.model_other = "TCM390";
filename "tcm300.cfg";
next-server 192.168.12.1;
}
Please define in dhcp.conf pool
and option allow members like:
allow members of "tcm390" in this space.
Look this link:
http://www.cmtsinfo.net/index.php?howto=cm_up_dhcp
Hi there
What we did is set up a file called modems.conf that puts every known modem into the modems class (which are the only classes of client that get TFTP and provisioning information). The modems get private RFC1918 IP addresses that don't and can't route outside our headend/ network (e.g. 172.16.1.x). The modems are defined by MAC address, and any unknown device that boots up and asks for an IP gets a routable address and no provisioning/ tftp information. So if someone wants to bring their own modem, they have to supply us with their modem's HFC MAC address, so it can be added tot he system. THis is also how we disable modems for violation of TOS or non-pay - we simply kick them out of the modem class in DHCP and reset their modem at the uBR, so their modem gets an IP but no config file and the CPE can no longer get online. We don't statically address each modem's IP, as we want the pools to be used efficiently by the DHCP server.
If you PM me I'd be glad to share our configs with you.
Rubin
I'd love to see those configs! (I'd have PM'd you but oddly I can't find where one does that here... perhaps my account is too new to do so? Or possibly I am just stoopid today...)
Another solution could be to provide unprovisioned modems with an IP address from a reserved pool. IPs from that pool could be routed (tunneled by cmts) to a special webpage.