crashing on receiving connection

Guus Sliepen guus at sliepen.warande.net
Thu Mar 8 23:26:47 CET 2001


On Thu, Mar 08, 2001 at 11:02:08PM +0100, Eduard Bloch wrote:

> > > netmask: 255.255.255.0 and broadcast: 192.168.1.255, so we have an IP
> > > range from 192.168.1.1 to 192.168.1.254. I just want to have to
> > > (virtuall) network cards (tap devices) which are really connected trough
> > > the SSL tunnel in userspace instead of cable. This is my point of view.
> > 
> > Ok, but then you should use Subnet = 192.168.1.1/32 and Subnet =
> > 192.168.1.2/32, because the Subnets indicate which parts of the virtual
> 
> Bad solution. Then I musf ifconfig'ure tap devices for "pointopoint" to
> another one.

Think of it like this:
     _____________________________________________________________
    |                       Entire VPN                            |
    |                     192.168.0.0/16                          |
     ________________    ________________    _____.. .   . 
    |     tincd A    |  |     tincd B    |  |
    | 192.168.1.0/24 |  | 192.168.2.0/24 |  |

Replace the IP addresses with those that fit your situation, but remember that
there is an entire VPN and part of it.

Ok, in the picture above, you would have to ifconfig tap 192.168.0.0 netmask
255.255.0.0, and add Subnet = 192.168.1.0/24 to the host configuration file of
tincd A, and Subnet = 192.168.2.0/24 to that of tincd B, and so on.

> > Btw, it's not exactly an SSL tunnel.
> 
> Hm, what else?

Blowfish encrypted packets.

-------------------------------------------
Met vriendelijke groet / with kind regards,
  Guus Sliepen <guus at 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/20010308/f2daeb4a/attachment.pgp


More information about the Tinc mailing list