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
For reasons relating to the salesmen wanting to do customer-facing demonstrations of our networkable products, I'll be spawning one or more of these services on the localhost. But I'm having trouble discovering several services that are on the same physical host, since they respond from 172.16.16.158, the interface's IP address, instead of from 127.0.0.3, 127.0.0.4, etc, where the service is actually available.
This means that instead of receiving two or more instances of ResponderFound, I'm getting one ResponderFound and then one or more ResponseUpdates, which change the IP address back and forth.
My implementation is the broadcast example, mutatis mutandis, both ends having the .loopback() option.
Is there something I'm missing here?
The text was updated successfully, but these errors were encountered:
For reasons relating to the salesmen wanting to do customer-facing demonstrations of our networkable products, I'll be spawning one or more of these services on the localhost. But I'm having trouble discovering several services that are on the same physical host, since they respond from 172.16.16.158, the interface's IP address, instead of from 127.0.0.3, 127.0.0.4, etc, where the service is actually available.
This means that instead of receiving two or more instances of
ResponderFound
, I'm getting oneResponderFound
and then one or moreResponseUpdate
s, which change the IP address back and forth.My implementation is the broadcast example, mutatis mutandis, both ends having the
.loopback()
option.Is there something I'm missing here?
The text was updated successfully, but these errors were encountered: