hyperboria / bugs

Peer-to-peer IPv6 networking, secure and near-zero-conf.
154 stars 17 forks source link

Not working on windows 7 #60

Closed misuzu closed 9 years ago

misuzu commented 9 years ago

Used this guide to build on Debian 8: https://github.com/hyperboria/cjdns/blob/master/doc/install/windows.md

C:\>cjdroute --nobg < cjdroute.conf
1437493720 INFO cjdroute2.c:580 Cjdns i386 win32
1437493720 INFO cjdroute2.c:584 Checking for running instance...
1437493720 DEBUG UDPAddrIface.c:294 Bound to address [0.0.0.0:57532]
1437493720 DEBUG AdminClient.c:333 Connecting to [127.0.0.1:11234]
1437493720 DEBUG Pipe.c:134 Buffering a message
1437493720 DEBUG cjdroute2.c:629 Sent [140] bytes to core
1437493720 INFO RandomSeed.c:42 Attempting to seed random number generator
1437493720 INFO RandomSeed.c:50 Trying random seed [RtlGenRandom() (Windows)] Success
1437493720 INFO RandomSeed.c:64 Seeding random number generator succeeded with [1] sources
1437493720 INFO LibuvEntropyProvider.c:59 Taking clock samples every [1000]ms for random generator
1437493720 DEBUG 437493720 DEBUG Pipe.cC:231 ore.cPipe [\\.\pipe\cjdns_pipe_client-core-727uzv1ypnz8lyv7s4kwgvvyr4xjrm] established connection:1256 437493720 DEBUG GPipe.cetting pre-configuration from client:1253 Sending buffered message
1437493720 DEBUG Pipe.c:231 Pipe [\\.\pipe\cjdns_pipe_client-core-727uzv1ypnz8lyv7s4kwgvvyr4xjrm] established connection
1437493720 DEBUG Core.c:259 Finished getting pre-configuration from client
1437493720 DEBUG UDPAddrIface.c:255 Binding to address [127.0.0.1:11234]
1437493720 DEBUG UDPAddrIface.c:294 Bound to address [127.0.0.1:11234]
1437493720 DEBUG UDPAddrIface.c:294 Bound to address [0.0.0.0:57533]
1437493720 DEBUG AdminClient.c:333 Connecting to [127.0.0.1:11234]
1437493720 INFO Configurator.c:135 Checking authorized password 0.
1437493720 INFO Configurator.c:157 Adding authorized password #[0] for user [password [0]].
ОК.

1437493721 CRITICAL Configurator.c:107 Got error [Not supported on windows] calling [Security_getUser]
1437493721 CRITICAL Configurator.c:57 enable Log_LEVEL=KEYS to see message content.
1437493721 CRITICAL Configurator.c:71 Aborting.

C:\>
iczero commented 9 years ago

The error can be fixed by commenting out line 461 rpcCall0(String_CONST("Security_getUser"), d, ctx, tempAlloc, &ret, true); of client/Configurator.c and turning off incompatible security features. However, after applying those changes, cjdns will still crash without an error message. Apparently the core exits with error code 0. I use http://www.santacruzmesh.net/installer.html if I want to run cjdns on windows.

misuzu commented 9 years ago

Windows installer is kinda outdated.

iczero commented 9 years ago

Yes. It certainly is outdated.

iczero commented 9 years ago

I got it to work... Apparently you have to also comment out lines 460, 461, and 462 to prevent a segfault.

misuzu commented 9 years ago

Yeah now it starts. But when i ping some cjdns host it crashes.

ghost commented 9 years ago

@misuzu please include logs and crash output

misuzu commented 9 years ago

Terminal screenshot: http://i.imgur.com/avE3Iuv.png

iczero commented 9 years ago

I have encountered the same exact issue. Any network traffic crashes cjdns.

interfect commented 9 years ago

The crash on network traffic should be fixed by https://github.com/cjdelisle/cjdns/pull/815

I have also rolled that fix into an updated installer.

misuzu commented 9 years ago

It works!