Local Companion App - Exposing local port to remote workspace doens't work

[0Grit]

Bug description

Steps to reproduce

1. Start GDB server (Jlinkgdbserver) on port 2331 on local machine

2. PS C:\Users\Grit\Downloads> ./'.\gitpod-local-companion-windows (2).exe' --auto-tunnel=false

3. PS C:\Users\Grit> ssh -F C:\Users\Grit\AppData\Local\Temp\gitpod_ssh_config -R 2331:localhost:2331 blush-coral-ojk0razu

Port still looks like it's exposed in the opposite direction

4. GDB Fails to connect
   

[4:02 PM] ila: Yes, as I described the same approach works on Linux but is broken on Windows.

Workspace affected

Not applicable

Expected behavior

GDB client should connect to GDB server

Example repository

https://github.com/gitpod-io/gitpod/tree/main/components/local-app

Anything else?

No response

[ila-embsys]

I have found where the problem is.

Local Companion App do forward from the remote side to the local side with the right ports but use ipv6. However, in my example OpenOCD app uses ipv4. So the Windows reject the connection.

When I had tried an app that listens to ipv6, everything had working as expected.

[0Grit]

@ila-embsys was it ipv6 or the fact that localhost is resolving incorrectly?

[iQQBot]

use 127.0.0.1 instead and try

[0Grit]

Yes. It worked when I used 127.0.0.1.

[ila-embsys]

@ila-embsys was it ipv6 or the fact that localhost is resolving incorrectly?

On my system, the hostname "hocalhost" resolves to ipv6 address "::1". So replacing the "localhost" hostname to direct ipv4 address "127.0.0.1" resolves the problem.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.