Change DHCP range api and set server as default mode#2988
Change DHCP range api and set server as default mode#2988patrickelectric merged 2 commits intobluerobotics:masterfrom
Conversation
0ab01df to
e4154dd
Compare
e4154dd to
1095c92
Compare
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
1095c92 to
452a609
Compare
|
ping @Williangalvani @JoaoMario109 |
|
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. |
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.
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.
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.
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.
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.
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.
No description provided.