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.

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

examples/gnrc_border_router: Add ethos and start_network.sh to README.md #4996

Merged
merged 1 commit into from
Apr 14, 2016

Conversation

kYc0o
Copy link
Contributor

@kYc0o kYc0o commented Mar 8, 2016

I had added it in a wrong branch, open again with correct commit message
Added documentation for ethos and automatic setup with the start_network.sh script on #4725

@kYc0o kYc0o added Area: network Area: Networking Area: doc Area: Documentation labels Mar 8, 2016
@kYc0o kYc0o added this to the Release 2016.04 milestone Mar 8, 2016
@OlegHahm OlegHahm added the State: waiting for other PR State: The PR requires another PR to be merged first label Mar 8, 2016


# gnrc_border_router with ethos
A new setup is possible thanks to \#4438(https://github.com/RIOT-OS/RIOT/pull/4438) on which only one serial interface is needed. This is done through the ethos (Ethernet Over Serial) driver that multiplexes serial data between ethernet packets and shell commands.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not typical to reference a merged PR in a documentation text.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, please try to keep the lines under 80 characters long.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes we'll wait until the PR is merged, then I'll change that part

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But #4438 is already merged

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we are waiting for #4725

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean I should remove the reference to the closed PR?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. :-)

@jnohlgard
Copy link
Member

Can you change the prefix to anything in the ULA range (fc00::/7) instead of affe:: to use the RFC 4193 designated private use addresses. Preferably something in fdxx::, see https://en.wikipedia.org/wiki/Unique_local_address#Properties

@miri64
Copy link
Member

miri64 commented Mar 8, 2016

2001:0000::/29 - 2001:01F8::/29 are also viable for experimental use



# gnrc_border_router with ethos
A new setup is possible on which only one serial interface is needed. This is done through the ethos (Ethernet Over Serial) driver that multiplexes serial data between ethernet packets and shell commands.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/ethos/\0/g

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And still too long lines

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the long lines bother you? Do you think I should split into 2 paragraphs?

@jnohlgard
Copy link
Member

@authmillenon I interpret that paragraph that they mean more for routing experiments across sites for developing the IPv6 internet, not for local IoT experiments.

Now, you should be able to ping your nodes using the global addres starting by your prefix, on our case `affe::`.

# gnrc_border_router using automatic configuration (not merged yet)
In \#4725 (https://github.com/RIOT-OS/RIOT/pull/4725) an effort to automate all the previous steps is done using 3 tools:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can have proper links in markdown doing this

[\#4725](https://github.com/RIOT-OS/RIOT/pull/4725)

(and it's not too disruptive for local readers either)

@miri64
Copy link
Member

miri64 commented Mar 8, 2016

@authmillenon I interpret that paragraph that they mean more for routing experiments across sites for developing the IPv6 internet, not for local IoT experiments.

Well the RFC also references 2001:db8::/32 for documentation purposes which is exactly what we have here. :-)

@biboc
Copy link
Member

biboc commented Mar 23, 2016

Ping @authmillenon

@kYc0o
Copy link
Contributor Author

kYc0o commented Mar 23, 2016

Oops! That's me, I'll address the comments ASAP

@kYc0o
Copy link
Contributor Author

kYc0o commented Mar 26, 2016

I addressed most of the comments and changed the addresses for "documentation purposes" to 2001:db8::/32.

@emmanuelsearch
Copy link
Member

@kYc0o what's the status on this PR, on your side?
@aabadie do you see ways to improve this README based on your recent experience?

@kaspar030
Copy link
Contributor

Current #4725 drops the slip mode completely. Should the readme reflect this?

@OlegHahm
Copy link
Member

Current #4725 drops the slip mode completely. Should the readme reflect this?

I think it might be nice to add a hint that you can use SLIP (or any Ethernet transceiver) as well.

@kYc0o
Copy link
Contributor Author

kYc0o commented Mar 30, 2016

On my side I think I addressed most of the comments, maybe a paragraph is apparently too large but I can't see how to split it or male it short. Otherwise we are still waiting for #4725

@kYc0o
Copy link
Contributor Author

kYc0o commented Apr 1, 2016

Looking at #4725 there are lots of changes so it seems this is very outdated. @kaspar030 can you confirm what is up-to-date and what's not?

@kYc0o
Copy link
Contributor Author

kYc0o commented Apr 12, 2016

As for my last tests, this guide is still valid, aiming to merge it once #4725 is merged too?

@kaspar030 kaspar030 removed the State: waiting for other PR State: The PR requires another PR to be merged first label Apr 12, 2016
@kaspar030
Copy link
Contributor

ACK after you shorten the lines to <= 80 characters. :)

```bash
sudo sh start_network.sh /dev/ttyACMx tap0 2001:db8::/64
```

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be great to mention here that one has access to the shell here. For instance, one can track the neighbour cache using ncache.

@haukepetersen
Copy link
Contributor

@aabadie: thanks for you input!

@kYc0o: could you adjust the README ASAP!? Would be good to merge this as soon as possible, as the border router app was merged and has a broken doc currently...

@@ -1,4 +1,144 @@
# gnrc_networking_border_router example
# gnrc_border_router using automatic configuration
A new setup is possible on which only one serial interface is needed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is now the default config, how about rephrasing the first two sentences with something like "This setup uses a single serial interface, ethos (Ethernet Over Serial) and UHCP (micro Host Control Protocol).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UHCP (micro Host Control Protocol)

micro host configuration protocol ;)

@kYc0o
Copy link
Contributor Author

kYc0o commented Apr 13, 2016

Comments addressed. Sorry for the delay, I was sick this morning... Please check if all comments were correctly addressed.

By typing `help` you will get the list of available shell commands.

At this point you should be able to ping motes using the global address.
For instance, if you use the `gnrc_networking` example, you can ping with:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"example" => "example on the mote"
"ping" => "ping it from your machine"

@emmanuelsearch
Copy link
Member

Thanks. Added a few comments. ACK when addressed.

@kYc0o
Copy link
Contributor Author

kYc0o commented Apr 13, 2016

Thanks to you @emmanuelsearch.

This is done through the same serial interface.
By typing `help` you will get the list of available shell commands.

At this point you should be able to ping motes using the global address.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using the global address => using their global address

@kYc0o
Copy link
Contributor Author

kYc0o commented Apr 14, 2016

Since there's already an ACK, I'll squash the commits and merge. Since it is a readme I don't think Murdock is required for this. I'll let some minutes before doing it, in case of someone has more comments.

@emmanuelsearch
Copy link
Member

re-ACK. Merge at will (and back port to release branch asap).

@kYc0o
Copy link
Contributor Author

kYc0o commented Apr 14, 2016

Squashed and go!

@kYc0o kYc0o merged commit 998c4ab into RIOT-OS:master Apr 14, 2016
@miri64
Copy link
Member

miri64 commented Apr 19, 2016

Needs backport.

@miri64 miri64 added the Process: needs backport Integration Process: The PR is required to be backported to a release or feature branch label Apr 19, 2016
@miri64 miri64 removed the Process: needs backport Integration Process: The PR is required to be backported to a release or feature branch label Apr 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: doc Area: Documentation Area: network Area: Networking
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants