22 lines
1.1 KiB
Markdown
22 lines
1.1 KiB
Markdown
---
|
|
title: "Running ROS2 with localhost only."
|
|
date: 2024-05-22T21:36:00+03:00
|
|
draft: false
|
|
summary: "Ever had ROS2 DoS your router accidentally? Want to learn how to stop that from happening? Well, here you are."
|
|
author: "Rusted Skull"
|
|
series: []
|
|
tags: ["Random"]
|
|
---
|
|
|
|
Recently I had the requirement to run ROS2 with a specific automotive stack on a PC that's connected to my home network.
|
|
Following the 3rd reinstall due to my evolving need to use a GPU, everything was roughly up and running. I started the stack,
|
|
and to my surprise, everything worked.
|
|
|
|
That is, until I stopped paying attention, forgot what my PC was doing, and noticed that
|
|
my phone was having trouble staying on WiFi. The router was seemingly losing its uplink connection, and the ISP saw a similar effect
|
|
on their end. Following some cable replacements and router reboots, I was headed towards a full router reset per the advice of the ISP tech.
|
|
I didn't get quite that far, however: everything started working after I unplugged my computer from the router. I revive the computer,
|
|
and see the ROS2 stack still running there. Welp, couplrit found. Now, what do we do about it?
|
|
|
|
|