Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting all-zeroes gateway IP for NI is not allowed #41

Merged
merged 2 commits into from
Dec 19, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 11 additions & 15 deletions go/config/netinst.pb.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

26 changes: 12 additions & 14 deletions proto/config/netinst.proto
Original file line number Diff line number Diff line change
Expand Up @@ -113,12 +113,11 @@ message NetworkInstanceConfig {
AddressType ipType = 39;

// network ip specification
// If ip.gateway is set to all-zeroes IP, default route will not be propagated
// to applications for interfaces connected to this network instance.
// Default route propagation is also automatically suppressed when the network
// instance is air-gapped or when the uplink is app-shared without default route
// configured. This behaviour can be further customized using static_routes
// (see below).
// Note that ip.gateway must be a valid IP address and can not be all-zeroes.
// To suppress automatic propagation of the default route into apps, configure network
// instance as air-gapped (without uplink) or mark the uplink as app-shared
// (not for management) and ensure that it will not get a default route
// (e.g. set ip.gateway of the attached NetworkConfig to all-zeroes IP).
ipspec ip = 40;

// static DNS entry, if we are running DNS/DHCP service
Expand All @@ -143,14 +142,13 @@ message NetworkInstanceConfig {
// routes can be propagated at the same time, there are no restrictions for using both.
//
// Note that the default route (with the bridge IP as the gateway) is automatically
// propagated to connected applications with these exceptions:
// a) default route propagation is explicitly disabled by setting
// NetworkInstanceConfig.ip.gateway to an all-zeroes IP
// b) network instance is air-gapped (without uplink)
// c) the uplink is app-shared (not management) and does not have a default route
// of its own
// In the b) and c) cases, it is possible to enforce default route propagation
// by configuring a static default route for the network instance.
// propagated to connected applications, unless network instance is air-gapped
// (without uplink) or the uplink is app-shared (not management) and does not have
// a default route of its own. In both cases, it is possible to enforce default
// route propagation by configuring a static default route for the network instance.
//
// For more info on static and connected routes please refer to:
// https://wiki.lfedge.org/display/EVE/Connected+and+Static+IP+Route
//
// This option is only valid for local network instances. For other types
// of network instances, it will be ignored.
Expand Down
Loading