tinc - Feb 2001 - Massive confusion

I'm probably thinking way too hard on this... but I've already got a
headache.

I've setting up a VPN for a client between two sites. Someone had
recommended vtun, so I gave it a try. I was VERY put off by the lack of
decent documentation. I _think_ I got a VPN set up between the two sites,
but it wasn't working right and I gave up because the documentation sucked.

So, then I found tinc on freshmeat and installed the 1.0pre2-1 RPMs for Red
Hat on both sides of the VPN. Tinc was a lot more attractive because of the
manual on the website. But... it is very confusing. I think the reason I'm
confused is because the manual is for 1.0pre3 and I'm using 1.0pre2. I see
there are .debs for pre3 but no RPMs for pre3. *sighs*

Both sites in my VPN have Linux boxes running IP Masquerade on them acting
as gateway and firewall to the Internet. I think this is why I couldn't get
vtun to work correctly. After I set up the vtun link, I would try to ping a
host on 192.168.1.x from a 192.168.2.x host and I wouldn't get any
responses.  But if I tried to ping an Internet host, I would get duplicate
replies (presumeably because the packets were being sent via both Linux
gateways. 

Do I need to write ipchains rules to get this to work with tinc? 

Also, the primary reason for doing this is so users at the remote site can
use this lame Windows network timecard app. Does anyone have any experience
doing this? 

If my information is not specific enough, I'll be happy to supply more...
but right now I'm not even sure where to start.

-=Fozz

-- 
Doran L. Barton <fozz@iodynamics.com> - Chief Super Hero - Iodynamics LLC 
< http://www.iodynamics.com/ > - Linux solutions and dynamic websites
 "A good messenger expects to get shot." --- Larry Wall 
-
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 Wed, Feb 07, 2001 at 10:53:12PM -0700, Doran L. Barton wrote:
> So, then I found tinc on freshmeat and installed the 1.0pre2-1 RPMs for Red
> Hat on both sides of the VPN. Tinc was a lot more attractive because of the
> manual on the website. But... it is very confusing. I think the reason
I'm
> confused is because the manual is for 1.0pre3 and I'm using 1.0pre2. I
see
> there are .debs for pre3 but no RPMs for pre3. *sighs*
Good point, we'll try to make some RPMs for pre2. But the 1.0pre2 RPM should
include a texinfo file called "tinc.info". If you have installed it
correctly,
you should be able to read it by typing "info tinc". That's the
same manual as
on the web, except that it is for pre2.
> Both sites in my VPN have Linux boxes running IP Masquerade on them acting
> as gateway and firewall to the Internet. I think this is why I couldn't
get
> vtun to work correctly. After I set up the vtun link, I would try to ping a
> host on 192.168.1.x from a 192.168.2.x host and I wouldn't get any
> responses.  But if I tried to ping an Internet host, I would get duplicate
> replies (presumeably because the packets were being sent via both Linux
> gateways. 
Very strange. It would help if you would send the output of "ifconfig"
on both
gateways, and the config files you wrote for tinc.
> Do I need to write ipchains rules to get this to work with tinc? 
No. But maybe you have an ipchain rule that is blocking tinc's packets
somehow, maybe you could send us your ipchains rules as well?
> Also, the primary reason for doing this is so users at the remote site can
> use this lame Windows network timecard app. Does anyone have any experience
> doing this? 
Not with timecard apps, but tinc should be able to handle that situation for
you.

-------------------------------------------
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/20010211/c5366e83/attachment.pgp