provisioning a client with 2 nics will have to default gateways
|Assigned To:||Marek Hulán|
|Target version:||Team Marek backlog|
|Found in release:||Pull request:||https://github.com/theforeman/community-templates/pull/345|
|Velocity based estimate||-|
Description of problem:
provisioning a client with 2 nics will have to default gateways.
Version-Release number of selected component (if applicable):
Create 2 subnets and specify the gateway for etch one then create a client and add 2 networks to point to these 2 subnets. After you kickstart the client the client will have 2 default gateways. when we create a new host we need to have an option to specify the default gateway instead to remove the gateway from the subnets.
#1 Updated by Marek Hulán 9 months ago
- Subject changed from provisioning a client with 2 nics will have to default gateways to provisioning a client with 2 nics will have to default gateways
- Assigned To set to Marek Hulán
- Target version set to Team Marek backlog
The issue is not the fact we have multiple gateways but that we don't have control over which default gateway wins. I didn't find a way to specify custom metric in dhcpd and it probably make sense to define only one default gateway based on which interface is primary. Therefore we can adjust the configuring template so it defines DEFROUTE accordingly. I don't know how this works on deb based systems, but so far no one reported issues there.
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset community-templates|92b5ca92219efa90b68a3517a92371dca61e235a.