Bridging over ethernet to the Duckiebot about csce274

[18r441m]

could you attach the exact command you ran. Also, did you use to identify the duckiebot?

[Musa-Azeem]

I's getting the same error. We booted the duckiebot and saw that is was ready using 'dts fleet discover'. When I try to ssh into it using 'ssh [email protected]' I get 'ssh: Could not resolve hostname duck28.local: Name or service not known'. I also can't access http://duck28.local/ or http://duck28/. I should mention that I was able to ssh into the duckiebot once, using quackquack password, but I can't get it to work again.

[Musa-Azeem]

Update: I was able to make it work. Not sure what the problem was exactly but I think my ethernet cable may have been damaged because it worked with a new one

[marksoehner]

We followed this documentation https://docs.duckietown.org/daffy/opmanual_duckiebot/out/duckiebot_network.html

the hostname of the duckiebot is duck29

Our ethernet cord also looks a bit damaged, but I don't know if that is what is causing the issue. I was able to ping the duckiebot, set up the dashboard, and look through the duckiebot camera.

[18r441m]

I'm closing the issue since it seems both teams resolved the issue

[Jennak1]

I haven't been able to fix this issue.

[18r441m]

@Jennak1 I'm reopening the issue.

Firstly, check to ensure a physical connection between your computer and the dukciebot. The Ethernet port on the duckiebot has a light indicator, ensure that light is on.

If the above is true, go ahead and ping the duckiebot. Do so by running: ping duckiebot-hostname.local

Let me know if you get any response.

[Jennak1]

The Ethernet port was flashing. I ran ping duck#.local and didn't get anything. I did not see this specific command in the documentation. I will try this.

[18r441m]

The command I mentioned is the same one you ran. I forgot to ask but did you run dts fleet discover? and was there a response?

[Jennak1]

yes, we ran that before trying to bridge ethernet and got nothing. And after I set up the bridge for the ethernet I did it again and nothing. Pretty confident I set up the bridge correctly, but as soon as I tried to do the first ssh command it would not work.

[Jennak1]

As soon as I ran dts fleet discover just now the status came up to ready but the dashboard still displays down.

[brendanreeder]

Hey ibrahim, I am also having issues with ssh into the [email protected] I am getting the error "kex_exchange_identification: read: Connection reset by peer" I've checked google and they say to change the host.deny and .allow files. however no luck. any suggestions?

[18r441m]

@brendanreeder restart the duckiebot by unplugging the battery and plugging it back in.