We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was experimenting with gpredict under windows 10 towards my macpc
I set a radio interface on port 7777 then used 7356
The radio interface showed as using port 7356 but wirshark traces show 7777 in use
I am unsure why gpredict hung onto the original port 7777 I was testing on
Please test by cycling Radio interface port and network traces on "engage" button
Andrew VK4TEC
The text was updated successfully, but these errors were encountered:
Have no idea how this can happen. Is this still an issue with the latest windows snapshot? https://github.com/csete/gpredict/releases/download/v2.3/gpredict-win32-2.3.37.zip
Sorry, something went wrong.
No branches or pull requests
I was experimenting with gpredict under windows 10 towards my macpc
I set a radio interface on port 7777 then used 7356
The radio interface showed as using port 7356 but wirshark traces show 7777 in use
I am unsure why gpredict hung onto the original port 7777 I was testing on
Please test by cycling Radio interface port and network traces on "engage" button
Andrew VK4TEC
The text was updated successfully, but these errors were encountered: