Michael
My feedback
-
176 votes
An error occurred while saving the comment -
38 votes
An error occurred while saving the comment Michael
commented
From my point of view this request is very important and the current behavior is a BUG, since why ever at all a device schould get an IP address for example out of LAN 1 when beeing connencted to any other one??
The host will not be able to connect anywhere at all unless one manually sets - and at this time one is always forced to do so - a matching fixed IP, Mask, Gateway and DNS Server(s) everytime the device is beeing moved!
This is not "state of the art" and therefore from my point of view this issue has to be fixed very soon!
Every DHCP server needs it´s own assignment list and if there is no assignment in some networks for some clients they have to take an IP out of the related lease range of the network they are connected to at the moment.
Michael
supported this idea
·
-
20 votes
An error occurred while saving the comment Michael
commented
Yes!! Allow Firmware-update in HA - mode on XG without rebooting both devices at the same time like in UTM/SG - OS possible.
Why is there the need boot both devices at the same time during FW - updates in HA-mode, since the connection schould be online 24x7?
That´s why HA is implemeted!!Michael
supported this idea
·
An error occurred while saving the comment Michael
commented
Allow Firmware-update in HA - mode on XG without rebooting both devices at the same time like in UTM/SG - OS possible.
Why is there the need boot both devices at the same time during FW - updates in HA-mode, since the connection schould be online 24x7? That´s why HA is implemeted!! -
256 votesMichael
supported this idea
·
-
130 votesMichael
supported this idea
·
-
403 votes
This is being considered. The current intention is to add a superadmin role, making the default admin account just a member of that role.
This will allow you to create new superadmin accounts, capable of logging into the shell, adding ssh keys, and any other features limited currently to the named admin account.
Second, you will be able to disable or demote the named admin account.
Michael
supported this idea
·
-
11 votesMichael
supported this idea
·
-
8 votesMichael
supported this idea
·
-
30 votesMichael
supported this idea
·
-
63 votesMichael
supported this idea
·
-
108 votes
This is currently being planned for inclusion in an upcoming version
Michael
supported this idea
·
-
873 votesUnder Review ·
AdminStuart Hatto, XG Product Manager
(Admin, Sophos Features & Ideas Laboratory)
responded
This feature is under review but as yet is not committed.
An error occurred while saving the comment Michael
commented
If there is a production environment - with remote and service work - where one cannot reboot the device during working houres, there will be no possibility to update the device at all.
Michael
supported this idea
·
-
13 votesMichael
supported this idea
·
-
552 votes
This is a high priority feature, and will likely be targeted as soon as possible after v17 ships, though it is not yet committed to a release.
Michael
supported this idea
·
-
353 votes
This will be implemented in a future release. It is being included as part of a larger project, to generally improve configuration capabilities across the product. Version for release is not yet confirmed.
Michael
supported this idea
·
-
204 votesMichael
supported this idea
·
-
66 votesMichael
supported this idea
·
-
17 votesMichael
supported this idea
·
-
198 votesMichael
supported this idea
·
-
12 votesMichael
shared this idea
·
Hello all,
it is already possible to assign a fixed mac - IP binding in the DHCP server.
From my point of view the static and dynamic range schould stay separated.
Why?
If one will use the dynamic range with fixed mappings, the number of clients to connect dynamically will decrease - suddenly to 0!
It is up to every admin to very well plan the usage of IP address ranges within the complete network range to avoid IP address conflicts.
1. Network devices like routers, switches, access points and so on
2. Servers
3. Printers, Scanner devices and Clients / Workstations that are always present
4. Portable devices like Laptops, card phones and so on, that will not be always connected
1 to 2 is always static with a fixed IP configured
3 is static or may be assigned to a fixed mapping via DHCP outside of the dynamic range
4 is normally dynamic and the IP comes out of the dynamic range. In some cases one can behave like 3 with some devices here.
So one has to devide the static from the dynamic range(s) to prevent running out of free IPs of the dynamic part and / or to prevent IP address conflicts.
In Short:There is no need for this request / function and I dissagree to this request.
Sorry