Feature-rich wifi hotspot creator for Linux which provides both GUI and command-line interface. It is also able to create a hotspot using the same wifi card which is connected to an AP already ( Similar to Windows 10).
As you can see, the range is hardcoded to be [1, 254].
I have updated this piece of code to include configurable ending ranges (see code changes below).
By default, the range is still set to [1, 254]. However, if the dhcp-range option is passed on the command line or a configuration value of DHCP_RANGE is changed then those values are taken instead.
Examples:
--dhcp-range 150,160
--dhcp-range 155,165
Values are validated against the range [1, 254] (inclusive) and the condition lower < upper. Aside from those restrictions, I feel that any ranges specified by the user would be at the fault of the user themselves.
If any errors occur (non-integer types, range check fails, etc.) then the default [1, 254] range is used.
Aside from the feature changes, I have also updated the READMEs to include the feature description and an example, and the version flag has been updated.
Please let me know if there is anything else I need to do/change and I would be happy to respond.
This PR is linked to issue #336 .
I needed the ability to set a custom DHCP range for my use-cases. For example, I wanted the following IPs to be assigned to connections:
In the current
linux-wifi-hotspot
version, this is not possible. Here is how thedhcp-range
configuration value is set (link here) currently:As you can see, the range is hardcoded to be
[1, 254]
.I have updated this piece of code to include configurable ending ranges (see code changes below).
By default, the range is still set to
[1, 254]
. However, if thedhcp-range
option is passed on the command line or a configuration value ofDHCP_RANGE
is changed then those values are taken instead.Examples:
Values are validated against the range
[1, 254]
(inclusive) and the conditionlower < upper
. Aside from those restrictions, I feel that any ranges specified by the user would be at the fault of the user themselves.If any errors occur (non-integer types, range check fails, etc.) then the default
[1, 254]
range is used.Aside from the feature changes, I have also updated the READMEs to include the feature description and an example, and the version flag has been updated.
Please let me know if there is anything else I need to do/change and I would be happy to respond.