Hello All,

Currently we have been developing on FPC for both Windows and Linux and we have noticed that socket communications are not working correctly under Linux environments. I have also been advised that the netdb has issues on 2.0.4? is this correct?

If we use FPC 2.1.1 on Windows, the socket communications work correctly but if we drop back to 2.0.4 it then fails also. I can not use 2.1.1 on linux or am I knowledgeable enough to get it working under linux with Lazarus. The client application we are creating MUST be linux environment. I was wondering the following:-

1) Is there a patch out for this bug or a known solution on how to correct the problem so that socket communications can work from Linux to windows?

2) When is FPC 2.1.1 expected to be released to the public? (No pressure, just a simple question).

3) Can we actually get the 2.1.1 development code (I know how to do this) and make it work with Lazarus 9.19 beta (Don’t know how to do) on Linux? If so, can anybody guide me on how this can be done?

Any feedback to this mail would be greatly appreciated.

Kindest Regards,

Daniel Hobson

Currently we have been developing on FPC for both Windows and Linux and we have noticed that socket communications are not working correctly under

Linux environments.
please define what you mean by not working correctly, preferally with a test app

I have also been advised that the netdb has issues on 2.0.4? is this

correct?
dunno i gave up on using netdb when a friend added IPV6 to the sockets wrapper i use and needed workable IPV6 dns code.

-----Original Message-----
From:
On Behalf Of peter green
Sent: Monday, 23 October 2006 9:28 AM
To: FPC developers' list
Subject: RE: [fpc-devel] FPC 2.0.4

Currently we have been developing on FPC for both Windows and Linux and we have noticed that socket communications are not working correctly under

Linux environments.
please define what you mean by not working correctly, preferally with a test app

I apologise for been a bit vague in the original message.

It is not connecting to the windows server which is using TCP/IP. The Server address we use is 10.0.0.18 on Port 20000. Now we have tried various things with this including the following:-

1) Using Synapse 37 API (Messaged these fellows already)
2) INET 0.4.0
3) SocketClient

I remember when using FPC 2.0.2 I had to fix the htons() call as it was using a 32bit value rather than a 16bit word value. I have checked this code again against 2.0.4 and it seems to be ok.

From my analysis I believe there is a failure somewhere when it comes to

building the SIN IP address / resolving the address. The port information seems to come across correctly as a word value of 8270.

We have done pinging and trace routing to the windows machine where the server application runs and packets are going through. This indicates there is NO firewall and shows that our network is working correctly. Ethereal 0.99 shows no packets coming across to the windows machine when attempting to connect. The server application does not show any indication of connection.

I have also been advised that the netdb has issues on 2.0.4? is this

correct?
dunno i gave up on using netdb when a friend added IPV6 to the sockets wrapper i use and needed workable IPV6 dns code.

I hope this is more helpful

Regards,

Daniel Hobson.

If you run port mapping tool such as nmap, do you see that the port is open (please note that on nmap the default amount of ports to scan are the first 1024, so you will need to tell it to scan port 20000) ?

Another point of checking will be in the machine that does the communication, and not the Windows side... can you see that the packages are going away ? if so, try to place on the same network another computer with a sniffer, and see if there is a search for the windows machine. If not, then it might be something else (firewall is not the only problem, proxy, ips and few other filters can be in the way as well, including ISA server).

Ido