Change DHCP range api and set server as default mode #2988
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
patrickelectric
force-pushed
the
range
branch
from
0ab01df to
e4154dd
Compare
patrickelectric
force-pushed
the
range
branch
from
e4154dd to
1095c92
Compare
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
patrickelectric
force-pushed
the
range
branch
from
1095c92 to
452a609
Compare
|
ping @Williangalvani @JoaoMario109 |
joaomariolago
approved these changes
Nov 13, 2024
ES-Alexander
added
docs-complete
|
Does this mean that blueOS would act as a DHCP server on the default eth0 network? If that is the case, then that worries me a little bit, since we usually have an existing device there that does that already, and having two DHCP servers is usually not a great experience. Or does it only kick in if it did not already get a DHCP lease from an existing DHCP server? |
We could turn on the DHCP server if we fail to find one running on the network, I'll create an issue for that. |
goasChris
added a commit
to MithalAS/BlueOS
that referenced
this pull request
Feb 25, 2025
In bluerobotics#2988 BlueOS defaultet to running a DHCP server. This will not work for our needs, as we handle our own DHCP server, and we've seen instance of this DHCP server taking over client, unfortunately.
goasChris
added a commit
to MithalAS/BlueOS
that referenced
this pull request
Mar 26, 2025
In bluerobotics#2988 BlueOS defaultet to running a DHCP server. This will not work for our needs, as we handle our own DHCP server, and we've seen instance of this DHCP server taking over client, unfortunately.
goasChris
added a commit
to MithalAS/BlueOS
that referenced
this pull request
Mar 26, 2025
In bluerobotics#2988 BlueOS defaultet to running a DHCP server. This will not work for our needs, as we handle our own DHCP server, and we've seen instance of this DHCP server taking over client, unfortunately.
goasChris
added a commit
to MithalAS/BlueOS
that referenced
this pull request
Mar 26, 2025
In bluerobotics#2988 BlueOS defaultet to running a DHCP server. This will not work for our needs, as we handle our own DHCP server, and we've seen instance of this DHCP server taking over client, unfortunately.
goasChris
added a commit
to MithalAS/BlueOS
that referenced
this pull request
Mar 27, 2025
In bluerobotics#2988 BlueOS defaultet to running a DHCP server. This will not work for our needs, as we handle our own DHCP server, and we've seen instance of this DHCP server taking over client, unfortunately.
goasChris
added a commit
to MithalAS/BlueOS
that referenced
this pull request
Mar 28, 2025
In bluerobotics#2988 BlueOS defaultet to running a DHCP server. This will not work for our needs, as we handle our own DHCP server, and we've seen instance of this DHCP server taking over client, unfortunately.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.