Was running 1.0pre2 just fine, but had to move machines, so I figgured I'd give 1.0pre3 a try. After getting everything to build and figguring out the new config files, here's where I'm stuck. Start the server process (remote machine). Start the client process (local machine). In remote machine, the following shows up in syslog: tinc[2659]: Got SEGV signal In local machine, the following shows up in syslog: tinc[21049]: Metadata socket read error for Srv (1.2.3.4): No such process Is more information needed? Since there's so many config files, I didn't want to immediately send them out. Also, is there any way to make the client process /not/ listen at all? It will not serve as a listen process for anything, so I'd rather not have the port open by tinc. Thanks! - Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://ftp.nl.linux.org/pub/linux/tinc/
On Tue, Jan 09, 2001 at 08:18:07PM -0600, Jason Ostermann wrote:> Was running 1.0pre2 just fine, but had to move machines, so I figgured > I'd give 1.0pre3 a try. > After getting everything to build and figguring out the new config > files, here's where I'm stuck. > > Start the server process (remote machine). > Start the client process (local machine). > In remote machine, the following shows up in syslog: tinc[2659]: Got > SEGV signal > In local machine, the following shows up in syslog: tinc[21049]: > Metadata socket read error for Srv (1.2.3.4): No such processThe error in the local machine is perfectly normal, it tells that the remote tincd has shutdown improperly (because of the SEGV). However, in order to determine the cause of the segmentation fault, could you show the lines in the syslog preceding the SEGV notice? And indeed, it would help if we could see the configuration files. ------------------------------------------- Met vriendelijke groet / with kind regards, Guus Sliepen <guus@sliepen.warande.net> ------------------------------------------- See also: http://tinc.nl.linux.org/ http://www.kernelbench.org/ ------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20010110/8e7d9e83/attachment.pgp
On Wed, Jan 10, 2001 at 09:30:58PM -0600, Jason Ostermann wrote:> The remote machine is bridged to another seperate network. The goal of > all these exercises is to bridge the local, remote, and the remote's > bridged networks. The problem is that tinc isn't sending the packets for > the remote bridge, I assume due to the "Subnet" directive.That is correct.> Quick map: > Local: 192.168.111.0/24 > Remote: 192.168.110.0/24 > Bridged to remote: 148.94.168.0/24Try to addt his to the host configuration files for remote: Subnet 148.94.168.0/24 You can have multiple Subnet statements in 1.0pre3.> What are my options? I know with 1.0pre2, I just had to shove the > packets to tap0, and tinc would go ahead and forward it.Ehr, if it did, you were just lucky :). ------------------------------------------- Met vriendelijke groet / with kind regards, Guus Sliepen <guus@sliepen.warande.net> ------------------------------------------- See also: http://tinc.nl.linux.org/ http://www.kernelbench.org/ ------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20010111/08ae9ffc/attachment.pgp