You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe:
The mcrouter and logger are services that can run under Windows and Linux platform. If these services run under Windows, the applications running under WSL (Windows Subsystem for Linux) with Ubuntu distro cannot connect to mcrouter and logger. The other way work fine, i.e. if services run in WSL, applications under Windows easily connect mcrouter and logger.
As a first step, changed the IP address of mcrouter and logger, replaced 127.0.0.1 to 172.23.96.1 (selected from ipconfig). But it didn't help. As well tried to make changes in the firewall settings of Windows Defender. Not sure whether made in the right way, but it also didn't help.
To Reproduce
Compile AREG SDK under Windows with enabled logging (default behavior).
Start mcrouter.exe and logger.exe
Optionally, to make sure that the there is a connection, can start logobserver.exe, type -r to start log observer and time -i to list connected instances. Result: it lists the mcrouter.exe ;
Open WSL and compile AREG SDK under Linux (Ubuntu) with enabled logging (default behavior).
Start logobserver.out, which theoretically should connect to logger.exe running under Windows, type -r to start observer, type -i to list connected instances. Result: it displays message that no instance is connected.
Start any application with IPC (for example, the client service application of example 12). Result: nothing happens.
Expected behavior
The applications should connect to the logger and mcrouter independent whether they run under Windows, WSL or Linux machine.
Desktop:
OS: Windows and WSL with Ubuntu Linux distro
Hardware: x64
Compiler: msvc for Windows (cl compiler), g++ or clang++ for Linux
AREG SDK version: latest sources in repo
Additional context
I do believe it is not a software issue, rather than configuration or security settings. There is a known issue accessing Windows service from WSL, but I was not able to solve it easily.
To change the IP address of mcrouter, edit router::*::address::tcpip = 127.0.0.1 in areg.init. The * can be replaced by application name or leave * if it reflects to all applications.
To change the IP address of logger, edit logger::*::address::tcpip = 127.0.0.1 in areg.init. The * can be replaced by application name or leave * if it reflects to all applications.
The text was updated successfully, but these errors were encountered:
Describe:
The
mcrouter
andlogger
are services that can run under Windows and Linux platform. If these services run under Windows, the applications running under WSL (Windows Subsystem for Linux) with Ubuntu distro cannot connect tomcrouter
andlogger
. The other way work fine, i.e. if services run in WSL, applications under Windows easily connectmcrouter
andlogger
.As a first step, changed the IP address of
mcrouter
andlogger
, replaced127.0.0.1
to172.23.96.1
(selected fromipconfig
). But it didn't help. As well tried to make changes in the firewall settings of Windows Defender. Not sure whether made in the right way, but it also didn't help.To Reproduce
mcrouter.exe
andlogger.exe
logobserver.exe
, type-r
to start log observer and time-i
to list connected instances. Result: it lists themcrouter.exe
;logobserver.out
, which theoretically should connect tologger.exe
running under Windows, type-r
to start observer, type-i
to list connected instances. Result: it displays message that no instance is connected.Expected behavior
The applications should connect to the
logger
andmcrouter
independent whether they run under Windows, WSL or Linux machine.Desktop:
cl
compiler), g++ or clang++ for LinuxAdditional context
I do believe it is not a software issue, rather than configuration or security settings. There is a known issue accessing Windows service from WSL, but I was not able to solve it easily.
To change the IP address of
mcrouter
, editrouter::*::address::tcpip = 127.0.0.1
in areg.init. The*
can be replaced by application name or leave*
if it reflects to all applications.To change the IP address of
logger
, editlogger::*::address::tcpip = 127.0.0.1
in areg.init. The*
can be replaced by application name or leave*
if it reflects to all applications.The text was updated successfully, but these errors were encountered: