[DHCP] RE: Determining request

[Randall C Grimshaw]

Ashley:

>From the Procurve doc on hp.com this is not your solution either all by itself. You lack a routing functionality and that would mean still more manuals to figure out what you could use instead (firewall, internet router).

I also checked Linksys.com and the WAP is a soho router where the users are behind a NAT - Which means that the APs have their own DHCP. I don't think what you are describing is even relevant.

Can we start over.

Randy

------------------------
support for up to 8 IEEE 802.1Q-compliant VLANs so you can divide the attached end nodes into logical groupings that fit your business needs
Effect of VLANsIf you configure multiple virtual LANs (VLANs) on the switch, each VLAN behaves as a "logical switch" containing the switch ports that you assign to it. Each logical switch behaves as an isolated broadcast domain, just as if it were a separate physical switch. The forward, filter, and flood behavior described for the physical switch above, operates the same for each of the logical switches defined by the VLANs: packets are forwarded or flooded only to the ports that are within a given VLAN. Just as for separate physical switches, there is no communication between ports that are in separate VLANs unless the VLANs are connected by an external router. For more information on configuring VLANs and their behavior, see the HPProCurve Switch 8000M and 1600M Management and Configuration Guide that came with your switch.
-------------------------

On Tue, Jan 5, 2010 at 13:08, Ashley M. Kirchner <ashley at pcraft.com> wrote:
> Randall C Grimshaw wrote:
>>
>> With this information I am going to join with Matt in suggesting the use
>> of vlans to define a separate subnet.
>>
>
>   Lovely, that would mean me having to go through the documentation for the
> switch (HP ProCurve 4000m) and figuring out the VLANs - something that was
> never done in the first place.  When the switch was installed, they simply
> powered it up and plugged everyone in and called it done.
>
>   Ok, I'll go that route and see if I can figure it out, but ...  Once
> that's done, I still don't know how to configure DHCPd to tell what's what
> ...?
>
>   A
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
_______________________________________________
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users