@DelphiWorlds Are you setting either
BroadcastListenerrIPv6.IPVersion := Id_IPv6 or BroadcastListenerIPv6.Bindings.Items[I].IPVersion := Id_IPv6 to match the IP you are assigning? Why do you have a Binding created at design-time if you are just going to overwrite it at runtime? You may as well just use Bindings.Add() at runtime instead.
const
cMulticastGroupIPv6 = 'FF02:0:0:0:0:0:0:1';
procedure TForm1.FormCreate(Sender: TObject);
var
I: Integer;
LBinding: TIdSocketHandle;
begin
FLocalAddresses := TIdStackLocalAddressList.Create;
GStack.GetLocalAddressList(FLocalAddresses);
BroadcastServerIPv6.Port := 6000;
BroadcastServerIPv6.MulticastGroup := cMulticastGroupIPv6;
BroadcastServerIPv6.Active := True;
BroadcastListenerIPv6.DefaultPort := 6000;
BroadcastListenerIPv6.IPVersion := TIdIPVersion.Id_IPv6;
BroadcastListenerIPv6.MulticastGroup := cMulticastGroupIPv6;
BroadcastListenerIPv6.Bindings.Clear;
for I := 0 to FLocalAddresses.Count - 1 do
begin
if FLocalAddresses[I].IPVersion = TIdIPVersion.Id_IPv6 then
begin
LBinding := BroadcastListenerIPv6.Bindings.Add;
LBinding.IP := FLocalAddresses[I].IPAddress;
LBinding.IPVersion := TIdIPVersion.Id_IPv6;
LBinding.Port := BroadcastListenerIPv6.DefaultPort;
end;
end;
BroadcastListenerIPv6.Active := True;
end;
Just so that it's clear what is and is not being set
@DelphiWorlds and? what happens with it? If it is still not working, I don't know what else to tell you. I've only worked with multicast once before, but it was on Windows using IPv4, and I didn't use Indy for it, I used straight Winsock calls. But TIdIPMCastClient basically makes the same Winsock calls I did. The only difference being that I also enabled the SO_REUSEADDR option (the ReuseSocket property in Indy), but I don't think that is a factor in your situation. Try talking to Apple about your error.
I may have solved the binding issue, however unless another issue I'm having is resolved, it'll be rather moot. I've posted to the delphi.internet.winsock group in the forums and posted an attachment to the attachments group which illustrates the issue, which is happening on Windows, before I've even tried any other platforms
@mezen the simplest equivilent is to 1) resolve the IP using the socket API
gethostname() or getaddrinfo() directly (which are wrapped by Indy's TIdStack.HostByName() method), which uses the OS's own DNS resolver; and then 2) resolve the HostName using gethostbyaddr() or getnameinfo() (which are wrapped by Indy's TIdStack.HostByAddress() method), which also use the OS's own DNS resolver. Yes, TIdDNSResolverrequires a Host, because it implements DNS manually from scratch, and doesn't use the OS resolver at all. You can query your OS's DNS server(s), or let the user specify them.
Hello Techies, I am new to this forum I have a problem with INDY IDHTTP and IDSSLIOHANDLERSOCKET in delphi 5, after adding 3DES encyption in the server, all the rest call using "THTTP" fails with exception "Error Connecting with SSL", is there a way to fix this ? thanks in advance...!!
@MravArun also note that 3DES is vulnerable to attack, so why would you want to enable it in your server in the first place?
@penengo
TIdSync still works, but is deprecated because TThread::Synchronize() with an anonymous procedure accomplishes the same thing that TIdSync was originally intended for. Read Embarcadero's documentation for How to Handle Delphi Anonymous Methods in C++.
I want to replicate this site : https://hide.me/id/proxy to work in my internal network. From where i must begin?
@rlebeau Is support for OpenSSL 1.1.0 coming? I managed to successfully build iOS simulator dylibs for 1.1.0f, and tweaked IdSSLOpenSSLHeaders so it would load the new version, however it failed to bind to a number of routines, namely: SSL_load_error_strings, SSL_library_init, SSLeay_version etc
at least I assume it failed to bind to them because that's what WhichFailedToLoad reports
Complete list: SSL_load_error_strings,SSL_library_init,SSLeay_version,SSLeay,CRYPTO_lock,CRYPTO_num_locks,CRYPTO_set_locking_callback,CRYPTO_set_id_callback,ERR_free_strings,EVP_MD_CTX_init,EVP_CIPHER_CTX_flags,HMAC_CTX_init,HMAC_CTX_cleanup,CRYPTO_mem_leaks,CRYPTO_set_mem_debug_functions,OpenSSL_add_all_algorithms,OpenSSL_add_all_ciphers,OpenSSL_add_all_digests,EVP_cleanup,sk_num,sk_new,sk_new_null,sk_free,sk_push,sk_dup,sk_find,sk_value
I found the best performance by setting the client (sender) buffer to 0, and flat out sending the output message twice.
Wondering what I can tweak and what status I can look at to see what's happening.
I check the integrity of what I rcv.. it is good.
@robert010 are you sending the raw wave data as-is, or are you wrapping it in something like RTP?
not using any rtp type protocol,, very simple slow stuff, just an index per increment.
@robert010 that is a defining charactertictic of UDP, you can't guarantee packet delivery, or guarantee timing. Packets may be dropped, packets may take different network routes to the target, etc. You have to be prepared to handle that. Put an incrementing sequence number in the packets, require receivers to ACK packets received, re-send any packets that are not ACKed, reorder received pacekts, etc. Of course, this only applies if you require data integrity.
it is a visual wave,, so you see what is happening.
Data is for visualization only so occasional glitch would be ok
I know the disadvantages of udp.