new tmtc unix udp bridge #141
No reviewers
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Depends on
Reference: fsfw/fsfw#141
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "KSat/fsfw:mueller/feature/TmTcUnixBridge"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
fixes #125
Requires #137 . Requires #136 .
I might make the ports configurable by exposing setter functions.
(there still will be default ports I think).
WIP: new tmtc unix udp bridgeto new tmtc unix udp bridgeShall we merge this? is it already tested?
This has been tested and works on Linux. However, TMTC can be sent from any IP address right now as long as the port number is correct. I have not found another way, but maybe I am lacking some UDP/TCP basics.
new tmtc unix udp bridgeto WIP: new tmtc unix udp bridgeneed to update includes
WIP: new tmtc unix udp bridgeto new tmtc unix udp bridgebranch was updated. a new timeval operations is required which converts seconds to unix timeval.