Displaying 20 results from an estimated 8000 matches similar to: "Question about res_init()"
2015 Feb 09
2
Tincd fails to resolve domain names before it is started name resolution becomes available.
On Mon, Feb 09, 2015 at 10:57:05AM +0100, Florian Klink wrote:
> I have some hosts which converted to systemd-networkd (which doesn't
> support hooks by now), and most of the time, tinc simply won't come up
> after bootup (or won't be able to reconnect when the network is
> changed), which is really ugly.
>
> Having a local dns in front is somewhat hacky, I'd
2015 Feb 02
2
Tincd fails to resolve domain names before it is started name resolution becomes available.
William Kennington <william at wkennington.com> writes:
> Agreed.
> On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne at edechamps.fr> wrote:
>
>> Considering how cheap that operation seems to be, would it make sense
>> to call res_init() every time tinc retries a metaconnection? It's not
>> doing that very often anyway... and it would solve
2016 Oct 11
2
Win32: problem with tinc-up script
Okey, this is new and better version.
Now we handle wait up to hardcoded (for now) value.
After wait (IP stack reconf or timeout) we launch 'tinc-up' script.
To handle initial TAP device traffic, script is now launched
in separate thread.
This version works 100% for me under Win2003.
---------- Original message ----------
From: borg at uu3.net
To: tinc-devel at tinc-vpn.org
Subject: Re:
2016 Oct 09
2
Win32: problem with tinc-up script
Hello.
Yet again I fight with tinc-up script on windows.
Long time ago I added hastly commit to fix it:
f61fd437ca36ff03cd669726894a09ae4e128427
Unfortunately, its not enough.. So I decided to change aproach.
Here it is: git://borg.uu3.net/OEM/tinc.git
branch: tap_wait
Im using iphlpapi to wait for windows IP stack to settle
with newly initialized device. After that, when tinc-up
is called, you
2016 Oct 24
2
Win32: problem with tinc-up script
Okey, after more extensive R&D and testing I came up with 2
final solutions:
1) external tool: wipchg
2) internal tincd: wait_device(int secs)
Both solution works 100% time (tested on Win2003).
I publish them here, so interested parties can do they own testing.
1) ftp://borg.uu3.net/home/borg/tmp/wipchg.tgz
You need Mingw compiler to build this.
2)
2015 Feb 01
2
Tincd fails to resolve domain names before it is started name resolution becomes available.
On Sun, Feb 1, 2015 at 11:19 AM, Guus Sliepen <guus at tinc-vpn.org> wrote:
> On Sun, Feb 01, 2015 at 04:08:47PM +0900, crocket wrote:
>
>> If tincd is started before name resolution comes up, it keeps failing
>> for ever to resolve domain names in Address= host configuration
>> variable after name resolution becomes possible.
>>
>> I think tincd should
2015 Sep 23
2
Large scale tinc tests
Well. I want to test subnet propagation, alternate paths, etc...
Do this, I would use Imunes because im very familiar with it..
I want to build small test network around 10 nodes with different
connectivity between them and then lay-out tinc network on it.
Then I can just set BER=1 to kill links and see how things happen etc..
Nice spot about ng_eiface indeed. I'll check it out..
As for
2016 Apr 08
2
Commit 68f4ca7 issues
There are few reasons why I stick to older OSes.
In case of FreeBSD its my customized Imunes platform
for network simulations...
Anyway, back to root problem:
gcc -std=gnu99 -DHAVE_CONFIG_H -DCONFDIR=\"/etc\" -DLOCALSTATEDIR=\"/var\"
-DFORTIFY_SOURCE=2 -g -O2 -MT tincd.o -MD -MP -MF $depbase.Tpo -c -o tincd.o
tincd.c &&\
mv -f $depbase.Tpo $depbase.Po
2016 Apr 08
2
Commit 68f4ca7 issues
Hi.
I have issues building tincd-1.0.26 on FreeBSD 4.11
Seems commit 68f4ca711593416d0defd81199b176ba604c6cb1
that "modernizes" build system was a bad idea after all?
Not sure why merging lib/ to src/ was done.
Most software I see contains directories like compat/
to aid building for older or broken environments..
This makes clear difference between software sources
itself (src) and
2015 Sep 23
3
Large scale tinc tests
Hello.
I wonder if someone here performe such large scale
tinc-vpn tests.. There are platforms like Imunes or CORE
to do generic Ethernet and IP testing and routing, but I found
that at least on Imunes it is problematic to start TAP iface
on vimage on FreeBSD (at least 4.11 with I use).
To fix that, I think about coding in BSD NetGraph support
to tinc. But first I need to do testing if actualy
2019 Feb 28
1
Problems with control (TCP) connections
Hello.
Im running tinc from long time, but recently I noticed that
tinc TCP connections are not closed correctly (timeout).
They seem to linger around like this:
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 80 0 xxx.x.x.xx:58801 xx.xxx.xxx.xx:*** ESTABLISHED
tcp 515 0 xxx.x.x.xx:45422 xx.xxx.xxx.xxx:*** ESTABLISHED
2003 Nov 06
2
openssh-3.7.1p2 on HP-UX 10.20
Hello,
I have dowloaded all that is required to build a working OpenSSH on HP-UX
10.20 from the HP-UX Porting and Archibve centre (this seems to be the only
way to go for 10.20). Make/install of all prerequisites has scucceeded. Now
make of openssh-3.7.1p2 gives the following:
gcc -g -O2 -Wall -Wpointer-arith -Wno-uninitialized -I. -I.. -I. -I./..
-I/usr/local/openssl-0.9.7b/include
2017 Mar 20
1
Option UDPOnly missing?
Hello.
I noticed that there is no UDPOnly option. Why so?
I prefer to control traffic as much as possible..
I belive, currently, when there is loss of connectivity,
tinc tries TCP too to restore connectivity... If succeed,
it needs to switch back to UDP then... Right?
So, can tinc use only UDP? Or it needs TCP for some metadata
communication?
Regards,
Borg
2003 Jun 15
1
make stops in bind's compilation
Hi,
Brand-new installation of FreeBSD 4.8 + 'make world', including updating
ports, sources, crypt/secure sources and everything.
When trying to compile bind8 from ports, this is the error that get
reported:
===> Building for bind-8.3.6
Using .systype
Using .settings
/var/tmp/usr/ports/net/bind8/work/src/include
/var/tmp/usr/ports/net/bind8/work/src/include/arpa
2020 Jul 27
3
SegFault when using TunnelServer=yes
Hi, thank for getting back.
I'll answer the questions, but I've already gave up on tinc and switch
to zerotier-one.
On 2020-07-27 5:10 p.m., borg at uu3.net wrote:
> Hi. I have few questions out of curiosity.. Cant help for now with
> your problem...
>
> What version is crashing? 1.1 or 1.0 ?
1.1 is crashing
>
> How your network is segmented..?
> I use tinc myself
2003 Jun 18
1
* build problem on older systems
Hi,
I have * running on a SuSE Email Server II, which uses an older
libc-version. Calls to res_ninit et al. from enum.c prevent asterisk
from building on that system. Could that possibly be changed to use
res_init and res_search in order to provide backward compatibility with
these systems ?
Thanks,
Holger von Ameln
2003 Jul 24
1
compilation error
Hi
I have some trouble getting asterisk to compile on my system. I get
unresolved external symbol in enum.c et srv.c on res_ninit, res_nsearch
and res_nquery. I've looked through my /usr/include/resolv.h file, and
endeed I didn't found any declaration of such functions. It seems to be
some res_init, res_search, etc.. but the declarations are the same the
res_nxxx ones.
Does asterisk
2008 Sep 30
1
Problem compiling tinc-1.0.8 on gcc-2.95
Hello.
I found that anonymous structures does not work on gcc-2.95.
If you guys want to support a bit older platforms I suggest
fixing it.
You can check out patch I created to fix this issue.
I just added 2 extra structures to remove anonymous
structs inside connection_status_t and node_status_t.
Patch is here:
ftp://borg.uu3.net/pub/unix/tinc/tinc.patch
Attaching it as well.
Regards,
Borg
2017 Mar 13
2
Tinc can't connect to names defined in /etc/hosts
Hi,
I have a host name defined in /etc/hosts (say "1.2.3.4 host1") that
resolves via that but not via DNS; consequently pinging and netcatting
to it works fine.
When I try to use that in a tinc host definition like "Address = host1",
tinc 1.1 tells me
Error looking up host1 port 655: Name or service not known
Why is that? Does getaddrinfo() tinc uses not consider
2015 Feb 01
4
Tincd fails to resolve domain names before it is started name resolution becomes available.
If tincd is started before name resolution comes up, it keeps failing
for ever to resolve domain names in Address= host configuration
variable after name resolution becomes possible.
I think tincd should succeed in resolving domain names after name
resolution becomes available.