View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002525NoesisGUIInspectorpublic2023-03-01 14:312026-08-17 12:47
Reportersteveh Assigned Tojsantos  
PrioritynormalSeverityfeature 
Status resolvedResolutionfixed 
Product Version3.2.0 
Target Version3.2Fixed in Version4.0 
Summary0002525: Inspector: Support explicit IP communication
Description

Hi guys,

Right now it looks like the inspector is listening to any traffic on a given port and refreshing the servers when it receives data in RemoteCommandsClient.cpp.

Likewise, the game broadcasts on the announcement socket to all IP in RemoteCommands.cpp

We've had a request internally to specify an exact IP address to listen to, e.g. launch the inspector with something like "-ListenIP=x.x.x.x", and maybe even on the game, e.g. "-InspectorIP=x.x.x.x".

This would reduce the chance of clashing / connecting to the wrong IP if we're all on the same domain.

PlatformAny

Relationships

related to 0002418 resolvedsfernandez Add an option to limit Inspector target to local applications only 
related to 0005014 resolvedhcpizzi Inspector improvements 

Activities

jsantos

jsantos

2023-03-03 21:14

manager   ~0008321

Hi Steve,

In the latest version of the Inspector (0002418) there is a checkbox for connecting only to local IPs.

Not sure if this is helpful to you, I assume this is for consoles connected to a different IP right?
steveh

steveh

2023-03-06 19:01

reporter   ~0008324

Hi Jésus, I think that would partially help. However, the full solution would be a manual IP entry to support consoles as you have said. Ideally we'd be able to target a specific IP on the network so our consoles and dev machines can communicate directly without broadcasting to all IPs.
jsantos

jsantos

2023-03-06 23:36

manager   ~0008325

Sure, understood.
jsantos

jsantos

2026-08-17 12:47

manager   ~0012520

This has been solved in 4.0.

By default, the network discovery drop-down is set to Auto, meaning the scan will look for applications broadcasting on your local network. If you need to restrict the search, you can customize this behavior using the drop-down menu (for example, selecting 127.0.0.1 will filter the search to only scan for local applications).

Issue History

Date Modified Username Field Change
2023-03-01 14:31 steveh New Issue
2023-03-03 21:12 jsantos Assigned To => jsantos
2023-03-03 21:12 jsantos Status new => assigned
2023-03-03 21:12 jsantos Relationship added related to 0002418
2023-03-03 21:14 jsantos Note Added: 0008321
2023-03-03 21:14 jsantos Status assigned => feedback
2023-03-06 19:01 steveh Note Added: 0008324
2023-03-06 19:01 steveh Status feedback => assigned
2023-03-06 23:35 jsantos Target Version => 3.2.0
2023-03-06 23:36 jsantos Note Added: 0008325
2023-03-27 12:14 jsantos Target Version 3.2.0 => 3.2
2026-04-02 12:47 jsantos Relationship added related to 0004959
2026-04-02 12:52 jsantos Description Updated
2026-04-28 14:03 jsantos Relationship added related to 0005014
2026-04-28 14:04 jsantos Relationship deleted related to 0004959
2026-08-17 12:47 jsantos Status assigned => resolved
2026-08-17 12:47 jsantos Resolution open => fixed
2026-08-17 12:47 jsantos Fixed in Version => 4.0
2026-08-17 12:47 jsantos Note Added: 0012520