Home
build details

Show: section status errors & todos local changes recent changes last change in-page changes feedback controls

Networking, a.k.a. the hardest part

Modified 2018-09-28 by Andrea Censi

This page is for the DB18 configuration used in classes in 2018. For last year’s instructions see here.

A Duckiebot that is initialized according to Unit B-5 - Duckiebot Initialization.

Patience (channel your inner Yoda).

A Duckiebot that you can connect to and that is connected to the internet.

The instructions here are ordered in terms of preference, the first being the most preferable and best.

By default on boot your robot will look for a network with a “duckietown” SSID, unless you changed it in the SD card flashing procedure. You can connect to your robot wirelessly by connecting to that network.

This page describes how to get your robot connected to the wide-area network (internet).

TODO: would be great if we had some network diagrams here.

previous task next (12 of 27) index
task

The following was marked as "todo".

TODO: would be great if we had some network diagrams here.

File book/opmanual_duckiebot/atoms_17_operation_manual_duckiebot/1_7_networking_config.md.

File book/opmanual_duckiebot/atoms_17_operation_manual_duckiebot/1_7_networking_config.md
in repo duckietown/docs-opmanual_duckiebot branch master19-liam commit 07d4c56c
last modified by Russell on 2018-10-11 11:19:52

Created by function create_notes_from_elements in module mcdp_docs.task_markers.

Testing if your Duckiebot is Connected to the Internet

Modified 2018-10-04 by breandan

Some networks block pings from passing through, so a better way is to execute:

duckiebot $ sudo curl google.com

which will try to download the Google homepage. If it is successful, you should see an output like:

<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>

Option 3: Push Docker Images from Laptop

Modified 2018-10-11 by Russell

Since we are primarily using the internet to pull Docker images, we can simply connect the laptop and the Duckiebot then push Docker images from the laptop over SSH like so:

laptop $ docker save duckietown/image-name | ssh -C hostname docker load

Then the image will be available on your Duckiebot.

If you can connect to your laptop (e.g. through a router) but do not have internet access then you can proceed for now, but everytime you see a command starting with:

duckiebot $ docker run ...

note that you will need to pull onto your laptop and push to your Duckiebot in order to load the latest version of the image.

Because of mathjax bug

No questions found. You can ask a question on the website.