Displaying 3 results from an estimated 3 matches for "hub3".
Did you mean:
hub
2018 Dec 11
3
subnet flooded with lots of ADD_EDGE request
...om nodeX
(192.168.0.1 port 655) which does not match existing entry" and it
turns out that the mismatches were cuased by different weight received
by add_edge_h().
This network is consists of ~4 hub nodes and 50+ leaf nodes. Sample
hub config:
Name = hub1
ConnectTo = hub2
ConnectTo = hub3
ConnectTo = hub4
Leaf looks like:
Name = node1
ConnectTo = hub1
ConnectTo = hub2
ConnectTo = hub3
ConnectTo = hub4
Back to the days of pure 1.0.33 nodes, if the network suddenly
fails(users will see tincd CPU usage goes 50%+ and unable to get ping
response from the other node...
2010 Nov 28
4
TCPOnly is required since 1.0.13?
...were not contactable.
I re-generated my rsa-keys, and checked my configuration. My vpn uses
the following in tinc.conf, as I am routing both ipv4 and v6.
===
name = node1
mode = switch
AddressFamily = any
PMTU = 1280
PMTUDiscovery = yes
TCPonly = no
ConnectTo = hub1
ConnectTo = hub2
ConnectTo = hub3
===
My VPN has some hosts called by nodex. These nodes are dynamic-ip, and
set to contact (connectTo) the hubs when they bring up their tincd.
The hubx nodes are fixed-ip, and are connected to each other in a full mesh.
With TCPonly = no, the vpn would only connect to ONE of the hubs, and
traff...
2005 Oct 26
1
Error message with fbt::copen:entry probe
All,
The attached script is causing the following error message ...
bash-3.00# ./zmon_bug.d
dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry):
invalid address (0xfd91747f) in predicate at DIF offset 120
dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry):
invalid address (0xfef81a3f) in predicate at DIF offset 120
Any ideas?
thxs
Joe
--