Using ROIndyHTTPServer to provide services, how to set up services to support IPV6, in order to enable the IOS application through the IPV6 network normal access to the server?
use ROIndyHTTPServer.IndyServer.Bindings
Is not according to the following IPV4 and IPV6 are added, will support both IPV4 and IPV6?
HTTPServer.IndyServer.Bindings.Items[0].IPVersion:=Id_IPv4;
HTTPServer.IndyServer.Bindings.Items[1].IPVersion:=Id_IPv6;
var
k: TIdSocketHandle;
begin
k := ROIndyHTTPServer1.IndyServer.Bindings.Add;
k.IP := 'FE80:0:0:0:6CBB:5E0B:4F1A:8D5D';
k.IPVersion :=Id_IPv6;
k.Port := 8099;
k := ROIndyHTTPServer1.IndyServer.Bindings.Add;
k.IP := '192.168.206.1';
k.IPVersion :=Id_IPv4;
k.Port := 8099;
ROIndyHTTPServer1.Active := True;
Well, thank you very much.
@EvgenyK, what is the screenshot? looks interesting.
this is Process Explorer utility
Hello, I am bound by the above method IPV4 and IPV6, the access to the IPV6 address of the port listening, why?
Can you show a piece of code you have used?
Hello, I use the ROINDYHTTPSERVER, RO9.0.97.1245 according to the method provided by the binding IPV6, can not successfully bind IPV6 address, always prompt port is occupied, I do not know why?
what port you are specify for IPv6? 8099?
try to change it to anything else
Hello, bind IPV6, prompted as follows, with source code:
test.rar (4.6 KB)
it works for me:
have you specified valid IPv6 address?
Hello, this is not related to the compiler environment, the Annex I compiled for the EXE, in which you have no problem to run it?
Project1.rar (531.3 KB)
it works as expected
Hello, my server is WIN2003 or WIN2008, the program can not listen to the IPV6 after the start of the port, I would like to ask you what is the operation of the environment over there?
can you check this with Process Explorer utility?
what port and tcp protocol will be should in Process Explorer for your program?
Hello, I use Explorer utility Process seen in the TCP/IP page does not have the corresponding IPV6 and PORT。
do you have another active application that uses the same ip:port ?