Hi... Mark
one suggestion... have you check the configuration on the VLANs that the Ip
helper-address its correct?
Regards
2011/2/21 Mark Holmes <[email protected]>
> Yes, my production DHCP server will handle IP addresses for the production
> network.
>
> There is no overlapping of scopes at all.
>
> Reg and Iso vlans are handled by dhcpd on pf box
>
> Production networks are handled by dhcp on a separate server. I have
> interfaces with a dhcplistener running on them so pf can 'see' the dhcp
> traffic on the production nets as per the manual.
>
> As I said, dhcpd is configured correctly as if I put a port into the reg
> vlan manually via the switch CLI it picks up an IP - it's just when
> Packetfence puts the port into reg vlan, no dhcp request is ever receieved
> on the pf box and so the client doesn't get an IP.
>
> Thanks,
>
> Mark
>
>
>
>
>
>
> -----Original Message-----
> From: Manueco, Antonio [mailto:[email protected]]
> Sent: 21 February 2011 15:29
> To: [email protected]
> Subject: Re: [Packetfence-users] Fwd: VLAN assignment and DHCP
>
> Who's leasing the IP's for your Production (Normal) VLAN? This should be a
> DHCP server in your production VLAN that gives you the correct IP and DNS
> information once you've registered with PF. Make sure the scopes don't
> overlap with the PF DHCP ranges.
>
>
>
>
> -----Original Message-----
> From: Mark Holmes [mailto:[email protected]]
> Sent: Monday, February 21, 2011 6:28 AM
> To: [email protected]
> Subject: Re: [Packetfence-users] Fwd: VLAN assignment and DHCP
>
> I do, yes. I'm using pf as the dhcp for the reg and iso VLANS.
>
> I know dhcpd is working correctly, as if I manually put a port into the
> registration VLAN using the switch CLI it picks up an IP in the registration
> range.
>
> Thanks,
>
> Mark
>
>
>
>
> -----Original Message-----
> From: Manueco, Antonio [mailto:[email protected]]
> Sent: 21 February 2011 03:05
> To: [email protected]
> Subject: Re: [Packetfence-users] Fwd: VLAN assignment and DHCP
>
> Do you have a DHCP server listening on that VLAN?
>
> -Antonio Manueco
>
> Sent via Mobile.
>
> On Feb 20, 2011, at 7:04 PM, Mark Holmes <[email protected]>
> wrote:
>
> >
> > Anyone have any thoughts on this?
> >
> > Thanks,
> >
> > Mark
> >
> > From: Mark Holmes <[email protected]<mailto:
> [email protected]>>
> > Date: 18 February 2011 09:37:11 GMT
> > To: "'[email protected]<mailto:
> [email protected]>'" <
> [email protected]<mailto:
> [email protected]>>
> > Subject: [Packetfence-users] VLAN assignment and DHCP
> > Reply-To: "[email protected]<mailto:
> [email protected]>" <
> [email protected]<mailto:
> [email protected]>>
> >
> > Hi all,
> >
> > I have got Packetfence set up, it's putting ports into the various VLANS
> (registration, main network etc) correctly but then once the port has
> changed, nothing happens and the DHCP request times out.
> >
> > I'm using port security as that is supported with this switch (a 3Com
> 4200G)
> >
> >
> > For example
> > -----------
> > Connect new machine
> >
> > Port put into VLAN 50 by PF (registration VLAN) - I confirm this on the
> switch
> >
> > But no answer from DHCP on registration network (dhcpd running on PF)
> >
> > Same if I register the machine (via the admin console) and put plug it in
> - the port goes into the correct VLAN, but DHCP doesn't get an answer.
> >
> > Running tcpdump on the registration interface shows no dhcp request is
> received on the registration interface of the PF box.
> >
> > If I manually put another port into the registration VLAN and plug into
> that, it gets an IP from the reg subnet and when I then open a browser the
> registration page appears - so the dhcpd is configured correctly etc.
> >
> > Any ideas, anyone?
> >
> > 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]<mailto:
> [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
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
