Paul Gear wrote: >There's no need to run multiple instances of dhcpd for multiple VLANs. >Just define them as separate subnets, give your DHCP server an interface >in each subnet, and it will automatically allocate clients from the >right range.
Not when each VLAN is on the same subnet it won't. The whole point is that I'm not in a position to partition our address block, so the "firewall" I'm building has to be transparent - hence bridge or proxy ARP. > (Or you could use your switches as DHCP relays and have >them include option 82; dhcpd will still pick the right subnet range >under that circumstance as well.) > >I can show you working examples of the correct dhcpd and switch configs >(for HP Comware and ProCurve switches) if you need them. Don't know what switch I'll be using yet - the budget doesn't run to a new switch, so I'm eyeing up what's on the shelf. Today I was fiddlling with a Linksys switch that at first sight seemed to fit all the requirements - but the b***ard GUI uses so much javascript I get "Out of Memory" errors popping when going into the key VLAN config page (and it's IE only, doesn't seem to work with current versions at all, etc, etc). The CLI is really really basic and only provides the basics to get the switch online so you can use the GUI. I'll have to use an HP switch for testing, but I won't be able to justify keeping it - not enough ports, and all PoE (= expensive). ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
