-
Notifications
You must be signed in to change notification settings - Fork 11
Fix wireguard integrations for 4.8.x #21
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
Merged
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
492041d
Fix 4.8.1 wireguard integration
Hertzole 7e358f4
Fix outdated comments
Hertzole 431a52f
Revert "Fix outdated comments"
Hertzole 1adc9f0
Again fix outdated comments without changing everything else
Hertzole d7eca02
Fix duplicate method that just appeared?
Hertzole 1bb9897
Revert "Fix duplicate method that just appeared?"
Hertzole fd7dfd1
oh my god I hate python and vscode
Hertzole f220edb
Add versioning to wireguard clients
Hertzole f5226d4
Add wireguard tests
Hertzole bc922c4
Revert "Add wireguard tests"
Hertzole 045363d
Hopefully fix test file git
Hertzole 7c96d5d
Return response array directly
Hertzole edb9644
Use existing semver library instead of using own version
Hertzole 42b860a
Keep track of firmware version self
Hertzole d201eac
Fix import
Hertzole af1884b
Fix version type
Hertzole 1ddaa44
Fix linting errors
Hertzole 00d3ddf
Fixed even more trailing whitespaces
Hertzole 85d59c2
make semver non-dev, linting
HarvsG 1867f26
improve typing and unify wireguard calls
HarvsG bd08ceb
make tunnel ID optional
HarvsG File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you check if this is true for modern firmware - as it seems you are using tunnel_id and ned peer_id
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What exactly do you want me to verify? Just so I understand.
But in-case you're referring to the comment being outdated, you'd be right.
Here's the full output of calling that endpoint on 4.8.1 (with some redactions)
{ "id": 7, "jsonrpc": "2.0", "result": { "status_list": [ { "enabled": true, "type": "wireguard", "tx_bytes": 24953488020, "peer_name": "PEER NAME HERE", "domain": [ "XXX.XXX.XXX.XXX" ], "group_id": 1234, "via": "wgclient1", "port": 51820, "tunnel_id": 10, "rx_bytes": 49725356924, "peer_id": 5678, "status": 1, "name": "Primary Tunnel", "ipv4": "XXX.XXX.XXX.XXX" } ], "mode": 0 } }Should I update the comment with the new response?