Hello Stuart,

If you want to use VLAN 55 as your registration VLAN, make sure the DHCP is enabled on the interface 55 of PacketFence, and this interface is set a registration interface. If GeneralStaff is your 'production' role, then try to return VLAN 1 for this role instead.


Thanks


On 02/01/2017 09:59 AM, Stuart McWatt wrote:

Hi Antoine,


Thank you for your response.


VLAN 55 is for registration and VLAN 56 is for isolation. VLAN1 is our production VLAN.


We have got GeneralStaff in VLAN55 for registration. Should Generalstaff be in VLAN 1 (our production VLAN)?


Thanks

Stuart





------------------------------------------------------------------------
*From:* Antoine Amacher <[email protected]>
*Sent:* 01 February 2017 14:13
*To:* [email protected]
*Subject:* Re: [PacketFence-users] Packetfence DHCP/roles

Hello Stuart,

PacketFence is not a DHCP server for other VLAN than registration / isolation, if I followed properly VLAN 55 is your production VLAN for 'GeneralStaff', this mean you must have your own DHCP server in the VLAN 55.

Thanks


On 02/01/2017 04:42 AM, Stuart McWatt wrote:

Hi,

We are trying to set up a new Packetfence server and are having problems somewhere between the ‘roles’ and client Windows machine picking up a relevant IP address from the pf server.

AD is successfully added as a user source and there are basic rules added, the rule conditions are for AD group membership so if an AD user account is in a group which matches the rule then its assigned a role.

The Windows client becomes ‘registered’ and is put into a relevant role ‘GeneralStaff’ for this situation. In PacketFence within Network-Switches area, our Cisco switch has the ‘Role by VLAN ID’ = ‘General Staff’ and is configured for VLAN 55 (Registration).

So when I connect my laptop, it is registered and is put into the ‘GeneralStaff’ role but I do not get an IP address associated with VLAN 55 (infact I get a 169 IP address).

I can ping all the VLAN interfaces etc so network connectivity is fine and in Network – Interfaces&Switches the VLANs have been configured eg vlan55 10.55.55.10 255.255.255.0 Registration. We are slightly confused why the packetfence does not give my laptop a VLAN 55 address?

Do we need to create separate DHCP scopes for each VLAN?

Thanks for any help you can provide in advance it would be very much appreciated.



  ­­


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org!http://sdm.link/slashdot
Slashdot: News for nerds, stuff that matters <http://sdm.link/slashdot>
sdm.link
Slashdot: News for nerds, stuff that matters. Timely news source for technology related news with a heavy slant towards Linux and Open Source issues.




_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

--
Antoine Amacher
[email protected] ::www.inverse.ca +1.514.447.4918 x130 :: +1 (866) 353-6153 x130
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence 
(www.packetfence.org)


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot


_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

--
Antoine Amacher
[email protected]  ::  www.inverse.ca
+1.514.447.4918 x130  :: +1 (866) 353-6153 x130
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence 
(www.packetfence.org)

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to