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
What?
I was trying to run mtr and see the output for tcp port 22.
Why?
There seems to be network issue at my office vpn
What happened (include all command output)?
I saw that when I run default tcp (port 80) or icmp or udp (port 33xxx) then it works fine but when I run with option for port with tcp or udp then, there is no output shown after command finishes running.
I also ran wireshark and I can see that packets were sent out by my mac but cli showed no report output.
What did you expect to happen?
I expect to see regular report output which shows the hops taken with loss and other network characteristics. See example below for working scenario with default port (80).
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
What?
I was trying to run mtr and see the output for tcp port 22.
Why?
There seems to be network issue at my office vpn
What happened (include all command output)?
I saw that when I run default tcp (port 80) or icmp or udp (port 33xxx) then it works fine but when I run with option for port with tcp or udp then, there is no output shown after command finishes running.
I also ran wireshark and I can see that packets were sent out by my mac but cli showed no report output.
What did you expect to happen?
I expect to see regular report output which shows the hops taken with loss and other network characteristics. See example below for working scenario with default port (80).
Step-by-step reproduction instructions (by running
brew
commands)1. brew update 2. brew upgrade 3. brew install mtr 4. sudo mtr --tcp --port 22 -w -o "LSRD BAW MXI" 194.108.117.16
The text was updated successfully, but these errors were encountered: