Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Default route #332

Closed
emschwartz opened this issue Sep 25, 2019 · 2 comments · Fixed by #365
Closed

Default route #332

emschwartz opened this issue Sep 25, 2019 · 2 comments · Fixed by #365
Assignees
@emschwartz
Labels
feature

Comments

@emschwartz
Copy link
Member

Nodes should be able to configure a "default route" so that even if they do not have a specific route to a destination, they will try forwarding the packet to the default route's next hop. For child nodes, this should automatically be set to the parent. For others, we may want to allow this to be configured separately.
@emschwartz emschwartz self-assigned this Sep 25, 2019
@emschwartz emschwartz mentioned this issue Sep 25, 2019
Closed
15 tasks
@gakonst
Copy link
Member

gakonst commented Sep 26, 2019

note: A node cannot know that it's a child currently

@emschwartz
Copy link
Member Author

It would just check if it has a parent

@emschwartz emschwartz mentioned this issue Sep 30, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@emschwartz emschwartz

Labels
feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reliability improvements interledger/interledger-rs
2 participants
@emschwartz @gakonst