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

Running a O3D/O3X behind a NAT router #69

Closed
graugans opened this issue May 16, 2018 · 0 comments
Closed

Running a O3D/O3X behind a NAT router #69

graugans opened this issue May 16, 2018 · 0 comments

Comments

@graugans
Copy link
Member

If we want use the O3D or O3X behind a NAT router. The following ports need to be forwarded to the outside world.

TCP/IP: 80 (XMLRPC), 8080 (SWUpdate), 50010 (PCIC)

In case of the camera module we can overwrite the default port. But for the framegrabber we can't in case of the framegrabber the port number is red from the config or the default one is used.

 if (! this->cam_->IsO3X())
    {
      try
        {
          this->cam_ip_ = this->cam_->IP();
          this->cam_port_ =
            std::stoi(this->cam_->DeviceParameter("PcicTcpPort"));
        }
      catch (const ifm3d::error_t& ex)
        {
          LOG(ERROR) << "Could not get PCIC Port of the camera: " << ex.what();
          LOG(WARNING) << "Assuming default PCIC port: "
                       << ifm3d::DEFAULT_PCIC_PORT;
          this->cam_port_ = ifm3d::DEFAULT_PCIC_PORT;
        }
    }

I would prefer to have the ability to do an override of the default port when instantiating the framegrabber.

@theseankelly theseankelly removed their assignment Jan 12, 2020
@inbangsa inbangsa linked a pull request Sep 21, 2020 that will close this issue
ifm-csr pushed a commit that referenced this issue Oct 13, 2021
BigBoot pushed a commit that referenced this issue Oct 25, 2024
BigBoot pushed a commit that referenced this issue Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants