Service cloth and IPv4
After starting DevClusterSetup.ps1, the default network gateway listens on IpV6 only even if there is no ipv6 IP address on the host. Since we only have ipv4 in my lap, I am wondering how to link it to ipv4?
PS C:\Program Files\Microsoft SDKs\Service Fabric\ClusterSetup> netstat -ano | select-string 19000 TCP 127.0.0.1:2880 127.0.0.1:19000 ESTABLISHED 7848 TCP 127.0.0.1:19000 0.0.0.0:0 LISTENING 5764 TCP 127.0.0.1:19000 127.0.0.1:2880 ESTABLISHED 5764 TCP [::1]:19000 [::]:0 LISTENING 5764 PS C:\Program Files\Microsoft SDKs\Service Fabric\ClusterSetup> get-process -id 5764 Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName ------- ------ ----- ----- ----- ------ -- ----------- 155 61 5436 13056 52 0.09 5764 FabricGateway PS C:\Program Files\Microsoft SDKs\Service Fabric\ClusterSetup> telnet 192.168.88.153 19000 Connecting To 192.168.88.153...Could not open connection to the host, on port 19000: Connect failed
As you can see FabricGateway is the one listening on port 19000, but I cannot connect to it with an IPv4 address.
If you have an IPv4-only environment, this will cause an interesting problem.
How can we customize this?
source to share
For security reasons, the DEV cluster listens by default on loopback addresses, 127.0.0.0:19000
for IPv4 and [::1]:19000
for IPv6, to deny connections from outside the machine. telnet 192.168.88.153 19000
does not work because it tries to connect to the address without 192.168.88.153
your machine's feedback , there is no listener by default 192.168.88.153:19000
. This is not about IPv4 and IPv6. If you want to connect to 192.168.88.153
, you will need to replace localhost
with 192.168.88.153
or the fully qualified domain name of your machine in the cluster manifest file. Keep in mind that this makes your endpoint visible from the outside of your car.
<NodeList>
<Node NodeTypeRef="NodeType01" IsSeedNode="true" IPAddressOrFQDN="localhost" NodeName="Node1" FaultDomain="fd:/RACK1" UpgradeDomain="MYUD1" />
source to share