On Tuesday, February 24, 2015 12:32:38 Daniel-Constantin Mierla wrote:
Hello,
can you try again with the latest master -- it should have fixed the
part with ipv6.
The other issue with matching client profile was changed to ignore port
if it is 0 in the tls.cfg definition -- can you try to
Hello,
can you try again with the latest master -- it should have fixed the
part with ipv6.
The other issue with matching client profile was changed to ignore port
if it is 0 in the tls.cfg definition -- can you try to see if works?
Cheers,
Daniel
On 24/02/15 04:09, Anthony Messina wrote:
On
On Tuesday, February 24, 2015 12:32:38 PM Daniel-Constantin Mierla wrote:
Hello,
can you try again with the latest master -- it should have fixed the
part with ipv6.
Using [client:[2607:5300:60:1f93::0]:0] in tls.cfg, it looks like the IPv6
part works. Thank you.
The other issue with
Hello,
can you try with latest master? After just quick view of sources, I
spotted some issue identifying ipv6 address and pushed a small patch for
it, but no time to test it for now.
Cheers,
Daniel
On 23/02/15 10:01, Daniel-Constantin Mierla wrote:
Hello,
On 23/02/15 02:16, Anthony Messina
I just pushed a patch to lookup client tls profile using bind address
(if available), instead of local source address for the connection,
trying to avoid matching on a randomly allocated port by os.
Let me know if works fine.
Cheers,
Daniel
On 23/02/15 11:26, Daniel-Constantin Mierla wrote:
Thanks, Daniel. I'll be rebuilding with the recent changes this evening. A
few clarification requests inline below...
On Monday, February 23, 2015 11:26:27 AM Daniel-Constantin Mierla wrote:
Hello,
can you try with latest master? After just quick view of sources, I spotted
some issue
On Monday, February 23, 2015 11:31:27 PM Daniel-Constantin Mierla wrote:
I just pushed a patch to lookup client tls profile using bind address (if
available), instead of local source address for the connection, trying to
avoid matching on a randomly allocated port by os.
Let me know if works
Hello,
On 23/02/15 02:16, Anthony Messina wrote:
I'm wondering if anyone can point me in the right direction for the following
two issues with Kamailio and tls.cfg
1. When attempting to configure TLS settings for connecting to a specific
IPv4
client, it seems that the ca_list indicated
On Monday, February 23, 2015 11:26:27 AM Daniel-Constantin Mierla wrote:
Hello,
can you try with latest master? After just quick view of sources, I spotted
some issue identifying ipv6 address and pushed a small patch for it, but no
time to test it for now.
Cheers,
Daniel
snip
2.
I'm wondering if anyone can point me in the right direction for the following
two issues with Kamailio and tls.cfg
1. When attempting to configure TLS settings for connecting to a specific IPv4
client, it seems that the ca_list indicated in [client:default] overrides the
one in the
10 matches
Mail list logo
