One-Hop Routing #132
Comments
|
Update: I just found the gitter room where there has been more discussion and it looks like one-hop is not supported. Can the website be updated to indicate that? It would have saved me a lot of time to know not to use Sub-IoT in the first place. |
|
Thanks for bringing this up. I see that one hop topology is mentioned on
the DASH7 intro page (which explains the spec, not the Sub-IoT
implementation), or did you see it on another place as well? You are
right that it would be better to indicate on the website that not all
spec features are implemented. Will add that. Furthermore, development
is pretty much on hold (at least from our side), so will add this
message as well.
On 3/15/24 01:51, Toshi Taperek wrote:
Update: I just found the gitter room where there has been more
discussion and it looks like one-hop is not supported. Can the website
be updated to indicate that? It would have saved me a lot of time to
know not to use Sub-IoT in the first place.
—
Reply to this email directly, view it on GitHub
<#132 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLEMIWXQHFNQF44M2PMBC3YYJAZTAVCNFSM6AAAAABEXCL476VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYG4YDSMJRGY>.
You are receiving this because you are subscribed to this
thread.Message ID:
***@***.***>
--------------lHAmymsvXYHkxb65v6ZcAiM0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Thanks for bringing this up. I see that one hop topology is
mentioned on the DASH7 intro page (which explains the spec, not
the Sub-IoT implementation), or did you see it on another place as
well? You are right that it would be better to indicate on the
website that not all spec features are implemented. Will add that.
Furthermore, development is pretty much on hold (at least from our
side), so will add this message as well.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 3/15/24 01:51, Toshi Taperek wrote:<br>
</div>
<blockquote type="cite" ***@***.***">
<p dir="auto">Update: I just found the gitter room where there has
been more discussion and it looks like one-hop is not supported.
Can the website be updated to indicate that? It would have saved
me a lot of time to know not to use Sub-IoT in the first place.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
Reply to this email directly, <a href="#132 (comment)" moz-do-not-send="true">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABLEMIWXQHFNQF44M2PMBC3YYJAZTAVCNFSM6AAAAABEXCL476VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYG4YDSMJRGY" moz-do-not-send="true">unsubscribe</a>.<br>
You are receiving this because you are subscribed to this
thread.<img src="https://github.com/notifications/beacon/ABLEMIQAHBJNDFHOYYIXFEDYYJAZTA5CNFSM6AAAAABEXCL476WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTXEHQXY.gif" alt="" moz-do-not-send="true" width="1" height="1"><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message
ID: <span><Sub-IoT/Sub-IoT-Stack/issues/132/1998709116</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#132 (comment)",
"url": "#132 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
</blockquote>
</body>
</html>
…--------------lHAmymsvXYHkxb65v6ZcAiM0--
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Sub-IoT community,
I've been looking at and trying Sub-IoT for some time now, and I've just gotten to the point where we need to switch on the one-hop routing that made us choose D7A as our stack in the first place.
However, to my dismay it looks like there is a TODO from 7 years ago saying "TODO hopping not yet supported"!
The website also mentions the one-hop routing, but is it true that one-hop is just completely unsupported? Is there a plan to implement this any time soon?
I see mention about the ability for another routing protocol to be added, but is this reasonably feasible?
The text was updated successfully, but these errors were encountered: