Getting at a machine behind a ISDN router

[Guus Sliepen]

On Sun, Oct 13, 2002 at 10:46:52AM +0100, Carlos Sousa wrote:

> I'll only have physical access to miragaia tomorrow (a problem I was hoping
> to solve with tinc :), so I'll do it then.

Ok.

> tinc.vbcnet[2189]: Ignored signal 17 (Child exited)
> tinc.vbcnet[2189]: Checkpoint trace: process.c:253 <- conf.c:199 <- conf.c:122 <-
> conf.c:199 <- conf.c:122 <- device.c:76 <- conf.c:183 <- conf.c:122 <-
> protocol.c:190 <- event.c:54 <- edge.c:69 <- node.c:63 <- subnet.c:127 <-
> connection.c:72 <- connection.c:52 <- net_setup.c:526...
[...]
> Perhaps this signals a problem with my tinc-up script? It's:

No, nothing is wrong. If you set the debug level that high, tinc logs
all signals it received, whether they are harmless or not. In this case
it's harmless.

> So the "listening on 0.0.0.0" is right? Since I use "BindToInterface = eth0",
> shouldn't it be the actual IP assigned to eth0?

No. The eth0 interface can have more than one IP address, and they can
even change. "0.0.0.0" means "any IP address" that eth0 might have.
If you want to bind to a specific address, use BindToAddress =
<address>. You don't really need these options though, unless you have
multiple physical network devices or multiple IP addresses and really
want to limit access to a specific interface or address.

-- 
Met vriendelijke groet / with kind regards,
    Guus Sliepen <guus at sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20021013/fd0d6093/attachment.pgp