Displaying 20 results from an estimated 4000 matches similar to: "questions"
2000 Jul 08
1
Problems starting up tincd with startupscript 1.0pre2-1.i386.rpm
Hello,
I'm trying to set up a vpn using tinc, so I installed tinc with the rpm version on my firewall as a listener. Setting up the tap device is no problem. The file /etc/tinc/tinc.conf looks like:
TapDevice = /dev/tap0
MyVirtualIP = 192.168.2.1/24
Vpnmask = 255.255.255.0
When I start the script /etc/rc.d/init.d/tinc start it says something about missing /etc/tinc/nets.boot
2000 Jun 11
3
TINC 1.0pre2 problem
On Sun, 11 Jun 2000, David Summers wrote:
> Thanks for the great software package! The question I have is this:
Thank you :)
> My goal is to set up a triangle topology VPN between three sites and run
> OSPF routing on all the sites so that if a link goes down between any two
> sites the OSPF routing will reroute the packets that used to go between
> the sites A <-> B to A
2000 Aug 03
1
tinc config(?) problems
I'm having a bit of a problem getting tinc up and running between a pair of
RedHat (one 6.0, the other 6.1) boxes. It's installed and configured to the
point where they can connect, but I'm not seeing any traffic passing
between the two systems.
System A looks like -
tinc.conf:
# Sample tinc configuration.
# Insert your own ip numbers instead of the placeholders,
# and be sure to use
2000 Mar 25
3
RFH -> Request for Help.
Hello all,
I've been playing with tinc to setup a wan between two offices of the
company that I work for. I'm partially there but having a slight problem.
tinc comes up between the 2 machines (both 2.2.14 debian woody
machines), and I can ping from the vpn machine at office a, and get a
response from office b. However, if I ping any other machine across the
wan I can't get a
2000 Jun 16
1
RedHat initialization script and bash2
Installing the new tinc on a system (Mandrake 7.0) that uses bash2 as it shell
turned up a problem with the redhat initialization script.
Attached is a patch to make it functional for both bash and bash2.
- Jamie
-------------- next part --------------
diff -uNr tinc-1.0pre2.org/redhat/tinc tinc-1.0pre2/redhat/tinc
--- tinc-1.0pre2.org/redhat/tinc Fri May 26 05:22:49 2000
+++
2000 Aug 21
0
Rewritten script /etc/init.d/tinc
THis is the modified script that came with tinc 1.0pre2, and it now uses ifconfig in stead of
ip-route.
I changed the syntax to be correct (may already have been fixedin a newer version), it now checks
whether or not there is a '/dev/tapX' or a '/dev/netlink/tapX' and it checks if there is a module or
not.
I also added the force_connect and the reload options. Force_connect send
2001 May 31
1
Routing
Hello,
>From the docs, it seems that tinc handles routing itself. Do users need to
add any routing entries for tunnels at all?
Here is sample scenario. There are six gateways A, B, C, D, E, and F
connected using tinc. Each gateway is has a separate network attached to it
and the connections are as follows:
E<-->F
^
|
v
A <--> B <--> C <--> D
^ +
|
2001 Jan 10
2
1.0pre3 difficulties
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
2001 Mar 16
2
Installation problems
When I try to install the tinc RPM I am missing
[root@relay buytaert]# rpm -vih tinc-1.0pre2-1.i386.rpm
error: failed dependencies:
libgmp.so.2 is needed by tinc-1.0pre2-1
[root@relay buytaert]# ls /usr/lib/libgmp.so.3
/usr/lib/libgmp.so.3
[root@relay buytaert]# rpm -qf /usr/lib/libgmp.so.3
gmp-3.1.1-3
This seems to be a too recent version.
So I tried compiling it and got the following
2001 Jun 09
2
/usr/local/etc instead of /etc
hi,
it looks like tinc-1.0-pre4 looks for configuration files in /usr/local/etc
instead of /etc ! what is the best way to change that to /etc/ so that i can
keep my configuration in /etc/tinc/netname/, as described in the tutorial?
from what i can see, you have a sysconfdir="$prefix/etc" in configure.in.
However, i can't just change prefix to empty string because there is also a
2000 Jun 12
0
TINC 1.0pre2: unable to access one private network
On Sun, 11 Jun 2000, gbarnett wrote:
> Guus... I couldn't seem to get this to the mail list... could you post it
> and/or answer it for me?
Sure.
> 2.3.4.5/tinc.conf
> MyVirtualIP = 10.69.69.69/32
> TapDevice = /dev/tap0
> VPNMask = 255.255.255.0
Problem found (I think)! MyVirtualIP should be 10.69.69.69/29. Your
VPNMask is correct. Idem for server B, where MyVirtualIP
2001 Mar 19
4
Tinc doesn't connect
Hi,
I'm trying to set-up a VPN using Tinc 1.0pre3.
When I start tincd I get the following in /var/log/messages.
On the machine that listens for incomming connections:
> Mar 16 17:23:24 vpn tinc[1168]: tincd 1.0pre3 starting
> Mar 16 17:23:24 vpn tinc[1168]: Ready: listening on port 655
On the machine making the connection:
> Mar 16 17:16:51 mail tinc[802]: tincd 1.0pre3 starting
2001 May 25
4
tinc 1.0pre4 released
Hello everybody,
I have just released tinc 1.0pre4. Changes:
- New authentication protocol (better security, and faster too).
- TCPonly and IndirectData are back (but not fully tested).
- Documentation revised, it's really up to date with the released package now.
- tincd -K now stores public/private keys in PEM format, but keys of 1.0pre3
can still be used.
- Faster and more secure
2008 Jun 03
2
Interrupt storm with shared interrupt on digi(4)
I have an on-going problem with DigiBoard Xem boards causing interrupt
storms (since 4.x days). The FreeBSD driver polls the board and
doesn't have a functional interrupt handler (and Linux behaves in the
same way). It seems that under some conditions, the board will assert
its interrupt line and, since there's no interrupt handler to clear
whatever triggered the interrupt, the IRQ is
2007 Feb 18
3
handling mac addresses and guid''s
Hi,
I like Xen''s feature of autogenerating those values if they are not supplied in
a config file, but for sake of persistency I want to inherit the once-generated
values and reuse them after the first creation of a domU.
I found it possible to query the values at runtime using xm list
--long but I''m not sure I''m going the most elegant route with that, it
would mean
2001 Feb 08
1
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
2001 May 07
1
Config error - please help
I installed Tinc and started on two mashines. both connect and say
everything is OK. But then when I try to ping through the VPN I get the
following errors in syslog:
on server:
rtr-us tinc.vpn_net[911]: Metadata socket read error for BG_VPN (x.x.x.x -
inet ip of client): No such process
and on client
ns tinc.vpn_net[301]: Incoming data socket error: Connection refused
what does it mean as on my
2001 Feb 22
1
tincd running, but ping test doesn't work!
Hi Tinc Mailing Group,
I've got Tinc-1.0pre3 set up on two Redhat Linux 6.2 / kernel 2.2.18
servers. It compiles okay, it reads the configuration files okay, it
makes a valid connection between the two tincd daemons. However, it
does not route data from one subnet to the other subnet. I will
describe my setup below, and if anyone can suggest why it is not
working, can they please reply to put
2000 Sep 10
2
tinc SECURITY INFORMATION - Unauthorized access to VPN
Although we (the authors of tinc) have done our best to make tinc as
secure as possible, an unfortunate combination of encryption and key
exchange techniques has created a hole in at least all versions of
tinc >= 0.3, including the current CVS version.
Exploit:
If somebody can intercept the meta protocol to a host that is running
a tinc daemon, it is possible to decrypt the passphrase, which
2000 Sep 10
2
tinc SECURITY INFORMATION - Unauthorized access to VPN
Although we (the authors of tinc) have done our best to make tinc as
secure as possible, an unfortunate combination of encryption and key
exchange techniques has created a hole in at least all versions of
tinc >= 0.3, including the current CVS version.
Exploit:
If somebody can intercept the meta protocol to a host that is running
a tinc daemon, it is possible to decrypt the passphrase, which