-
Notifications
You must be signed in to change notification settings - Fork 41
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
external
flag for broker makes non-ZeroMQ cores not work
#634
Comments
This also applies when using --ipv4 (and I imagine --ipv6 as well). |
Have you tried this with the UDP broker? |
I don't remember. The TCP core definitely wasn't working. |
I was able to verify the TCP issue as well, but the UDP core works differently so I wasn't sure if that fails in this context as well. I will test it soon, but I wondered if you knew. |
Ok, @nightlark can you check again. |
I tested the tcp, tcpss, and udp cores; the --external flag no longer breaks any of them. |
closed with PR #720 |
Describe the bug
Starting the broker with
--external
with a core type other than ZeroMQ causes the broker to not work (federates are unable to connect).What is the expected behavior?
The other core types should continue working when given
--external
(they don't seem to need it, so it should either be ignored or it should be removed from the help message of non-ZMQ cores and give an error/warning when used).Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: