Hello,
One thing we would like to achieve is the most possible separation between
packetfence and the "users".
The regular setup of packetfence suggets that we set up an interface eth0
being the management interface, with isolation & registration VLAN built on
top of eth0. Eth0 being connected to the switch with a trunk connection.
Does the admin portal must necessarily have the same IP address as the
management interface ?
Would it be possible to set up the trunk connection on eth0,that would
become the management interface,
and let's say, have the admin / configuration portal setup on another IP
address (i.e. interface) in another part of the network ?
So users shouldn't be able to access the admin page depending on their VLAN
/ setup / rights.
Like seeing the admin portal as a "service" in the network, and as such,
should not be coupled with an "access" switch directly.
I've checked the httpd.admin conf file but the "$vhost" variable is
generated dynamically , I think from the packetfence conf, so it doesn't
look possible but I don't know that much about the internals of PF.
Thank you, I hope I've been clear enough .. !
Nicolas GAILLY
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
