You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If one user would like to access meta/storage from another network, say, nebulagraph in the public cloud, spark cluster on-premise. It's natural to have storaged configured with a public IP provided by NAT/Floating IP of the cloud provider.
Issue:
The storaged won't boot up as it's doing validation based on all addresses of NIC:
return Status::Error("%s is not a valid ip in current host, candidates: %s",
Suggestion:
We should consider allowing addresses to be configured as host ip/service identity but somehow allow internal network routing(to prevent west-east traffic to be routed outside of the OS)?
Background:
If one user would like to access meta/storage from another network, say, nebulagraph in the public cloud, spark cluster on-premise. It's natural to have storaged configured with a public IP provided by NAT/Floating IP of the cloud provider.
Issue:
The storaged won't boot up as it's doing validation based on all addresses of NIC:
nebula/src/common/network/NetworkUtils.cpp
Lines 325 to 326 in 2f3259d
Suggestion:
We should consider allowing addresses to be configured as host ip/service identity but somehow allow internal network routing(to prevent west-east traffic to be routed outside of the OS)?
ref: https://discuss.nebula-graph.com.cn/t/topic/9726/22
The text was updated successfully, but these errors were encountered: