Jake, Many thanks for the reply.
I'm not using dns or dhcp on the PF box for my production VLANS - that's handled elsewhere - but aren't they needed for the reg and Isolation networks? As I see it I need to create interfaces on the pf box which sit on the Reg and isolation vlans and set the config so dns and dhcp listens on those two interfaces. Otherwise when a machine gets put into say, the registration VLAN, it won't get an IP, won't be directed to the captive portal, etc etc? Cheers, Mark On 17 Feb 2011, at 17:32, "Sallee, Stephen (Jake)" <[email protected]> wrote: > If you're not using PF for the DHCP or DNS on your vlans you can disable it, > as far as I know they are only there to server up DHCP and DNS, if you're not > going to use those features then I wouldn't even worry about setting them up, > you should be able to disable them so they won't complain @ startup. > > Jake Sallee > Godfather Of Bandwidth > Network Engineer > > Fone: 254-295-4658 > Phax: 254-295-4221 > > > > -----Original Message----- > From: Mark Holmes [mailto:[email protected]] > Sent: Thursday, February 17, 2011 10:33 AM > To: '[email protected]' > Subject: [Packetfence-users] Reg and Iso networks- dhcpd not running > > Hi all, > > I'm getting somewhere - the switch is now putting unregistered machines into > the registration VLAN. > > The next stumbling block - dhcpd isn't running. I'm pretty sure it's because > I haven't set up the reg and iso VLANS correctly - I just wondered how other > people generally do this? > > My setup is thus:- > > PacketFence installed in CentOS VM > > Two virtual interfaces, one on main network (VLAN1) and one on Student > network (VLAN3) > > DHCP for those interfaces is handled by our current dhcp server, not > packetfence. Both interfaces have dhcplisterners on them to pick up the DHCP > traffic. > > What do I need to do with the Reg and Iso VLANS? Surely I have an interface > for each of those set up - maybe using 802.1Q so the reg and iso networks can > use the same virtual interface as the main network? > > Cheers, > > Mark > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Packetfence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Packetfence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
