search

hyperboria / bugs

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

Failed to make function call [Timed out waiting for a response], error: [ETHInterface_new] #160

Closed Qix- closed 6 years ago

Qix- commented 6 years ago 
# cd /tmp
# sudo cjdroute --genconf > cjdroute.conf
# Log_LEVEL=KEYS sudo cjdroute --nobg < cjdroute.conf

1502085448 INFO cjdroute2.c:632 Cjdns amd64 darwin
1502085448 INFO cjdroute2.c:636 Checking for running instance...
1502085448 DEBUG UDPAddrIface.c:293 Bound to address [0.0.0.0:59521]
1502085448 DEBUG AdminClient.c:333 Connecting to [127.0.0.1:11234]
1502085448 DEBUG Pipe.c:134 Buffering a message
1502085448 DEBUG cjdroute2.c:689 Sent [144] bytes to core
1502085448 INFO RandomSeed.c:42 Attempting to seed random number generator
1502085448 INFO RandomSeed.c:50 Trying random seed [/dev/urandom] Success
1502085448 INFO RandomSeed.c:64 Seeding random number generator succeeded with [1] sources
1502085448 INFO LibuvEntropyProvider.c:59 Taking clock samples every [1000]ms for random generator
1502085448 DEBUG Core.c:355 Getting pre-configuration from client
1502085448 DEBUG Pipe.c:231 Pipe [/tmp/cjdns_pipe_client-core-1pcc58kj6c7qhtyqy04gclt0g0mwb4] established connection
1502085448 DEBUG Pipe.c:231 Pipe [/tmp/cjdns_pipe_client-core-1pcc58kj6c7qhtyqy04gclt0g0mwb4] established connection
1502085448 DEBUG Pipe.c:253 Sending buffered message
1502085448 DEBUG Core.c:358 Finished getting pre-configuration from client
1502085448 DEBUG UDPAddrIface.c:254 Binding to address [127.0.0.1:11234]
1502085448 DEBUG UDPAddrIface.c:293 Bound to address [127.0.0.1:11234]
1502085448 DEBUG UDPAddrIface.c:293 Bound to address [0.0.0.0:49305]
1502085448 DEBUG AdminClient.c:333 Connecting to [127.0.0.1:11234]
1502085448 INFO Configurator.c:135 Checking authorized password 0.
1502085448 INFO Configurator.c:159 Adding authorized password #[0] for user [default-login].
1502085448 INFO Configurator.c:407 Setting up all ETHInterfaces...
1502085448 INFO Configurator.c:423 Creating new ETHInterface [en0]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [en1]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [en3]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [en2]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [en4]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [bridge0]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [p2p0]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [awdl0]
1502085448 INFO Configurator.c:384 Setting beacon mode on ETHInterface to [2].
1502085448 INFO Configurator.c:423 Creating new ETHInterface [utun0]
1502085453 CRITICAL Configurator.c:97 Failed to make function call [Timed out waiting for a response], error: [ETHInterface_new]
1502085453 CRITICAL Configurator.c:57 enable Log_LEVEL=KEYS to see message content.
1502085458 CRITICAL Configurator.c:69 Failed to stop the core.
1502085458 CRITICAL Configurator.c:71 Aborting.

Running as root, still getting this error.

Is there something in the default configuration that's causing it to fail? I'm just trying to get some simple "hello world" type of connection going.

Qix- commented 6 years ago

Ah - by default, it attempts to bind to all interfaces.

Changing the default interface binding from all to my actual NIC device, en0 was the key here.

- "bind": "all",
+ "bind": "en0",