search for: logo_ixblue

Displaying 5 results from an estimated 5 matches for "logo_ixblue".

2010 Nov 11
1
Tinc and security
...8 88 Cell. +33 (0)6 37 23 40 93 logo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20101111/8b691d1b/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_ixblue.jpg Type: image/jpeg Size: 16773 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20101111/8b691d1b/attachment-0001.jpg>
2011 Jan 14
1
QOS Wishes
...08 88 88 Cell. +33 (0)6 37 23 40 93 logo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20110114/5cde076d/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_ixblue.jpg Type: image/jpeg Size: 16773 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20110114/5cde076d/attachment.jpg>
2011 Jun 15
1
Re connecting to SIP Provider with virtual IP, from pacemaker cluster
...Cell. +33 (0)6 37 23 40 93 logo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110615/a08a6e65/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_ixblue.png Type: image/png Size: 4832 bytes Desc: not available URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110615/a08a6e65/attachment.png>
2011 Jan 06
3
linux ip command and routing
Hi, I have a routing problem. When i start tinc it creates the following route in the main routing table. 192.168.2.0/24 dev nb003004 proto kernel scope link src 192.168.2.8 The problem is that i want to use extra routing tables for each tinc vpn. When i set the netmask for the tinc device to 255.255.255.255. The route is not created, how can i add it to a another route table. Setting a
2010 Nov 28
4
TCPOnly is required since 1.0.13?
Hi, I upgraded some of my Tinc nodes from 1.0.8 recently and found something strange. All of a sudden, the vpn would not work as a full-mesh. Certain nodes 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