Boris Epstein <[email protected]<mailto:[email protected]>> wrote:
> I think my point still stands - you do need to mandate at least
> one production VLAN. I guess I should have worded my point better
> by saying "one or more".
Are you referring to interfaces in PacketFence being mandatory? If so,
PF does not need to interact with your production VLAN(s) or their
clients if you are not running inline mode. Hence, no PF interface
is required on the production VLAN(s). PF tells the switch to change
VLAN, and at that point the client is on their own.
If you want PF to track IP address history, you need to either make
sure that PF has an interface on each production VLAN to sniff the
DHCP packets or else make sure that your switch(es) forward DHCP
packets to PF using an internal helper (ala Cisco).
Hope this helps...
-Arthur
-------------------------------------------------------------------------
Arthur Emerson III Email:
[email protected]<mailto:[email protected]>
Network Administrator InterNIC: AE81
Mount Saint Mary College MaBell: (845) 561-0800 Ext. 3109
330 Powell Ave. Fax: (845) 562-6762
Newburgh, NY 12550 SneakerNet: Aquinas Hall Room 11
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
