SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264
|Anonymous | Login||2019-02-23 16:37 UTC|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000937||Endian Firewall||Other Services||public||2008-06-12 10:12||2010-09-21 18:33|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||future||Fixed in Version|
|Summary||0000937: dhcp: no possibility to use secondary subnets|
|Description||there is no possibility to use secondary subnets of a zone in dhcp configuration.|
If the other subnets would be configured without ip range, one may assign fixed leases of secondary subnets to a mac address.
|Tags||No tags attached.|
"If the other subnets would be configured without ip range, one may assign fixed leases of secondary subnets to a mac address." -> this is not possible
a possible solution would be, give the possibility to create an instance per interface and filter dhcp traffic between interfaces of the same bridge
|at least there should be the possibility to select the subnet which should be used in a zone. currently only the primary subnet will be used|
"All versions of the server have the ability to support so-called VLAN configurations, where more than one IP subnet is run on the same network wire, possibly with some traffic isolation performed in the switch. It is also possible to list client identifications in the configuration file and then prevent the server from interacting with clients that have not been so identified. "
we need somthing like that
dhcp relay is easily supportable by changing the dhcp configuration slightly in order not to have per-zone configuration, but per instance/subnet.
an instance is a subnet declaration, of a subnet which not necessarily must be directly attached to the firewall.
within an instance the already implemented parameter are configurable like our zone configruation already has.
with another configuration possibility, say checkbox, or the like, it must be possible then to define on which interfaces the dhcp server should listen
another checkbox could cause the dhcp server instance to be a relay to a specified server of the specified interface instead of being an authoritative server
|2008-06-12 10:12||peter-endian||New Issue|
|2008-06-12 15:47||peter-endian||Note Added: 0001306|
|2008-06-12 15:47||peter-endian||Target Version||2.2 => 2.3|
|2008-09-10 15:58||chris-endian||Target Version||2.3 => future|
|2008-11-13 09:19||peter-endian||Note Added: 0001784|
|2008-11-13 09:48||peter-endian||Note Added: 0001785|
|2008-11-13 14:55||peter-endian||Note Added: 0001787|
|2010-09-21 18:33||peter-endian||Status||new => confirmed|
|Copyright © 2000 - 2012 MantisBT Group|